Facing the same issue "Error Finding App Store Connect Credentials" Rebooting Xcode and/or the device, sign in/out from Xcode, transporter... Nothing is working. All the certificates are Ok. Read somewhere that the issue solved by itself, so this is something on Apple side ? System status are green.

I've also tried uploading the build with Transporter and ... no success. Xcode Archive and export IPA (Distribute App) => working (with all the certificates and profiles checked) The IPA is exported on the disk Add the IPA in Transporter BUT Transporter contacts App Store Connect and gives the following issue: The App Bundle ID <com.xxx.NameApp> does not exist yet. Go to App Store Connect to add a new App. (6) This is already done! The bundle ID in the App (App Store Connect) is: XC com xxx NameApp - com.xxx.NameApp So I'm more than lost here! The profiles are successfully created by Xcode without an error, and the IPA created after all the checks with the App Store Connect. I've already sent a mail to the support as well.

Did you find a solution to this problem ? I'm facing a similar issue described here

Same here on Sonoma | Xcode 15 Reboot does not fix the issue, all explained here Did you find a solution to this problem ?

I got "Error Finding App Store Connect Credentials" on Monterey with Xcode 14 Now on Sonoma with Xcode 15 the error message is different, any status ???

I really feel your pain! I'm facing almost the same scenario since last Friday 17th. The technical team seems to be on vacation for thanksgiving (1 week), return to work on Mon, 27 Nov. I'm stuck with some builds that I can not upload to App Store Connect, all described here I've tried to solve on my side without luck, everything is set properly. Now I'm done and I'll wait for proper support. Very rough for a self-employed individual.

Bummer. However, this is still a useful result because it shows that Xcode is working fine and that issue is specific to the App Store Connect upload side of things. Does that mean we shouldn’t worry too much about double certificates (expired and valid) ? See here I think that’s the best path forward here Yes I sent it to your mail :) and I've also filled a TSI

What substitute mechanism could I use to determine visibility status of an AUv3 on macOS? I did some testing as well, none... Get the complete feedback created by user NikoloziApps here: After a few email exchanges with an engineer from Apple Developer Technical Support, Case-ID: 1997379, and experimentation, it has become clear that a subclass of AUViewController when used in a MacCatalyst AUv3 plug-in doesn't receive viewWill/DidAppear/Disappear callbacks. SwiftUI’s onAppear, onDisappear and onChange of scenePhase, also aren't getting called. However, when it's a pure macOS AUv3 then it works as expected. And things work correctly on iOS Reported via FB12145974, and I've just created FB13410524, please do the same and include both refs. The issue is also mentioned here on both topics: AudioUnits v3 OS X: How AU PlugIn may detect that AU Host did close window Plugin-editors still redraw even when closed on M1/Logic: https://forum.juce.com/t/plugin-editors-still-redraw-even-when-closed-on-m1-logic/45268

Update: The expired WDRC certificate is no more created by Xcode Beta 3 (Issue with previous versions of Xcode) "No App Store Connect access for the team" problem still remains, no solution! The error provided by Xcode Organizer is too generic, so I run the following command to get a bit more: xcrun altool --list-providers --verbose -u … The web service request post is Ok but the web service response is not: • Non-localized server string received “Unable to generate an Apple Connect token at this time due to a general error (1611)” • Bad status code: <MZWebServiceDAWTokenForUsernameAndPassword: …> • Error: Failed to list providers. Failed to get authorization for username ‘… and password. =>The auth server returned a bad status code (-1011) Apple service status is all green, what is general error (1611) @eskimo ?

Update: To better understand the previous error message from altool, I've tested with an invalid password and I got: Your account information was entered incorrectly. (-20101) Great! I generated an app specific password (instead of the regular one), and then the command succeeds! Finally I uploaded my IPA with altool (--upload-app) and it succeeds as well! (generated with Xcode | see previous reply) UPLOAD SUCCEEDED _ Back to Xcode and Transporter: "No App Store Connect access for the team" problem still remains I tried entering an app specific password with no chance! I have to use the regular one. So there is definitely something odd with the two authentication factors under the hood ? My TSI has been canceled and I received a list of suggestions regarding mainly signing issues, I've already replied and waiting for more info. I was already able to generate a valid IPA, signed and checked by Apple. So the issue is probably not on the signing but on the authentication in Xcode and Transporter.

Feedback created FB13449680 "Xcode Can't upload a build to App Store Connect, No App Store Connect access for the team"

Yeah, I’m at a loss as to what’s going on here App Store Connect connection problems from Xcode are mentioned in many places, in different forms regarding the Xcode version (the message is different). Usually a reboot is enough..., but it's not the case here. For info, Transporter app is also wrong with the failed message, I tested after uploading my IPA with altool. Transporter keeps mentioning a missing bundle id, but the app is there with the requested bundle id. I've tried to increase the build, no chance. So that’s unblocked your development, right? Yes I figured out a temporary solution, I hope to get a reply in "feedback assistant" very soon and a fix to upload my builds from Xcode to App Store Connect as I always did.

Same issue described here (ignore the expired certificate drama, probably not linked with the connection issue) Here a workaround: create your ipa manually: Xcode/Archive/Organizer/Distribute/custom/App Store Connect/Export (Sign and export to the disk without uploading) try to upload your ipa with Transporter if Transporter fails, try with altool (Check the link for details) If you still can’t upload your build with Xcode or Transporter, fill an additional bug report with feedback assistant. Include mine in the description: Feedback FB13449680 "Xcode Can't upload a build to App Store Connect, No App Store Connect access for the team"