Parking and paying apps.

anarchosax

First day with GrapheneOS on a Pixel 6a and I am appreciating the help that I am getting so far. GOS is pretty basic, but I think that I can live with it as a point of reference. However, there are two apps that I need to get going right away - EasyPark and MobilePay. EasyPark stalled despite having WiFi. I haven't yet tried using my sim card yet with my Pixel 6a, could that be the issue, as it stops at my phone number.

MobilePay is a different kettle of fish, as it needs to be authenticated with MitID. As I currently have an authenticator for this, rather than the MitID app, I thought that this would be a better solution than having to try to get two apps running. The MobilePay authentication process starts, but keeps spinning its wheels after the one time code. The authentication with MitID is already twitchy, so I am not planning on doing too much experimentation...

Any ideas on either of these app issues?

ErnestThornhill

Have you tried any of the Possible Workaround Solutions found here: https://discuss.grapheneos.org/d/8330-app-compatibility-with-grapheneos?

anarchosax

I seem to have gotten EasyPark working by switching the location settings to precise and temporarily disabling the "secure app spawning".

6yrgfmy7

anarchosax Is EasyPark working for you now? I tried what you proposed but didn't receive the one time code (even after pressing resend). Did you change anything else?

anarchosax

The issue with MobilePay appears to be that it insists on validating using the Vanadium browser, even when I have installed Firefox and set it as the default browser.

Relaks

anarchosax The status of MitId and Mobilepay is that they are very problematically blocking the usage of alternative browsers. Here's an update from the official GOS account: https://discuss.grapheneos.org/d/5391-mobilepay-danish-not-working/23

anarchosax

Relaks Interesting. Thanks for that. I came across the following:
https://github.com/GrapheneOS/Vanadium/issues/421
Unfortunately, the older version listed in the link is not available anymore. It does appear that I have gotten Chrome working in my GOS install. As I am using the MitID authentication device (rather than the app, due to past issues with the app) the verification is slightly different, however in my verification process, it is possible to switch from the Vanadium browser to Chrome by clicking on the three dot menu next to the URL message at the top. Having done that, I was able to successfully complete the verification process. Unfortunately, I also received the following error message:
".mitid.nonce cookie missing in HTTP request (authority 'https://mobilepay.criipto.id')"

i have seen in the news today or yesterday, that some changes were being made to MobilePay due to security issues. Perhaps these problems are part of the issue. I just don't see a solution on the horizon, unfortunately...

anarchosax

On a side note, the irony is not lost on me, that what is probably the most secure version of Android out there is experiencing difficulties with NemID and MobilePay security changes, when these apps are pretty much ubiquitous in DK. Isn't it possible to work with the NemID and MobilePay developers? I think issues may get increasingly difficult on this front when the EU implements EU wide personal digital wallet and security measures...

other8026

anarchosax Isn't it possible to work with the NemID and MobilePay developers?

From what I can tell, they're doing things that don't make sense. If you read further down the issue that you linked, it seems the way they're trying to "secure" their app is questionable.

I'd pay close attention to this comment: https://github.com/GrapheneOS/Vanadium/issues/421#issuecomment-1866495979

anarchosax

other8026 Wow, I got it working. Thanks for the heads-up. As mentioned in the comments, disabling the default Vanadium browser and setting Google Chrome as default works.

Thanks for all of the replies from everyone.

First thing to try tomorrow is to get my MitID app working on GOS.

anarchosax

I am trying to tag this topic as solved, but I don't see an option. Am I missing something?

other8026

anarchosax I am trying to tag this topic as solved, but I don't see an option. Am I missing something?

You're not missing anything. Only mods can do that, so I've marked it solved for you!

Elf_Navy

I've got a similar issue but also cannot solve it using this method.
(1) Installed Easypark V7.35.2 using sandboxed Google Play Store (with network and sensors enabled on Play, Play services, and Play services Framework)
(2) Disabled secure spawning and enabled compatibility mode on Easypark
(3) Rebooted
(4) Cleared Cache and storage from Easypark
(5) Gave Easypark all permissions (at first only network & precise location, and additionally when that didn't work all the others it requested, such as nearby devices, contacts, etc.)

But when I try to log in it just shows a red warning underneath the email/username field which says: "check-your-connection", which is the same text I got without without any of these interventions.

Can I get some help? I'm on a pixel 8 pro with GrapheneOS buildnumber 2024062700. Could post logs if needed.

PaulDavis

Elf_Navy why does it need access to your contacts? I hope you scoped it

TrustExecutor

Elf_Navy Try give sms and phone permissions to Play Services.

Elf_Navy

PaulDavis Thanks for the advice! Currently don't have any contacts as I'm still setting up my phone, so figured that just giving it permission to test if it will log in won't cause harm. Unsurprisingly for a permission that I cannot justify this app having for its intended use, it did not help giving it Contacts permission.

Elf_Navy

TrustExecutor This (in combination with the previous steps which I had not yet undone) does not seem to work either.

After trying to sign in to easypark with the additional play services permissions enabled (which failed), I also put my sim card in (which I had not done before, since I could do the setup with wifi) just to be sure. And I rebooted just to be sure. But trying to log in to easypark still fails.

Any other advice?

Stephan-P

Possibly not the solution you're looking for, but after struggling with the Easypark app for some time, I decided to look around for an alternative and found Yellowbrick to be quite easy to install, functional within GOS and in fact a teeny bit cheaper as well.

Poorly coded apps depending on Google Play attestation methods are indeed a pain in GOS and hurting its adoption.

Elf_Navy

Stephan-P I'll look into it. Thanks for the suggestion. I may end up having to switch so it's good to have alternatives available.

I'm experiencing similar issues logging into a few other apps that I consider less essential (Udacity, MoveMove), so if a solution can be found I'm sure that would be helpful to the GOS community as a whole, but there may not be one. Either way, those other apps I can just use without logging in or through a web interface, so I'm only mentioning them for completeness.