Crash with iOS 17.4 when running in the Simulator
Hi!
First of all, I would like to apologise in advance because I understand it's unlikely the information I'm able to provide here will be sufficient to understand the crash I am experiencing; I still wanted to open an issue in case my problem is not isolated.
I have a SwiftUI project targeting iOS 17.x that uses VLCKit 3.6.0b10 to play RTSP streams; my project does not yet take advantage of the new Swift concurrency and Xcode's concurrency check is set to minimal.
I've been running this app in the Simulator and on devices (iPhone and iPad) for a couple months without any issue, from different Xcode versions up to 15.2.
Yesterday I noticed that launching the app with Xcode 15.3's Simulator reliably determines the attached crash to occur just a fraction of a second after calling mediaPlayer.play()
, and before playback actually begins:
I've run some tests (all on an Apple silicon Mac with Sonoma 14.3.1 23D60) with different Xcode combinations and iOS versions for the Simulator, confirming that the crash is directly connected with the iOS 17.4 Simulator, and does not seem to be related to the Xcode version (and therefore the Swift toolchain, which in all cases is left to Xcode's default):
- Xcode 15.2, iOS 17.2 sim -> no crash
- Xcode 15.2, iOS 17.4 sim ->
💥 - Xcode 15.3, iOS 17.2 sim -> no crash
- Xcode 15.3, iOS 17.4 sim ->
💥
Playing different RTSP streams does not affect the result.
Luckily, the problem only occurs when running my app on the Simulator, as this morning I have updated both my iPhone 12 Pro and my 9th gen. iPad to v17.4 of the operating system, and the crash never happens on device, even when attached to Xcode's debugger.
It seems to me the stack trace isn't telling much about what's going on, apart from possibly being a memory issue somewhat connected to OpenGL; I'm not sure if it's an Apple bug – seems likely – and how much invested would Apple be in solving an OpenGL bug if that's the case.
I hope these informations are somewhat useful, or better yet that no one else experiences this problem.