-
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] Persistent connection error thrown when using Unity 2022 on Mac #1023
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hey @lmt385, thanks for reaching out. I'm trying to test your scenario using our quickstart repo but it seems to work just fine. I'm testing with version Firebase Realtime Database
Thanks in advance! |
I'll see what I can do in terms of providing a MCVE. Edit: While digging deeper, it doesn't seem to be triggering upon the listeners being registered, but at a later point related to the initial callbacks when calling GetValueAsync. The general flow is:
|
Description
When setting up or triggering ValueChanged callbacks for a DatabaseReference, errors are being thrown by the SDK in Unity Editor.
These errors only occur to our Mac machines, Windows machines and Android devices are unaffected.
The ValueChanged callbacks can be triggered, but they can then cause the same error that occurred when setting up the listener.
Originally observed this on Firebase version 10.7, upgraded to 11.9.0 and issue is still present.
Reproducing the issue
persistent_connection.cc
Firebase Unity SDK Version
11.9.0
Unity editor version
2022.3.23f1
Installation Method
.unitypackage
Problematic Firebase Component(s)
Database
Other Firebase Component(s) in use
Analytics, Authentication, Storage
Additional SDKs you are using
Azure Speech, AWS
Targeted Platform(s)
Android
Unity editor platform
Mac
Scripting Runtime
IL2CPP
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
Expand
Podfile.lock
snippet👀 Replace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: