If you use iOS 26, please read this! ⚠️

UPDATE 06.11.2025

The issues have been fixed, please see:

Users on iOS 26 may experience problems with SWAPD, especially with the composer. This is not an issue with SWAPD, it’s caused by Safari bugs on iOS 26. Unfortunately, nothing can be done until Apple provides an update.

This is a global issue affecting many platforms, not only SWAPD. More info: iOS 26 bugs with fixed-position elements in Discourse

We’ll share updates as soon as Apple rolls out a fix. Thanks for your patience.

13 Likes

UPDATE

The newest iOS update (currently BETA) does not fix the problem. The issue is with Safari, so if you plan to use SWAPD on your Apple iPhone our best suggestion is to install Chrome browser, as these errors seem to be absent on it.

Also the Discourse app has issues with IOS 26. Same problem where its very difficult to write text sometimes and click buttons :smiling_face_with_tear:

1 Like

You can thank @woody for this and his superior American products.

iOS 26.1 (BETA) update seems to have fixed the issue. So, once the final 26.1 iOS comes out, upgrade ASAP and problem fixed.

1 Like

It’s out. Let’s see if it fixes the issue.

1 Like

Testing. Is it better?

Still feels off. Can anyone check?

Checked. Its not fully fixed, but I can see they did some good work.

1 Like

It seems to be fully fixed! Can anyone confirm?

Nope

Not fully fixed for me :( However I only tested via HomeScreen app, not the browser. @Brant which do you use?

I use Chrome, seems fixed here.

Yes Chrome works. It’s Safari that’s the problem :(
GG Apple.

I can’t seem to download the app on my iPhone 15 at all since I can’t find it, is there a way to somehow download it? I hate getting the telegram notifs but not being able to have the app haha

Review this topic - The SWAPD iOS app is being discontinued, but that doesn't mean you can't use SWAPD on your iPhones and iPads, that’s the only way as for now to have it.

1 Like

Is it okay if we update?

Apple already fixed the issue, we are stuck waiting for them to release the fix.

Unfortunately they are being extremely slow releasing a critical OS fix, so we have to wait.

The issues have been fixed, please see: