So the actor is being used to allow for lazy initialization of the pushToTalk framework while ensuring that it is only created once for the entire app. For example - if there were two places in the app that needed to use the pushToTalkFramework - we would want to ensure that the ptchannelManager was only created once but that it was lazily created (so not made until either area requested it). Normally we would use some sort of lock to ensure that the lazy variable was only created once - however since the ptChannelManager init is async we would not be able to ensure the lock is locked and unlocked from the same thread. This is why we introduced the actor to handle this. The crash isn't happening on macOS - we are seeing it in our telemetry for users on various iOS versions (16 + 17) and across many iPhone and iPad devices. I can work on trying to get a redacted full crash log and sharing here - if there is a way to share a private version though I think my team would prefer that. This is the type of crash we are seeing: Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 From what I can tell (by putting fatal errors in my own PushToTalkManager init and comparing those crash logs to my crash logs) the crash is happening somewhere in apple's PTChannelManager.channelManager async function.

So I was getting this error as well, it went away in beta3 and then came back in the other betas and in the released Xcode. I discovered that it was being caused by a custom framework we use throughout our app that was included in widget extension's Frameworks, Libraries, and embedded content section. We use the framework in all our other extensions with no issue so not really sure what is going wrong with it and the widget extension. The framework also seemed to be causing issues with swiftUI previews too. If anyone else encounters this or has any idea why a framework might do this it would be very helpful! Thanks!

I am on Xcode beta 5 with new build system and am still getting the same error, any other suggestions?

I was already on the new build system and have still been getting this error. Do you know if there is any other solution? I have encountered it in every xcode 12 beta (up to beta 5). Thanks!