-
Notifications
You must be signed in to change notification settings - Fork 46
[Bug] "Unavailable invalid" FirebaseAuth for Unity on Quest 2 #1074
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
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hey @lremor , thanks for reaching out. For context, there's an issue with Firebase SDK version
Now according to the Unity forums, Unity Editors currently do not support compileSdkVersion 34, and is currently being worked on by their engineers. There are workarounds, by the Unity engineer, however I haven't tried it myself. While waiting for Unity to fix the version to support compileSdkVersion 34, one mitigation solution would be to downgrade Firebase SDK version There's also another solution shared by our developers, which I was able to verify that it works for Android emulators version 14. Though, given that we don't have any Quest 2 lying around, I'm unable to verify if this works.
Let me know if these changes works. Thanks! |
Hello, thanks for the answer, I tested with compileSDKVersion 33 but a build error occurs in the Android Gradle Plugin:
So, do I need to downgrade my version of Unity? If so, what would be the correct version? |
You have to downgrade Firebase Unity SDK to version |
Have you tried the solution from this thread shared by our developers?
If that doesn't work, could you try downgrading to version |
Hi again. I have already tested with the updated version (for Unity) of the FirebaseAuth SDK 12.1 (API Level 34, 33), and with 11.9.0 (API Level 32) and 11.6.0 (API Level 31). The dependencyStatus keeps showing "Unavailable invalid" The strange thing is that it works on windows, unity editor and android phone. Doesn't just work on Quest 2. Now I will try export the Unity project to Android Studio, btw I would appreciate it if you have another opinion |
Thanks for the updates, @lremor. Sorry, I'm not sure what the issue is. Do you have any logs or stacktrace to share with us so we can investigate this further? |
Hello again, we finally solved the problem! Although the application is for Android, all you had to do was install the IOS support build on Unity for Firebase to work and be available!
and it worked. Thanks for helping |
Its working now. |
Glad to hear it's working, thanks for the update! |
Description
I'm having trouble starting Firebase on Meta Quest 2. The app builds without errors and the message that should appear in the
FirebaseAuth dependencyStatus is: "available". However, when starting it on Quest 2, the following message appears: "unavailable invalid"
"Available" status occurs normally on Windows, Unity editor and Android phone. Does anyone know why this error occurs on Quest 2?
I tried rewriting the code, reinstalling the SDKs, setting up another Firebase account, checked the package name, checked Google services, tried options related to internet connection.
Reproducing the issue
Follow the code:
async void Start() { Debug.Log("Checking dependencies"); await FirebaseApp.CheckAndFixDependenciesAsync().ContinueWithOnMainThread(task => { dependencyStatus = task.Result; }); Debug.Log("Logging"); var auth = FirebaseAuth.DefaultInstance; await auth.SignInAnonymouslyAsync(); Debug.Log("Logged!"); auth.SignOut(); Debug.Log("Unlogged!"); }
Firebase Unity SDK Version
12.1.0
Unity editor version
24f1.3.2022
Installation Method
.unitypackage
Problematic Firebase Component(s)
Authentication
Other Firebase Component(s) in use
No response
Additional SDKs you are using
Nothing, only FirebaseAuth
Targeted Platform(s)
Android
Unity editor platform
Windows
Scripting Runtime
IL2CPP
Release Distribution Type
Pre-built SDK from https://firebase.google.com/download/unity
Relevant Log Output
No response
If using CocoaPods for Apple platforms, the project's Podfile.lock
No
The text was updated successfully, but these errors were encountered: