Government issued app breaks because of invalid google libraries

@oliveradams thank you so much for sharing that you managed to get your banking app to work by using a different browser to log-in. I did the same for my banking app - and it worked!! :tada:

Like you, I didn’t manage to fool MobilePay though.

Side note: It’s funny that the company, that stores my money and payment cards let’s me install their app on a rooted phone, but the place that just stores a reference to them does not :upside_down_face:

I found a solution for mobilepay!
If you uninstall the pre-installed e os browser, then Mobilepay defaults to the kiwi browser if that is installed and you can then create your account using MitId.
You can always reinstall the default browser again if you like.
Works for me.
A guide to uninstalling standard apps: Uninstall default apps - #29 by AnotherElk

2 Likes

@oliveradams thank you so much for sharing - it works!

I took these specific steps to get MobilePay working:

  • Follow the guide, that @oliveradams mentioned to install the required tools on my computer
  • On my phone: Enable Developer Options and enable USB-Debugging
  • Connect phone to computer using USB-C cable
  • On the computer: In a Terminal, run:
    • adb shell pm uninstall --user 0 foundation.e.browser
  • On the phone: Install MobilePay
  • Log-in with my existing credentials etc.
  • Make a transfer
  • Works like a charm! :tada:

I have Brave and Firefox installed and Firefox set as the default. MobilePay decided to use Brave for the MitID login :person_shrugging:

I will leave this thread open as the original problem of the MitID app not working (refuses to get activated) still persists. Having MobilePay working is a huge improvement for me though :sparkles:

3 Likes

Great! Glad to hear it. :grinning:
After updating the Mobilepay app, I had the issue with not being able to login with my pin code again.
But after reinstalling the Mobilepay app it worked again. ( you can actually just delete cache and data from the app. No need to reinstall in my case)
Not sure if this is a one-off issue or if this will happen each time we update the app. But at least we have a workaround. :smiley:

1 Like

That’s very useful follow-up info :clap: I’ll make sure to keep an eye on this when I update the app.

Hi,

this is wierd, because some time ago I installed /e/os on my old OnePlus6 and had MitID, banking app, MobilePay working just fine. I bricked it recently (ever the tinkering fool), so I was contemplating installing /e/os on my Pixel 8 Pro…
But this thread… damn. Was really looking forward to it working easy peasy, but it seems something has changed.

@fonhom This may not be useful to you, but it’s another data point.

I run IodéOS (another privacy-respecting custom ROM, based on LineageOS for microG).

I was able to install the MitID app from Aurora Store. It ran with no problems, and I was able to proceed with the activation, as far as scanning my passport (which I couldn’t do because I don’t have a Danish passport).

I hope that is some use

1 Like

Hi guys.

Just wanted to first of all thank you all for making this work!

I’m a complete noob to all this, but given recent geopolitical events, I wanted to free myself from google and Apple. So I’m now running Ubuntu 24+ on my Macbookair with the T2 linux kernel, and moved to a Nothing Phone CMF 1, on which I flashed the community build of e/os on via the ubuntu terminal.

I assumed this would leave my phone rooted and I was unable to get Mitid and Mobilepay working, experiencing the exact same issues as others have posted here.

However using Devcheck Devices & System Info app, and running “adb shell su” command from terminal, both showed my phone without root.

Without any other actions, I simply ran the command the Fonhom suggested, re-installed Mobilepay and voila - amazing!

Thanks again everyone, and let’s hope for a solution with NemId.

Martin

1 Like

This topic was automatically closed after 90 days. New replies are no longer allowed.