Skip to content
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] Constant Editor Crashing on Using Firebase #1199

Open
Moe-Baker opened this issue Mar 5, 2025 · 3 comments
Open

[Bug] Constant Editor Crashing on Using Firebase #1199

Moe-Baker opened this issue Mar 5, 2025 · 3 comments
Labels
api: core needs-attention Need Googler's attention

Comments

@Moe-Baker
Copy link

Description

For the past 4 months our project has been plagued by constant Unity editor crashes.
After opening the project, the first play mode launch works fine, but the possibility of crashing starts racking up after that. It used to crash after every 5-6 play modes, now it crashes after about 2-3, and sometimes while just compiling code.

Reproducing the issue

No response

Firebase Unity SDK Version

12.6.0

Unity editor version

6.0000.0.40f1

Installation Method

Unity Package Manager

Problematic Firebase Component(s)

Firestore, Functions, Messaging, Database, Authentication

Other Firebase Component(s) in use

No response

Additional SDKs you are using

GameAnalytics, Adjust, Unity Services (Cloud Content Delivery, In App Purchasing, Vivox)

Targeted Platform(s)

Desktop

Unity editor platform

Windows

Scripting Runtime

IL2CPP

Release Distribution Type

Pre-built SDK from https://firebase.google.com/download/unity

Relevant Log Output

https://pastebin.com/7wdGJGgv

If using CocoaPods for Apple platforms, the project's Podfile.lock

No response

@Moe-Baker Moe-Baker added new New issue. type: bug labels Mar 5, 2025
@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@argzdev
Copy link

argzdev commented Mar 5, 2025

Hey @Moe-Baker, thanks for reaching out. For runtime crashes, I'm guessing that the instantiation of multiple SDKs using async/await could potentially introduce race conditions if ever any call to its functions is made before finishing initialization. As for compilation crashes, this is very rare, and could mean a bug within our SDK or an issue with the integration setup.

That said, are you able to reproduce the same behavior with an MCVE? If so, any chance you could share this with us? It'll help us investigate this issue further.

@argzdev argzdev added the needs-info Need information for the developer label Mar 5, 2025
@Moe-Baker
Copy link
Author

I can't really validate it with a minimal project; it's a very random crash.
I'll investigate the async SDK usage.

@google-oss-bot google-oss-bot added needs-attention Need Googler's attention and removed needs-info Need information for the developer labels Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: core needs-attention Need Googler's attention
Projects
None yet
Development

No branches or pull requests

3 participants