-
Notifications
You must be signed in to change notification settings - Fork 441
Firebase Database plugin crashes when calling UpdateChildrenAsync() #371
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
Comments
Hi @YoavR Thank you for the information! Could you obtain the call stack of the crash? You should be able to find the editor log here. Thank you, |
Hi @chkuang-g, thanks for the response. I found two suspicious places that may point to the issue: The first is right when after I trigger the call to UpdateChildrenAsync(): Fallback handler could not load library /Applications/Unity/Hub/Editor/2019.1.3f1/Unity.app/Contents/Frameworks/Mono/lib/libAssets/Plugins/x86_64/Firebase/FirebaseCppApp-6.0.0.bundle The second is at the end of the call trace, as Unity crashes: Receiving unhandled NULL exception Thanks! |
It looks like you've enabled the C++ implementation of RTDB for desktop, which is not yet supported. We have plans to officially enable this in the future but as you can see it's not quite there yet. For now, I recommend sticking with the Mono implementation we have enabled by default. |
I have the same issue, I use Unity Editor 2018.3.10f1 and it crashes when I use UpdateChildrenAsync. How do you switch implementation from C++ to mono? |
@madgreg99 by default when you import the plugin the Mono implementation is enabled. So reimport the database plugin to revert to the intended settings. |
@stewartmiles thanks for the answer, I switched back to Mono but this implementation keep throwing this error: "PM [Error] WebSocket: ws_0 - could not connect" |
@madgreg99 yes in some cases we've seen issues with Unity's network stack in some version so check the known issues on https://firebase.google.com/docs/unity/setup#known_issues Also, some corporate networks like to block websockets which may be causing your problems. |
@stewartmiles I'm at home without VPN and I tried also using connection of my phone, same error. I don't see any work around in your known issues. The only work around I see is this one: #106 (comment) |
This should be fixed as of the latest release, 6.2.0 |
UpdateChildrenAsync() still not working in the Editor with Firebase SDK v6.2.0 Information Issue |
Hi QuentinGprd, can you post a call stack of the crash? And logs too. Can you reproduce this issue in the quickstart testapp? |
I tried to reproduce the problem in the quickstart testapp, UpdateChildrenAsync() worked without issues. From my project, here is the Editor.log at the moment of the crash:
Let me know if you need anything else. |
We are having the same issue with UpdateChildrenAsync(). We were able to reproduce it in the quickstart testapp database. It happens when UpdateChildrenAsync() is used in a node that have an eventListener (using the method ValueChanged) in the same or below hierarchy level. So here we attach the modified UIHandler script that triggers the error. By the way, another issue we found is when you push the button "SetValue Test", the event handler of the method ValueChanged is called twice when the parameter passed in is: "ServerValue.TimeStamp", also this happens in Android Device. Is this the expected behaviour or a bug? |
Hi all, I've been able to reproduce the issue and will have a fix shortly. Sorry for the trouble. |
I have same issues. When we can expect the fix? |
Hi everyone, this issue is fixed in the most recent release, v6.2.2. Give that a try and let me know if you still experience issues. |
Hello. I just installed it and it still didnt fix the issue for me. |
Ok. This update actualy gave me another issue with listener. After the update of firebase one of the listeners I have in my app is called twice doing same operation twice in same time which leads to duplication of some things. Very very strange. Changed to previous version with same code = no issues with that. Of course I can fix it with some checking if its been already processed, but ... |
Hello, with v.6.6.2, crash of UpdateChildrenAsync is gone, but now I'm experimenting more errors: |
Hello, On editor on windows it is crashing after
On editor on mac os it is crashing even earlier on database init:
We're also using Analytics, Auth, InstanceId, Messaging and RemoteConfig. @alexames |
Hi folks, Sorry the closed issue usually would be out of our support radar. If it is a different issue to the original post, please create a new thread. @craNich Could you detail your issue in a new thread? @PabloArd and @kreys We did fix a couple of Database editor related bugs in 6.6.0. Please try to upgrade to 6.6.0 and see if your issue is resolved. If not, please file another issue and file out the template. Thank you, |
Information
Unity editor version: 2019.1.3f1
Firebase Unity SDK version: 6.0.0
Firebase plugins in use (Auth, Database, etc.): Auth, Analytics, Database, Crashlytics, Functions
Additional SDKs you are using (Facebook, AdMob, etc.): Facebook, Playfab
Platform you are using the Unity editor on (Mac, Windows, or Linux): MacOS Mohave 10.14.1
Platform you are targeting (iOS, Android, and/or desktop): Android
Issue
This happened after upgrading the Unity editor from 2017.3.1p4 and Firebase Unity SDK 5.6.1
Most (not all) times that UpdateChildrenAsync() is called, Unity Editor crashes.
I've seen this was talked about in issue #191 but there hasn't been any updates for a while and was hoping to get some response.
Important to note, as in #191 , this only happens in the Unity editor.
The text was updated successfully, but these errors were encountered: