Currently we are using a shared Apple ID to link Appcenter to our Apple Testflight, it doesn't have two factor authentication as its shared.
We noticed that we cannot deploy to Apple Testflight. When we go to the logs we get an error when it tries to deploy
##[error]{"code":"apple_authentication_error","message":"Error: Failed to publish to store. apple connection is not valid for connectionId: d3353867-3af0-4aa7-82ee-fdda6a1e896a"}
http response code: 400
We go into Distribute>Stores and we see "Your Apple App Store Credentials are no longer valid. Please re-authenticate." When we try to reauthenticate, iIt gives us an inaccurate error message. Need to acknowledge to Apple's Apple ID and Privacy statement. We sign in and there is no such privacy statement to acknowledge. Fastlane are suggesting fixes for this but since we are an Appcenter customer we do not implement this software ourselves.
https://github.com/fastlane/fastlane/issues/18098
I tried to authenticate user a different account (my own developer account) and get a warning that the 2FA code I entered isn't valid, yet the code works on Apple's site.
I reached out to Microsoft support and they requested I open a ticket here for a workaround since I don't see how to link Appcenter to an Apple .
We have the same problem
Same problem here
I was able to get connect but needed to create a new Apple ID. One thing I didn't realize was when I removed the old account and added a new one is, the actual apps had still the old account attached to them. I had to go to Distribute, Stores then hover over the AppStore Connect row, click on the "Delete Connection" then go back through the process of adding it back to the store. At this point it asked me to Authenticate with Apple with 2FA,create an App specific password (which I already had at hand) then enter the app specific password and I was back in business. I had to go delete the connection on my other Apple apps using that ID and reconnect them.
For me the problem was solved by enabling two-factor and app specific password, then remove connection and re-create the App Store connection in AppCenter
If i recall - there is something you need to acknowledge - but is isn't in the place you are expecting. I have forgotten exactly where - but try going to the Apple ID portal - not he app store portal.
Also - now everyone has to use 2 factor- but you can put multiple contact numbers
We solved the problem by using the app specific password but then it returned the subsequent time we went to do a deploy. I hope we will not need to create an app specific password and delete and create the connection each time we need to do a deploy.
Same issue here. I tried deleting my store connection as mentioned by @jdinnen, but as a lowly developer I do not have access to create new Apple IDs for my company. Perhaps it would have worked if I could have created a new user, but without that, I seem to be stuck in the water here.

This is impacting client work here as well. None of the mentioned workarounds are working, completely blocked.
I guess you need access to a Mac to upload IPA artifacts and this particular client is a Windows shop.
@mihailo-popovic96 any updates on this from the DRI?
@thejustinwalsh we have been able to delete the connection and recreate it and it will work the first time. It is when you go to do your next deploy it will give you the same message. I can't hardly believe that this has not been fixed.
Even with the 2FA set up, the connection will need to be re-authenticated on a regular basis and it's very inconvenient. We assume it did it's thing but often it didn't even distribute to TestFlight. Only one person has access to reconnect and the 2FA with Apple only sends to that one person's device to give us the 2FA code. I kinda wish that we just had an API key.
HI, we need help on this AppCenter, I also have it. Thanks for your time
Experiencing same issue here:(
Waiting for a fix soon
Experiencing same issue here:(
Waiting for a fix soon
Most helpful comment
HI, we need help on this AppCenter, I also have it. Thanks for your time