After upgrading iPad from 16.2 to 16.3.1, Xcode is behaving weirdly when I connect the iPad: most of the time, the iPad is listed in "Unavailable Devices" as "iPad (unsupported OS version)". I tried many times, and only 1 time my iPad was recognised normally by Xcode and I managed to deploy my app on it. But now Xcode lists it again as "iPad (unsupported OS version)" and I'm stuck again...
Post
Replies
Boosts
Views
Activity
Amsterdance26, go to this page to download a prior version of Xcode: https://xcodereleases.com. Dont choose 14.2 or 14.1 as they have this bug. I chose 13.2.1 but only because I have an old iMac (2014) and I'm stuck with macOS 11.7 (Big Sur). You can try 14.0.1 in your case. Then apply what I said and let me know if this works for you.
Amsterdance26: Just select the "DeviceSupport" folder in your old Xcode app, and select "Paste item" (assuming you selected "Copy" on the "16.1" folder before). This should make a copy of that "16.1" folder from Xcode 14.2 to this old Xcode app, which is then the good one to use.
Amsterdance26: Sure! You actually found the folder "16.1" I was talking about from the Xcode 14.2 package content. All you need to do now is to copy it and paste it in your previous Xcode version that was working before (same location within the package content), and then you keep and use only that patched Xcode. It worked for me, let me know if it works for you.
I found a workaround! Well, it will work if you're like me and the only reason why you upgraded Xcode is because it wouldn't recognize your device anymore (this happened to me after I upgraded my iPadOS to 16.2). Then the solution is to downgrade Xcode but with some missing files that you take from Xcode 14.2 so your previous Xcode version can recognize your device.
Here are the details: Locate Xcode (version 14.2) in the Applications folder, right click "Show package contents", navigate to Contents > Developer > Platforms > iPhoneOS.platform (or any other platform) > DeviceSupport. Then copy the folder(s) that are missing in your previous Xcode app in that same location (for me it was the "16.1" folder).
Then start the old Xcode app and it will recognize your device and you won't have that buggy 'Account Authentication Failure' anymore!
Same issue on 14.2, so I can't to test my app on my device as this issue prevents Xcode generating the signing certificate...
I have a free developer account for now. Does this issue affect only free developer accounts or also paid accounts?