-
Notifications
You must be signed in to change notification settings - Fork 433
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
[Bug] Unity editor crashes on start #1053
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
@dconeybe Updated the initial issue with more details what causes the editor crash. Pinging you because you tagged the issue with "storage", but this seems to be a general Firebase/Firestore issue. |
Oh that information is helpful. The stack trace suggests that it's related to storage but that must be a red herring. I'll try to reproduce on Tuesday with your updated instructions. |
If possible, could you attach the full logcat when the crash occurs? Or at least some of the additional logs leading up to the crash. For example, is it a SIGABRT that crashes the app? |
I've taken a look at Firestore's section of the Unity SDK and found several places where specifying I have no idea why |
Update: The fix to add additional null checks to avoid crashes like this has been submitted and will be part of the next Unity SDK release (release date TBD). Note that it's not part of the Unity SDK 8.0.0 release. I'll reply back once the fix is released. |
Thanks @dconeybe for the fix. This should go out in 8.1.0. |
[REQUIRED] Please fill in the following fields:
[REQUIRED] Please describe the issue here:
When starting our project in the Unity editor, the editor crashes. The error log shows
We could narrow it down to the call
firestoreDB.Collection("l").Document(documentID).Collection("p")
,where
documentID
isnull
.While this should be checked in our code that
documentID
isn't null before trying to access the document, the Firebase SDK should also handle this internally to not completely crash the editor.We're not using the Storage SDK.
Steps to reproduce:
Relevant Code:
The text was updated successfully, but these errors were encountered: