@ollyd87: All you need to do is give your users an option to sign in with apple...

Have the same issue... Any suggestions how to fix that?

You need to generate a new key since the one Xcode auto-generates is not supported... ssh-keygen -t ecdsa -C "our_email" pbcopy < ~/.ssh/id_ecdsa.pub Go to https://github.com/settings/ssh/new, paste the key and save. Go to Xcode -> Preferences -> Sign into the github account if not already. Select SSH for "Clone using" For SSH Key select id_ecdsa.

Can't believe this is still not fixed...

Still experiencing this in iOS17. Only happens when using NavigationStack with path.

Same issue here. iOS17.

Looks like it's fixed in iOS 17.2 Beta Fixed: Resolved a possible Swift access conflict crash that could occur with toolbar items. (113992797)

Still happening in Xcode 15.2...

I'm also getting spammed with main thread warnings when I call func sceneDidBecomeActive(_ scene: UIScene) { Task { [weak self] in guard let self else { return } await ATTrackingManager.requestTrackingAuthorization() } } {"message":"This code path does I/O on the main thread underneath that can lead to UI responsiveness issues. Consider ways to optimize this code path","antipattern trigger":"-[NSData dataWithContentsOfFile:options:error:]","message type":"suppressable","show in console":"0"}

This is so annoying, I have a business name registered, but I'm forced to use my name instead....

so if i want to make a temporary change starting immediately until tomorrow, how does that work with that 24 hours wait time?

Did you figure it out? I'm trying to use my current iOS widgets in WatchOS 10 but they don't even show up on my watch after adding WatchOS to my current WidgetsExtension target...

Doesn't this fix a different issue though? // Meant to be a reply to a fix posted by tdsstore.

Did manage to figure this out?

Xcode 16.3 and still no Swift Assist. WWDC25 is around the corner....