How can we test offline functionality now? I used to just switch to airplane mode to mimic loss of network and then disable airplane mode again to be back online. What happens now, is that I loose the connection to the debugger and the console output, when doing so. It took me a while to even understand, that it is not my apps fault, that the connection to the debugger keeps on dropping and the apps gets killed, as if it would crash, but without any crash logs... Unfortunately I do not have enough hair left, which I could pull out over this issue. I am not even talking about the annoyance, when waiting for the deugging session to finally start. I am not able to do my work properly and haven't found a way around it yet, does someone have some sort of "trick" to debug offline mode?

I am monitoring this thread for quite some months now. Have I overlooked the workaround? No: "put this certificate in " or "make a symlink from to ". Since October I am missing my third build agent Mac Mini, because I had to update OSX in order to install Xcode 13 and back then Big Sur wasn't available anymore so I installed Monterrey. The other two agents thankfully are still on Big Sur and can do "their work". I thought it might only be a matter of weeks until the next release of Monterrey or Xcode. Nothing and also no perspective. Does that mean Xcode Server is dead? Nobody cares? No reaction from Apple whatsoever? Apparently nobody uses Xcode Server or at least not enough people, so that Apple would care. Is it time to move on to another solution for my CI/CD? And no, Xcode Cloud is not an option for companies, who do not grant access to their repositories to third parties without signing an NDA. Which is pretty common in our industry. At least amongst the bigger companies. The 3rd Build Agent is now sitting there collecting dust. Really Apple? Not even a workaround? Sad

Sorry, I wrote to the wrong thread. Please disregard.

So this one line: UITabBar.appearance().scrollEdgeAppearance means really, that either I am forced to use Xcode 13 on every build agent and dev machine or I can not use Xcode 13 on none of the machines, because that will "break" the Tabbar and make the app unusable. Not nice. What am I missing? This is ONE line of code and I can not figure out how to deal with the previous version of Xcode from 2 months ago? Really?

We are also experiencing problems with WKWebView on iOS 15. That happens only, if we compile the app with Xcode 13 and run it on iOS 15 devices. Compiling with Xcode 12 all runs well on the same iOS 15 device (well, what we can call "well" in a WebApp...) Did you find a solution meanwhile?

I am also struggling with the same issue. In the docs I read, that I need to wait until session(session:activationDidCompleteWith:error) returns with a "activated" state before I can sendMessage() on the session. But when I wait until that happens and only then call sendMessage, I still receive an error: ["WCSession sendMessage.error: Error Domain=WCErrorDomain Code=7007 "WatchConnectivity session on paired device is not reachable." UserInfo={NSLocalizedDescription=WatchConnectivity session on paired device is not reachable.}"] I am at a loss and I already implemented something ugly like delaying the sendMessage() for a second after calling session.activate(). There must be some way to tell, when it is safe to sendMessage(). Waiting for the callback 'activationDidCompleteWith' doesn't seem to be one of them :-(

Disabling iCloud and releasing a new version, doesn't help.Since you can not force the users to update the app, you will never get rid of iCloud support :-(That is very odd....and not any more helpful for the user, if we now release a new app and take the old app off the store. :-(

Hi Guy,I'm having the same problem ... and the same question.I just dropped iOS 10 support in our app, because it seems to work in OSes above 10. That's not a problem at all, but I am also asking myself the same question as you.Have you had any problems so far?