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 have the same problem today with my old MacBook. Xcode worked great until today. I don't know if it's because I've updated Xcode yesterday to v14.0.1. Or maybe this is some backend problem on Apple's side? But you are not alone with this problem.
Same issue here, problem started yesterday. I was a member of a long defunct team in addition to my regular account. I removed myself from that team thinking it would fix the problem as I am now a member/owner of just one team, but I'm still seeing the issue. Pinged Apple support, waiting to hear back.
Same issue here. I noticed it today as I was about to submit a build to Test Flight. I've also sent off a support email to hopefully get more notice. This seems to be a backend issue.
Same issue here since a few days. You can create a new feedback at feedback assistant. There are many others with this problem, maybe this StackOverflow thread could help you.
I received a support response with a generic "have you looked at our code signing help documents" response. I have pushed back in my response explaining this is either a bug with Xcode or their backend.
Same issue - I last successfully deployed three days ago on Sept 30th with no problem. Todays deploy of a minor bugfix returns this error. I also filed a bug report.
Just chiming in, I'm running into the same problem. As of this morning Xcode (14.0.1) won't show any of my teams in Accounts prefs even after signing out/in and I can't submit builds to the App Store/TestFlight. Submitted a support request to Apple but haven't heard anything back.
Attempted upgrading from 14.0 to 14.0.1. No change.
Support ultimately told me to use Feedback Assistant, so I've submit a request in there as well.
Same issue, I am not able to load my Apple Developer account details in Xcode in my MacBook M1 Pro. 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’”. Cant release new version of our App!
I've also started seeing this as well. Not sure what to do about it, means we cant submit to app store
I can also confirm it happens on every computer I have Xcode installed on. It's something specific with the account, as my other accounts in Xcode load just fine.
Same problem here. Couldn't submit to App Store connect. Tried to logout, and now I can't even get a team overview, in my Xcode account settings :/
I have this issue too. Xcode won't log into my account correctly in System Preferences (aI dialogue pops up with "Unexpected nil property at path: 'Actor/relationships/providerId'") so it can't possibly be problem with my code signing settings. I can log into all the Apple websites and portals I've tried, so it's not my account. I have an update I'd like to submit to the store, and I can't at the moment.
I had this too, it works now with Xcode 14.1 Beta 3. But then later it complains with an unsupported SDK version for the App Store.
PS: Correction, it does not work. There was a problem uploading a build which was solved, I referred to that. Sorry.
To those needing to push out a critical update as I did: disable Xcode's "Automatically manage signing" and build your app using manually provided certificates/provisioning profiles.
Quick step by step on how to create them on https://developer.apple.com/ if you need to:
Then in Xcode:
Finally upload the exported .ipa file using Transporter.app (get it on the App Store, the forum wouldn't let me link this one). This is a rather straightforward app.
So, it's a big hassle no doubt, but this allowed me to push out a highly critical update anyhow!
You might also consider setting up FastLane, avoiding the Xcode automatic stuff while allowing more flexibility to build apps. It was on my to-do list, now I guess the setup time investment will be worth the peace of mind...