-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Firebase Query Crash, EXC_BAD_ACCESS (KERN_INVALID_ADDRESS) on App Startup (iOS) #11978
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Thanks for the report @philip511. Please share the Firebase version used in the app |
@paulb777 Sorry! I updated my post, SDK version 10.16.0 |
Thanks for reporting @philip511 . It'd be quite difficult to pinpoint the bug without a reproduction. The stack trace suggests the issue to be related to converting a Firestore "Value" to an obj-c type. Would you be able to share the document content(s) that are being read? (feel free to obfuscate the content, but keep the types and also keep empty strings and nulls) Thanks! |
Yea, I mean the document content isn't anything special. It's about 30ish keys. Mostly strings, maps, and arrays. |
@philip511 please share the document data anyway, redacted if necessary. |
Closing as there's been no repro. |
Description
I am experiencing this crash on one specific line of code, in one specific method, within the first 2 seconds of the app openning.
This crash occurrs randomly on my users devices and never on mine so I cannot reproduce it. I just have what Firebase Crashlytics provides.
Some extra details about the code:
This query is run in ViewDidLoad on the first page the user sees when they open the app
This query is run in a background thread
This query is run concurrently with 6 other queries each on their own background thread
This crash only occurs in this specific query in this specific line
This crash usually occurs on the first iteration of FIRDocumentSnapshot but occasionally occurs after multiple iterations
Some solutions I've already tried:
I've tried allowing this query to finish before running any other queries
I've tried running this query last, after all other queries have finished
I've tried adding NULL checks to snapshot, doc, and doc.data
I've tried checking for an NSError
I've tried running it on the main thread
Crash occurs on this line when accessing doc.data
NSLog(@"Test %@", doc.data);
Reproducing the issue
I am completely unable to reproduce this issue. I just have the information that Firebase Crashlytics provides
Firebase SDK Version
10.16.0
Xcode Version
15.0.1
Installation Method
CocoaPods
Firebase Product(s)
Firestore
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
snippetThe text was updated successfully, but these errors were encountered: