proceeding to SMS verification gives error for (some) apps using Firebase Authentication
Dear all,
First of all thank you for taking time and effort to look at this bug report!
Cheers in advance!
Introduction
After installing LineageOS 21 successfully on my Pixel 4a (was made easy with the instructions; many thanks to the community!), I reinstalled my apps and after logging in on two (dating) apps, Breeze and Hinge (could recommend both for the interested person ;), but Breeze is only in Netherlands and Germany available I think ), I ran into problems.
For both I needed to submit my phone number for login in, which would be verified by a SMS code, like with WhatsApp for example, nothing special.
But both gave an error after submitting my phone number, where Hinge didn't give me any clue besides I should try again and make sure I was connected to the internet, which I was (did it both on Wi-Fi and Cellular). The Breeze app gave me a more detailed error:
This app is not authorized to use Firebase Authentication. Please verify that the correct package name, SHA-1, and SHA-256 are configured in the Firebase Console. [ Invalid app info in play_integrity_token ]
I tried to search on the internet for this error, but to no avail. Then I guessed it maybe could be a combination of the software and the app (maybe it's a bug in the apps).
Expected behavior
So the expected behavior is you give your phone number and you receive a SMS with a verification code to verify it's you, from which you can continue to the app (Breeze and Hinge).
Current Behavior
The behavior on my phone was that after entering my number and clicking proceed, I either proceed to the screen where I enter my supposed to receive code (Hinge) or stay at the number entering screen (Breeze), after which I receive an error code with both apps.
For Hinge I first receive the error that I should try again, and after that there is an error that says to make sure you're connected to the internet, which I'm (tried both Wi-Fi and cellular).
In Breeze I got a more informative message which hinted on that Firebase Console wasn't configured correctly for some reason (view above for the exact message).
Steps to reproduce
To reproduce is very easy, I just enter my number again and get the same behavior and error codes, no magic.
Trick to circumvent error due to bug
I also found a way to deal with this malfunction, which is somewhat the same for both apps. When I try to login on Wi-Fi I get the usual error, but then after that I retry immediately, but then not on Wi-Fi, but on cellular network, and then Firebase goes to my standard browser to open a tab to check whether I'm a human (maybe because the IP-address changed within a short period of time?). After that I proceed to the enter SMS code screen, after which I receive a SMS from CloudOTP, with the content:
Your Firebase App verification code is xxxxxx
The only difference between the two apps is that for Breeze it worked with my standard browser Firefox with my settings being high on privacy and AdAway installed (tried to login with both AdAway turned on or off, but no difference), whereas for Hinge I needed to set my standard browser to Chrome to have it work.
logcat
I did the above login process for Breeze, including the error with the first login attempt, after which I exported a logcat, which is attached.
I hope I did it right.
Device information
/device sunfish /version lineage-21 /date 2024-04-02 /kernel Linux localhost 4.14.336-gfe61ffb52659 #1 Sat Mar 16 00:36:11 UTC 2024 /baseband g7150-00112-230505-B-10075601 /mods Google Apps, Magisk, AdAway
I have read the directions.