TIER escooter app. SMS verification with firebase fails.

wonder75

Hey, I try to register with the TIER e-scooter app.
https://play.google.com/store/apps/details?id=com.tier.app

Installation works fine but as soon as I request a confirmation SMS to my number the process fails.
The app opens the browser for a second, I can see that it calls a Google Firebase website.

The app returns after a second and notifies me that sending a SMS was not possible and I should retry a few minutes later.

I enabled nearly all permissions for google services framework, the app and Vanadium but still couldn't make it work. After that installed standard Chrominum to see if that solves the problem but it didn't. Disable VPN, tried with mobile data and WIFI, no success.

Have tried it for several days now and it seems to be a problem with GOS permissions, but I am out of ideas.

Did someone make it work? Any ideas what i could try to do?

Thanks a lot.

matchboxbananasynergy

wonder75 Hi there.

Did you properly install Sandboxed Google Play by installing Google Services Framework, Google Play Services and Google Play Store? All 3 are needed for a successful sandboxed google play installation.

https://grapheneos.org/usage#sandboxed-google-play-installation explains the correct proccess, please make sure to follow that.

Ideally you should uninstall and re-isntall the scooter app after installing Sandboxed Google Play.

If you already have, or if you do that, and it still doesn't work, please let me know.

wonder75

matchboxbananasynergy

I removed all the Google apps from GOS "Apps" and removed the TIER app.
Reinstalled them all.
Ended the profile (secondary user) and started it again.
Reinstalled TIER from GOS Sandboxed Playstore.

Sadly the same result.

I can try to provide any info needed to debug this

Thanks a lot.

GrapheneOS

Apps depending on Play services need to be installed after GSF. If you removed GSF, you broke all the apps depending on Play services in that profile until you reinstall those apps.

GSF is there to define shared permissions, interfaces, etc. It doesn't need permissions granted. Granting SMS permission to GSF won't give Google Play access to SMS where it needs it. Play services is what uses it.

In general, you don't need to grant permissions to Play services or the Play Store except in special cases. There's little reason to grant a permission to GSF.

uala

I can reproduce this.
Granting gsf SMS permissions won't change the error.
Any other permission missing?

akc3n

uala

Have you tried to dnable per-app exploit protection compatibility mode:
Settings → Apps → <App-name> → Advanced → Enable exploit protection compatibility

Also, look into the native code debugging setting, is it enabled or disabled?

sjors

I had the same issue and just worked around it by signing up with a Google account. Feeling a bit dirty, so let me try again…

The problem for me is confounded by the issue that Tier won't even show me the phone number login screen if it can't get a GPS fix, so I have to test it on the balcony. Turning on Exploit protection compatibility mode doesn't help. Where do I find the native code debugging setting?

If I go to the Apps app and click on Google Play services, it shows that this is installed, as are its dependencies (GmsCompatConfig, GSF and the Play Store). I haven't messed with those on my current device, but I restored it from a backup and I'm not sure what I've done on the previous device (also a Pixel 7).

I've tried enabling Exploit protection compatibility mode for Google Play Services (it was already on for GSF). No luck. Reinstalling Tier made no difference either.

MetropleX

sjors I've tried enabling Exploit protection compatibility mode for Google Play Services (it was already on for GSF). No luck. Reinstalling Tier made no difference either.

Nothing to add to the main point just wanted to inform you that the Exploit Protection Compatibility Mode toggle is only necessary if the app crashes due to a memory corruption issue. Beyond that the toggle should remain off. It certainly isn't necessary for any of the Play Services apps.

Edo

Similar problem with the app 'bond touch'. Weirdly enough other sms verification apps work with my profile but this one doesn't. The 3 google apps have every permission you can think of on this profile and i re-installed the problematic app with no luck.

Logs say he cannot find the firebase token, and that the firebase user is null.

type: logcat
osVersion: google/panther/panther:14/AP2A.240605.024/2024062000:user/release-keys
packageName: com.impossible.bondtouch:252
buffers: main,system,crash,events,kernel
level: error

06-23 13:37:06.090 22755 22826 E cutils-trace: Error opening trace file: No such file or directory (2)
06-23 13:37:09.484 22755 22895 E bondtouch: b: Get firebase token: Current user is null!
06-23 13:37:09.484 22755 22894 E bondtouch: b: Get firebase token: Current user is null!
06-23 13:37:12.556 22755 22818 E bondtouch: d$j: Failed to sync requests
06-23 13:37:12.556 22755 22818 E bondtouch: retrofit2.HttpException: HTTP 401
06-23 13:37:18.074 22755 22789 E FirebaseAuth: [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17499 Firebase App Check token is invalid.
06-23 13:37:18.083 22755 22755 E bondtouch: KickoffActivity$b: onVerificationFailed com.google.firebase.FirebaseException: An internal error has occurred. 


...
Any ideas?