Posts

Post marked as solved
2 Replies
0 Views
I seem to have solved the issue. Purged Xcode from my machine again. Including all caches. Deleted the contents of the /Library/Developer folder restarted my machine installed command line tools with Xcode-select --install redownloaded Xcode I think the PrivateFrameworks folder inside of /Library/Developer/ was the culprit. Its last modified time was when I installed Xcode 14 beta, not the last time I reinstalled Xcode 13.4.1 I imagine some of the stuff the simulator runtime relies on was corrupted.
Post not yet marked as solved
3 Replies
0 Views
I figured out what was wrong with it: this was what I was doing: for await _ in NotificationCenter.default.notifications(named: UIDevice.orientationDidChangeNotification, object: self) { print("orientation changed") // This would never fire } I changed it to: for await _ in NotificationCenter.default.notifications(named: UIDevice.orientationDidChangeNotification) { print("orientation changed") // This works } I guess I misunderstood what that object param was used for.
Post not yet marked as solved
3 Replies
0 Views
I honestly have not been able to get this to work either. It would be nice to see a demo of it in action.
Post not yet marked as solved
9 Replies
0 Views
Same issue here. A partial solution is to add the sign in with apple button to a navigation view. But if you log out and pop back to the login screen, it seems to happen again.
Post not yet marked as solved
3 Replies
0 Views
Having the same issue with one of our own swift packages. Works fine on intel Macs. Does not work on apple silicon Macs.
Post not yet marked as solved
3 Replies
0 Views
I have this issue as well. Xcode 12.3 is completely unusable.
Post not yet marked as solved
3 Replies
0 Views
I actually ran into an example of UIApplication.shared.delegate being nil today. During the init of your app delegate, UIApplication.shared.delegate is nil. So if something needs to access the app delegate immediately after super.init() there's a possibility its still nil. For me, I populated my dependency root for dependency injection here. I added a line of code to one of my services that needed to access the app delegate and it was nil. Other than this, I can't think of any other possible times that it would be nil.
Post not yet marked as solved
6 Replies
0 Views
Some additional details: im using the iPhone 11 Pro max simulator
Post not yet marked as solved
9 Replies
0 Views
So I figured it out sort of. Looks like something is wrong with the free provisioning profiles. I purchased a yearly dev subscription and now I can deploy without any issues. I hope this is a bug and Apple doesn’t plan on putting more limitations on free developers.
Post not yet marked as solved
9 Replies
0 Views
Same issue here. I’ve tried everything. I’ve tried deleting my developer certs, reinstalling Xcode, restarting my Mac and iPhone. The only thing I have not tried at this point is reinstalling iOS and Mac OS.