We are getting new Crashes in our Firebase recently for iOS 16.0 OS Devices. But we are not able to get any meaningful message from Crashlytics. Also when we are testing, we are not able to reproduce the issue as well.
nw_protocol_data_access_buffer crash for iOS 16.0
It’s hard to offer any insight here without an Apple crash report. If you have one, please post it here. See Posting a Crash Report.
for iOS 16.0 OS Devices
Are you seeing this just on iOS 16.0? Or on latest iOS versions?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
According to Firebase, this type of crash is all in iOS15 and iOS16，And according to Xcode Organizer, iOS15 and iOS16 are 95%. Below are the two crash stack information. Thanks a lot!
How does the OS version distribution of this crash match up with the OS distribution of your users? Because it’s interesting that iOS 16.1 crashes are very rare and iOS 16.2 doesn’t show up at all, even though 16.2 has been out for almost 3 months. Is there any reason to suspect that the vast bulk of your users haven’t upgraded to 16.2?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
About 25% of the OS Verson is greater than 16.2 And, according to the crash log, it is found that this type of crash comes from the background task launch
About 25% of the OS Verson is greater than 16.2
OK. We think we fixed a bunch of bugs that look kinda similar to this one in the late iOS 15 and early iOS 16 timeframe, but if you’re still see this on 16.2 then your issue is not the same as those issues.
It’s hard to offer any useful advice here. My best bet is that this crash is caused by problems in the OS itself. Given that, you should definitely file your own bug about this. Please post your bug number, just for the record.
However, I don’t see a lot of scope for workarounds. I presume that you’re not using Network framework’s QUIC support directly, but rather you’re using in indirectly by making URLSession requests, which in turn uses QUIC as part of its HTTP/3 support. Is that right?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
We are using ASIHttpRequest and URLSession now. and all crashes come from the background task launch
We are using
ASIHttpRequestandURLSessionnow.
Why are you still on ASIHttpRequest? It’s based on CFHTTPStream, an API that’s been deprecated for years now.
Having said that, it’s not the cause of this problem because it doesn’t support HTTP/3.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Sorry，According to Firebase, crashes happened all in OS Verson 16.0.x