Unity Editor (2018.3) crashes using Database v5.4.4
See original GitHub issueUnity editor version: 2018.3.5f1 Firebase Unity SDK version: 5.4.4 Additional SDKs you are using (Facebook, AdMob, etc.): empty project with Firebase only Platform you are using the Unity editor on (Mac, Windows, or Linux): Mac Platform you are targeting (iOS, Android, and/or desktop): iOS
Please describe the issue here:
The 1st problem I met implementing Database is that WebSocket errors appear after Database initialisation. Here is an issue described and solution I used to make it run in Editor: https://stackoverflow.com/questions/50651865/unityfirebase-databaseerror-websocket-ws-0-could-not-connect
That helped to solve WebSocket issue, but another has appeared. It’s very similar to that one - https://github.com/firebase/quickstart-unity/issues/200
Very easy to replicate - set database url, call database update request, something like
FirebaseDatabase.DefaultInstance.RootReference.Child(subDatabase).Child(key).SetRawJsonValueAsync(jsonString);
Press Play and call the method. Stop, and Play again - Editor crashes or freezes.
That problem don’t allow to use Firebase at all… Wasted so much time trying to find the solution but nothing. How you “Firebase dev team” even can release such SDK’s?! Shame
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)? Yes
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:20 (5 by maintainers)
I have this problem with mac os with unity 2019.1.10 and Firebase 6.3.0 In play mode everything is ok, but as soon as I stop, Unity crashes. No other errors.
Why is this closed? Unity crashes here also With settings: Firebase.Database in Mono: Editor-Enabled in Plugins: Editor-Disabled Result- Crash when running.
Second scenario- in Mono: Editor-Disabled in Plugins: Editor-Enabled Catch error when “reference = FirebaseDatabase.DefaultInstance.RootReference”
I use .net 4 scripting and can’t revert because I need it for my script.
Edit: I reverted back to Firebase 5.4.4 (from 5.5.0), the problem is gone. Please report it as a bug. I won’t upgrade til the problem is fixed.