Posts

Post marked as solved
32 Replies
0 Views
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
Post not yet marked as solved
31 Replies
0 Views
Sorry, I wrote to the wrong thread. Please disregard.
Post not yet marked as solved
1 Replies
0 Views
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?
Post not yet marked as solved
23 Replies
0 Views
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. :-(
Post not yet marked as solved
2 Replies
0 Views
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?
Post not yet marked as solved
2 Replies
0 Views
I have the same problem. Can't open the Xcode 11 archive, because there is not enough free space on the drive. The more GBs I delete, the less free space I have. :-(In summary I deleted about 30 GB and the free space went down from 9 GB to 7 GB. I suspected, that the TimeMachine Backup might be stored locally until the backup drive is connected. But running (the long overdue) backup, didn't solve anything. I installed the beta on a MacBook Pro, which I don't use much, as we all know, that such kind of problems can always appear when running beta software.When running "df" in the terminal, I can see, that a second partition was created. It seems like that second partition is autosizing and grabs free space from the partition I can see, as soon as some more free space get available.Did you find a solution, meanwhile? Or does beta 2 fix the issue and I get my hard disk back?