Open pavel-zaletski opened 5 months ago
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
Hello! Do you have any updates on this?
Any updates here?
Any updates?
Hi @pavel-zaletski, have you had any luck reproducing this locally since opening the issue? Apple's Finding Zombies guide may be helpful when trying to reproduce as the toolshould surface which object is receiving messages after deallocation. Another application state to try and target is sending a request before backgrounding the app.
Hey @pavel-zaletski. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
Hi @ncooke3, unfortunately I was not able to reproduce it locally. We see this crash only in the Embrace tool on some of our users' devices. I will try to use XCode Instruments tool (Finding Zombies) as you suggested. Thanks.
Description
Crash message: EXC_BAD_ACCESS (crashed) KERN_INVALID_ADDRESS Attempted to dereference garbage pointer 0x8.
From time to time we observe crashes in our app. Unfortunately we can't reproduce it locally. We see them only in Embrace tool
The issue is similar to the following: https://github.com/firebase/firebase-ios-sdk/issues/11403 https://github.com/firebase/firebase-ios-sdk/issues/12457
Recently we updated Firebase SDK to 10.24.0. But it did not help.
Reproducing the issue
Can't reproduce it locally. Crashes were observed in Embrace tool
Firebase SDK Version
10.24.0
Xcode Version
15.3
Installation Method
CocoaPods
Firebase Product(s)
Analytics, Messaging, Performance
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippet```json Replace this line with the contents of your Package.resolved. ```
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippet```yml Replace this line with the contents of your Podfile.lock! ```