-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in [APMSqliteStore endTransaction] #12962
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
@ilyavelilyaev Thanks for the report. By any chance, does your project or any of your dependencies call |
@htcgh Thanks for reply! |
Are there any other stack traces in the crash report that also use sqlite3? |
@htcgh No, only |
@ilyavelilyaev If you can share any crash reports in their entirety or provide any other information like affected iOS versions, that would really be appreciated. My team will continue to look into this, but progress will be really slow until we can reproduce the crash. |
@htcgh thanks for looking into this. Attaching couple of full stack traces. As for iOS versions - all versions are affected iOS 13 - iOS 17 |
I am also having a similar issue with a small number of my users. Here's the stack trace
|
Description
App crashes shortly after launching for small number of users having different iOS versions, pretty randomly.
There was a similar issue closed due to missing attention from reporter #11105 (comment)
Reproducing the issue
Could not reproduce locally
Firebase SDK Version
10.24
Xcode Version
15.2
Installation Method
CocoaPods
Firebase Product(s)
Crashlytics, Remote Config
Targeted Platforms
iOS
Relevant Log Output
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: