Some updates after a WWDC lab where I got to talk through this issue a bit with an Apple engineer: An issue on my end: I noted in my previous message that after successful PTT restoration it took two PTT messages for playback to be functional again. This was my fault. Re-initializing our AVAudioSession right away from within the incomingPushResult method fixed this for us Seems to still be a framework issue: In about 10-20% of cases, PTT does not fully restore itself after a device restart - meaning there is no blue PTT indicator after the device restarts. In these cases, receiving a new PTT message does appear to reinitialize PTT (the blue indicator suddenly appears and we get audio playback), but we still see some downstream effects in our app when this happens. For example, we can't reinitialize our microphone after PTT playback finishes (which we can do successfully when it fully restores in the 80-90% of cases) I've filed a Feedback (FB13890499) detailing issue #2 with two sysdiagnoses: one where it fails to reconnect upon restart (no blue PTT indicator), and another where it fails to reconnect upon restart and then revives itself after I receive a new PTT message. Both sysdiagnoses were captured on an iPhone 15 Pro running iOS 17.5.1. Things are significantly improved in this area after updating to iOS 17.5. Happy to discuss further. Let me know if there's anything else I can provide.

Great, thank you! I was testing on iOS 17.4.1. After updating to iOS 17.5, I am seeing notable improvement. After restarting my device 10 times with PushToTalk active, it restored PTT correctly 7/10 times and the blue PTT indicator was there. However, upon receiving the first PTT message after restart and successful reconnection, I would not get message playback. It would show the PTT notification saying "{person} is speaking", but there would be no playback. If I received a subsequent message, I would get playback for both messages (including the first one that did not initially play back) and then things worked flawlessly going forward. In the 3 occasions where it did not fully reconnect (i.e. the blue PTT indicator did not appear), when I foregrounded the app it reconnected fully and everything worked well from then on. This is a significant improvement, as previously if it failed to reconnect our app would get into a broken state regarding PushToTalk where we couldn't leave or join any channels. It seems that does not happen anymore, which is great. Ideally, though, it should successfully reconnect 10/10 times instead of 7/10 so users don't have to foreground the app to get back into a fully functional state. Thank you for the insight on this! So glad there is improvement as of 17.5.

I am seeing this exact behavior as well. Glad it's not just me! Have you found any workaround for it yet @Bodlund? I can "fix" it by essentially aborting the channelRestoration path within PTT's didJoinChannel method, but that means it will never reconnect on force quits, device restarts, etc. Not ideal

I'm seeing the same warning, as well as significantly decreased performance in my SwiftUI app on iOS 16 (none of these issues on iOS 15). Unsure if these are due to to an Xcode/iOS bug or if I'm actually doing something wrong.