The suggested workaround works, but the problem often returns and then the workaround has to done once more. For now, I work and build in Xcode 12.5, and then submit the build using Xcode 12.4.

I have found a work around / fix: • download and install both Xcode 12.4 and 12.5 from the developer downloads page • launch 12.4, then in the Organizer window one-by-one select all of your apps in the drop down box while “Archives” is selected. • quit 12.4, launch 12.5, open the Organizer window and it should no longer crash now.

Same assertion failure here in the logs.

Update: when I delete my developer account in Preferences - Accounts, Xcode no longer crashes when opening the Organizer. This means however that automatic signing and uploading a build no longer works, but at least it's some info that may lead to the solution.

Same problem, did not receive any e-mail but Testflight build was rejected. However, the accepted answer (clicking on the red badge) did not lead me to the resolution center (even though the URL made it seem so). I found the resolution center under My app - app store - version history - tap resolution center on the top right.

Same here (Xcode 12.4, 12D4e) , especially immediately after starting up my computer (fastest Mac mini 2018) which is switched off during the night. It occurs to me: • beach balls occur even without any file or project open. Xcode just stops responding while seemingly doing nothing. No disk, CPU or network activity can be seen. • if I wait it out (for instance 10 minutes) the beach balls will eventually finish and Xcode continues to work as normal. • if I wait it out (which is unbearable), the beach balls mostly will not come back until the next morning. • if I force quit Xcode, sometimes a couple of times in sequence, the problem is gone in most cases. • when Time Machine is doing stuff, beachballs take much longer to disappear. • unpairing all devices and re-adding them does not seem to help. • not using network but only lightning connections for devices does not seem to help. • cleaning out all caches, derived data, etc does not help. It's just terrible. I am afraid to open a new project or switch projects in Xcode because that seems to mean another early lunch break. I am afraid to open a storyboard or nib file because that may trigger another forced 10 minute wait.

Please note that I am NOT using Cocoapods and simply drag-install the Firebase frameworks manually into Xcode, and still the same warnings appear. This means it's probably not a Cocoapods issue.

No crash here but application grinds to a halt, using AVAudioSession and AVAudioPlayer. App execution on iOS 12, 13 simulators immediately logs: 2020-12-30 15:07:45.125612+0100 HALB_IOBufferManager_Client::GetIOBuffer: the stream index is out of range 2020-12-30 15:07:45.125793+0100 HALB_IOBufferManager_Client::GetIOBuffer: the stream index is out of range 2020-12-30 15:07:45.137752+0100 [aqme] AQME.h:254:IOProcFailure: AQDefaultDevice (1): output stream 0: null buffer 2020-12-30 15:07:45.137985+0100 AQMEIO_HAL.cpp:1774:IOProc: EXCEPTION thrown (-50): error != 0 2020-12-30 15:07:59.535460+0100 AQMEIO.cpp:179:AwaitIOCycle: timed out after 15.000s (0 1); suspension count=0 (IOSuspensions: ) 2020-12-30 15:07:59.535868+0100 CA_UISoundClient.cpp:241:StartPlaying_block_invoke: CA_UISoundClientBase::StartPlaying: AddRunningClient failed (status = -66681). After the 15 second timeout the app continues running until the next call to AVAudioSession or AVAudioPlayer. On iOS 14, everything is fine. I hope this does not occur on real devices but could not test that.

I encountered the same (pre-iOS 14) and stopped using NSKeyedUnarchiver. I now simply use: [SKEmitterNode nodeWithFileNamed:name];

Same here, also when using GKLocalPlayer authenticateHandler. Everything seems to work correctly though.

Same here, App Store version 12A7209

Same here, also using Google Mobile Ads Framework.However, the problem started AFTER I used the Product -> Analyze function. Before, no warnings, at all. After the analyze build, numerous "Invalid debug info" warnings appeared. Even after cleaning the build folder and the derived data folder, these warnings keep appearing.