I am not able to load my Apple Developer account details in Xcode in my new MacBook. After going to preferences in Xcode and signing in with Apple ID, after few seconds, it prompts the following error “Unexpected nil property at path: 'Actor/relationships/providerid’”. How can I fix this.
I got this problem as soon as I upgraded to XCODE 14.0. When I was just on XCode 13.4 I did not have this problem. But now because I wanted to update my XCode I am paying for it with this issue as it has done something to wipe out the 'Actor/relationships/providerId' in all my versions of XCode including 13.4. I have also had no luck whatsoever on solving this issue.
Same here. If someone from Apple is reading this please help! I was using 13.4.1 so I am installing 14.0.1 now hoping that fixes it. I am an admin for my organization and have multiple organizations. I cannot just leave the org and come back because I hold the keys to iOS deployment for my company. Please tell us how to fix this
I am also having this issue. Please help @Apple!
I can confirm. I have the same issue. Please help @Apple
Same here... same issue! @Apple
Same issue here aswell, @Apple help us!
Not sure if this will work for everyone but I was able to upload builds using Apple's Transporter app (available on the Mac App Store) WITHOUT having to switch to manual code signing and creating provisioning profiles. I just dragged in the exported .ipa file and it uploaded without a hitch.
As of right now, this seems to be working again. I was able to load my profile in Xcode Preferences and submit builds directly to App Store Connect.
Encountering the same/similar problem when trying to push from Swift on iPad. Full text of the error is:
Submission Failed
The operation couldn't be completed.
(PlaygroundDistribution.Distribution-AppRecordCredentialsProviderError error 1.). Credentialed provider request failed with error: "Unexpected nil property at path: 'Actor/relationships/providerId’”.
Error pops up right after tapping “Upload to App Store Connect”.
Unfortunately I don’t have a Mac so I can’t do the Transport work-around, and all other advice seems to center on XCode, but I haven’t found a solution for Swift on iPad yet.