-
Notifications
You must be signed in to change notification settings - Fork 38
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] Crash on macOS build when using any Firestore method call #1105
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hi @An-try. What type of mac are you using? Namely, is it an Intel-based or ARM-based CPU? Also, please enable debug logging, reproduce, and attach updated logs. To enable debug logging, run |
Hi @dconeybe. I’m using a MacBook Pro with a 2.3 GHz Quad-Core Intel Core i5. I have already enabled I will also prepare the Unity project and send it to you soon.
|
Thank you for the extra info. Could you try two things for me and let me know if the crash still occurs:
|
@An-try Can you also try running https://github.com/firebase/quickstart-unity to see if you experience the same crash? |
Oh, another thing: Are you calling |
I am calling I also tried the Firestore quickstart project and experienced the same issue. I tried removing the |
Hi @dconeybe I created a completely new Firebase project and used the Firestore quickstart project, but I'm experiencing crashes on any button press in this quickstart project only in builds for macOS. I set everything up according to the guides, and everything works fine in the Unity Editor on macOS, but not in Xcode or the built .app. I tested this on two different Mac devices: MacBook Pro, 2.3 GHz Quad-Core Intel Core i5, macOS Sonoma 14.6.1 (23G93) I have no pending updates for my system or Xcode (v15.4). I think we can close this issue and open a new one in the quickstart GitHub repository? |
Also, I tested it with Unity 2022.3.20f1, Unity 2022.3.44f1, Unity 2023.2.19f1 |
Additionally, I tried creating a build (.app) directly from Unity without using Xcode, and the issue still persists. |
Hey @An-try, just wanted to add some insights here. I noticed that I was also able to replicate the crashing behavior on macOS platform with our Firebase Unity Quickstart for Firestore. However, I accidentally resolved this after adding my login for the keychain. Steps I took:
I wonder if the issue in your case is also the same, though I'm not sure how to trigger or show the login credential for keychain manually. Let me know if this helps! |
@argzdev Unfortunately, I cannot reproduce your solution. The keychain popup is not showing up after several attempts. I will look for a way to manually trigger this window somehow... or maybe another solusion |
Description
When using FirebaseFirestore.DefaultInstance.Collection().Listen(), the function works as expected in the Unity Editor. However, when I launch the built .app or run it through Xcode, the app crashes with 90% chance.
Expected Behavior: Listen() should work without crashing in the macOS build, just as it does within the Unity Editor.
Actual Behavior: The function call crashes the app during runtime when executed from the macOS .app build or when launched from Xcode.
I need assistance in identifying why this issue occurs only in the macOS build and not in the Unity Editor.
Reproducing the issue
Behavior: After calling the StartListen() method, the log shows "id:..." as expected, but a crash occurs immediately afterward.
Firebase Unity SDK Version
12.2.0
Unity editor version
2022.3.20f1
Installation Method
.unitypackage
Problematic Firebase Component(s)
Firestore
Other Firebase Component(s) in use
Analytics, Authentication, Storage
Additional SDKs you are using
DOTween, Extenject, Photon Fusion, Agora Video Call
Targeted Platform(s)
Apple Platforms, Desktop
Unity editor platform
Mac, Windows
Scripting Runtime
Mono
Release Distribution Type
Pre-built SDK from https://firebase.google.com/download/unity
Relevant Log Output
If using CocoaPods for Apple platforms, the project's Podfile.lock
No response
The text was updated successfully, but these errors were encountered: