-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
FireBaseAuth not working in TIER-App #1281
Comments
See #1198 (comment) . Tier banned non-android authentication. |
Any news on that? I have a similar problem in LineageOS with microG (0.2.22.212658) when I try to register in Tier. I can type in my phone number and click on continue. It opens the browser then with a connection to
Everything is checked in the microG self test and I activated Cloud Messaging and Google SafetyNet. |
Just download an older version, for example i am vurrently using TIER app on 3.5.0 version, no firebase checks at all. |
@TonyK0s I can not confirm this, I downloaded Version 3.5.0 (version code 35000461) from the play store using Aurora, but when logging in, the FirebaseAuth Dialog still appears. |
Then clear all data and cache. |
I tried version 3.5.0 from Aurora Store and APK Fun, but both are just getting stuck in an loading loop after entering the phone number. I cleared all app data and cache. |
@TonyK0s It won't work, because both apps use FirebaseAuth, and they have to, as the API requires it, there are no alternative or old APIs. You probably have play services installed or aren't logging in, as the main view doesn't require authentification. |
No luck here either. :-( @acipenser How do I clear app data (other than deleting and re-installing?) LineageOS with MicroG 18.1 from 1/3/2022 Services Core 0.2.24.214816 Don't know if the following arre needed: |
I have the exact same behavior, but have installed a Samsung Stock Android 12 with original Google Play Store. So maybe the issue is not related to MicroG after all? |
I have the same behavior. |
Same problem. Micro g Version 0.2.29.233013-49 (1a2e94c) Calyxos 4.14.0 |
TIER app now seems to be working fine (at least for me). TIER app version: 4.0.127 |
Cannot confirm that (Same TIER app, MicroG and LOS version). Tried to sign up with my phone number. Did you use the Google Sign-In? |
No, I didn't. I used SMS verification. |
Okay, I tried it multiple times... But now I can say for sure that SMS authentication is indeed working fine for me. |
I updated to LineageOS 21.0 (2024-05-21) and it's working now for me. |
works for me with LineageOS 21: #1967 (comment) |
Отправлено с телефона
|
Dear all,
when TIER App tries to perform a SMS-auth via FireBaseAuth, the microG overlayer appears but nothing happens. Below I attached a logcat. I stripped off the key part of the URL https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=[replaced] because I'm not sure whether it contains sensitive info. I'm running microG 0.2.13.203915, Android 10, device is lavender.
11-25 22:24:41.221 D/GmsFirebaseAuth( 4035): onBind: Intent { act=com.google.firebase.auth.api.gms.service.START pkg=com.google.android.gms }
11-25 22:25:00.825 D/GmsFirebaseAuth( 4035): sendVerificationCode
11-25 22:25:01.168 E/Volley ( 4035): [333] BasicNetwork.performRequest: Unexpected response code 403 for https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=[replaced]
11-25 22:25:01.363 W/WindowManager( 1610): Unable to start animation, surface is null or no children.
11-25 22:25:01.470 E/Volley ( 4035): [333] BasicNetwork.performRequest: Unexpected response code 403 for https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=[replaced]
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035):
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): java.lang.RuntimeException: com.android.volley.AuthFailureError
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at org.microg.gms.firebase.auth.IdentityToolkitClient$getProjectConfig$2$2.onErrorResponse(IdentityToolkitClient.kt:58)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at com.android.volley.Request.deliverError(Request.java:617)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:104)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at android.os.Handler.handleCallback(Handler.java:883)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at android.os.Handler.dispatchMessage(Handler.java:100)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at android.os.Looper.loop(Looper.java:214)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at android.app.ActivityThread.main(ActivityThread.java:7356)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at java.lang.reflect.Method.invoke(Native Method)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): Caused by: com.android.volley.AuthFailureError
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at com.android.volley.toolbox.BasicNetwork.performRequest(BasicNetwork.java:195)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at com.android.volley.NetworkDispatcher.processRequest(NetworkDispatcher.java:131)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at com.android.volley.NetworkDispatcher.processRequest(NetworkDispatcher.java:111)
11-25 22:25:01.471 W/GmsFirebaseAuth( 4035): at com.android.volley.NetworkDispatcher.run(NetworkDispatcher.java:90)
The text was updated successfully, but these errors were encountered: