Hi!
Recently (a few weeks) I've been having issues with Uber. I downloaded it from the play store and it was working fine for a while but now I get an error (see link below). It says that I can still order rides, but when I try to it says the payment method is invalid, even though it is.
Thanks!
Idk about the app, but I just use the Uber web app in vanadium and it works fine and has less permissions
RRZishe I had this issue before and it was a temporary problem with the payment method I was using. Try using the Uber web app with the same payment method, If ordering rides fails again, then the problem is with the payment method. Try using a different payment method as well.
The nuclear option would be to create a new account, but I'm almost certain it is a problem with the payment method as I have never experienced trouble with Uber app (with the correct configuration for Sandboxed Google Play) for the past year.
I have also contacted Uber support once before and they stated that my use of a Custom ROM should not be a problem.
DeletedUser88 thanks, I did indeed have an issue with the payment method on the web, although I'm not sure why.
But that still doesn't explain why the app is having an issue with the device.
Exact same issue, started yesterday as well.
I ordered a ride via the app on GOS today, no issues.
Sometimes the app feels slow and stutters.
Usually force-stopping and reopening the app will fix it.
If enough time passes, I'll get blank screens, the map wont show up, etc.
I periodically uninstall and reinstall via Gplay every 6 months or so and that seems to fix it.
I run the app on a P7 in a separate profile with Google play et al installed.
Sorry you're having issues, hope this helps
I have another problem with the Uber (user, not driver) app, but since this thread is already active I don't want to open another.
I have a Pixel 7 Pro with the latest GOS, but I experienced this since 2024053100. I have the Google services installed on the main profile, and I installed the apps from the Play Store. I tried enabling all the permissions for the app, but nothing changed.
The problem is this: when I open the app, it correctly shows the start screen, but after only 1 or 2 seconds it automatically switches to a different screen, where I see all the cars in my area. This new screen is exactly like a web app, and by ordering with this interface I cannot pay with Uber credits; maybe this is connected to the payment problems the other users in this thread were reporting.
I think this is not a problem created by the OS, but rather a problem with the app itself. But I can't wrap my head around on why the app would switch to a web app inside the app. Does anybody have any clues?
ToffoliGate I had this issue as well. I'm not using the app anymore, but I had this issue.
ToffoliGate Got the exact same issue recently. Issue was not present when this thread was initially open. Not sure why this is suddenly the case.
DeletedUser88 I have some questions for the people who are facing this exact issue (native app turns to a web app interface) in order to troubleshoot the problem further.
1) Did you download the app in the main profile or a secondary user profile?
2) Did you install the app from Aurora Store or from the official Google Play Store?
3) Are all sandboxed google play services installed and given the network permission?
4) Did you experiment with turning "exploit protection compatibility mode" on?
Here is my answers to these questions:
1) Secondary profile
2) Aurora Store
3) Yes
4) Yes, did not yield any differences.
RRZishe Interesting. Are you using a VPN?
Relevant discussion on the Uber subreddit. Our bootloader is locked though. Can apps detect if the bootloader has ever been unlocked and then restrict features based off of that?
Update: It seems Uber has implemented the Play Integrity API which is quite unfortunate. I have sent an email to their support team with a link to the Attestation Compatibility Guide as recommended by the GrapheneOS developers. I suggest other people do the same to pressure Uber into removing the Play Integrity Checks.
Just adding another data point. No solutions.
Hi! I'm one of those who was also affected by the Uber web app issue early this month - saw the web app load for a few days in the native Uber app, but I don't remember how it was fixed for me. I think it lasted for about 3–4 days after which it was fixed.
Unfortunately I don't have much data/timeline on when exactly this started and when it was fixed, since I was travelling in those days and I just ended up using my friend's phone for our Uber purposes.
I know for a fact that the issue started happening immediately after I updated the Uber app one of the days during my travel. Immediately after the app update I started seeing the web app. I could have tried to downgrade the app and debug it, but I didn't have enough time back then during my travels and just let it be.
But for now Uber app loads fine for me(i.e. no web app) and I've been using it for 2 weeks now with no issues whatsoever. (besides the crazy battery drain while using Uber app - it's like 5% every 10 mins. lol)
And I've failed to reproduce the error again, so I could not report it.
If it helps, my details:
Device - Pixel 7
Profile - Main
Store - Aurora
Uber - 4.531.10001
Exploit Protection Compatibility - OFF
VPN - None
Would you mind checking the logs of Uber app in the 'View Logs'? It might give us an idea on what's going on.
I'm not sure if the logs contain anything sensitive. If not, maybe you can post the logs here and a kind soul can help us debug?
Edit:
Another data point
A friend of a friend working at Google who was testing Pixel 9(yes not a typo) was also seeing this issue during our travel. He mentioned it might be because P9 wasn't released yet (or something, don't remember exactly). But he also mentioned he'd been seeing that Uber issue since Day 1 of his P9 use and he just got used to it. This was about 3-4 weeks ago. I'm not sure of his current status
jagorom515 I have logs ready to post but I am not sure if they contain sensitive information or not. I made a post asking about the potential of accidentally sharing sensitive data in logs and what I should look out for but no one replied. I'll bump the post and see if anyone replies this time. It is strange that the issue was occurring on the Stock OS on the P9. Maybe because P9 wasn't released yet so it doesn't meet the Play Integrity checks? I'm not sure.
Edit: Has anyone on the GrapheneOS team recieved reports about this elsewhere? I'd like to know if the team is aware of this issue or not. Thanks.
A little update. Since the start of August 2024, the app seems to be working correctly again.
I know a guy who knows a guy who works at the Uber headquarters, and it was confirmed to me that they use Play Integrity API. But it was also confirmed that some engineers had some problems with the app too (and some even use GrapheneOS), so it might be that they reverted some of the checks of the Play integrity API. But I don't know this for sure.
I also wrote to them about this issue, pointing to the excellent GOS guide for using hardware attestation instead of google's own proprietary crap. Everyone should write them telling about this, and indeed to any developer that's using or plans to use google's own broken attestation API, that really does not do anything good and does everything bad, such as lowering security and locking the app for only "google approved" devices.
Here you find a logcat of the app when it opened the "webapp" interface: https://drive.proton.me/urls/YAZ62P8JC0#QfPy8SGd8e3m
And here is a more recent logcat of the app that now appears to be functioning correctly: https://drive.proton.me/urls/YM2Y268RT4#DklmQvCg3NzQ
(they're both txt files)
Maybe I found something related to the app not finding some component and switching to the webapp view. But it does not seem to be correlated with some Play Integrity API (or, at least, to be loosely correlated with it, and rather more with the GPS service). But I know very little about Android development, so I might (very likely) be wrong. From the logcat:
--------- switch to main
06-26 16:43:47.009 28568 28754 D onProviderDisabled (OsLocationListener.kt:40): gps
06-26 16:43:47.014 28568 28651 D updateListener (Listeners.kt:40): client com.ubercab added listener class com.google.android.gms.internal.location.ah, Request[@+5s0ms HIGH_ACCURACY, minUpdateInterval=+3s0ms] provider app.grapheneos.gmscompat.location.OsLocationProvider@252846b listenerCount 2
06-26 16:43:47.014 28568 28754 D onProviderDisabled (OsLocationListener.kt:40): gps
06-26 16:43:47.015 28568 28568 W FirebaseRemoteConfig: An entry in the defaults XML has an invalid key and/or value tag.
06-26 16:43:47.015 28568 28568 W FirebaseRemoteConfig: An entry in the defaults XML has an invalid key and/or value tag.
06-26 16:43:47.015 28568 28568 W FirebaseRemoteConfig: An entry in the defaults XML has an invalid key and/or value tag.
06-26 16:43:47.041 28568 28740 D d : loadedRenderer: LATEST
06-26 16:43:47.041 28568 28740 I GMS RENDERER: LATEST
--------- switch to events
06-26 16:43:47.045 28568 28568 I viewroot_draw_event: [window=VRI[RootActivity],event=Canceling draw. cancelDueToPreDrawListener=true cancelDueToSync=false]
I will be updating this thread if any new info occurs to me.
Other GOS users: do you still have any issues with the Uber app at the moment?
