I have now activated the Code Display. The process of activating is pretty straight forward, although I had to create a= Password, to be able and use the Code Display. Password options were from 8 to 64 characters, with seemingly no limitations within the ASCII characters. The first attempt using the Code Display was odd, as it did not log me in to e-boks page, but after the last step and confirmation on the screen, it just left the final 'pop-up' screen of the MitID process completely empty (white). Used another browser and then it worked fine.
Tried some browsers in Linux Mint Virginia 21.3 FF and Floorp and W10 chrome and FF
Tomorrow I will request to add a 2nd device to have MitID active (my GOS phone). So, up to now, all seems fine :)
Status of MitID app
Sadly, it failed for me. GOS 2024060500; GPServ. 24.15.17 (190400-626366329); GPStore 41.3.25-31 (PR) 640531013); GSF Installed v14; GmsCompatConfig Installed v117 and v3.3.5 MitID apk. Network services were on for GPServ. Downloaded apk, install went ok. Opening app also fine, scanning the QR from phone to copy to new phone the app notifies me that it will not install further, due to possible rooted phone. grrrrr This is on a alt. account on my P8pro, not my main account. Alas...., I will give up for now. I have the Code Display, my old phone with working app. I will survive without it... thanks all for info/likes and support. Log is saved, if a developer wants to take a look. , pm me.
- Edited
MentalM Do you have "OEM unlock" enabled in developer settings? The app checks for that. You have to leave that off. The bootloader also needs to be locked.
lbschenkel Sorry for being a bit late, but I have a family wedding coming up and that takes lots of time... Both OEM and bootloader are off. I made sure of that when re-installing GOS. Only a few options in Dev options are enabled : Verify bytecode of debuggable apps, WiFi scan throttling, Mobile data always active, Tethering hw accelleration. I have not yet looked at those, as they are in the Dev options. If they should be disabled let me know plz. at the moment, I have the code display and my old phone. So I can manage. Maybe one day, I will try again.
- Edited
MentalM There is something very different with your installation. I use MitID daily and many other users have reported that it works as well. There is not a single report, except yours, of the current version of the app refusing to work.
Note that once MitID flags an installation as "bad", it will never recover. You need to revoke and reinstall. So whatever the app is saying now is not necessarily indicative of the current state, it might as well be a past bad state.
- Edited
lbschenkel I have just bought a Google Pixel 8a and trying to install MitID. But after scanning the QR code, the screen turns red and the following messages are showing.
- Your phone or tablet is rooted.
- The APP are installed outside of Google Play.
- Your Google Play version is to old.
- Your phone do not support Google Play Services.
I have installed MitID with Google Play.
I have checked the Google Play version.
Do you have any idea what is wrong?
Proxima Not really. That looks really odd. I just installed MitID from scratch on a fresh user profile, and everything worked. I could do all activation steps.
Just double checking: Are you sure that when you installed for the first time, did you satisfy all the criteria? Locked bootloader, OEM unlocking disabled, Google Play Services, and installed from Google Play? Because if MitID "trips" due to some failing check, it will permanently taint that installation. You will need to uninstall the app and install it again.
lbschenkel Hmm ok, thank you.
Yes bootloader is locked, OEM unlocking is disabled, deleted chache, Re-installed and tried verifying with passport, same thing happen.
But thank you for answering.
It looks like both reports of MitID not working are with the Pixel 8 family? Do we have any other MitID users with Pixel 8 who can share their experience?
@MentalM and @Proxima: can you confirm if the app complains immediately after launching, or later? If later, aren't you able to enroll at all (if not, which exact step fails?) or are you able to enroll but not authenticate (again: which step?).
lbschenkel I have a Pixel 8 pro and it works
I have pixel 8 and works fine.
- Edited
lbschenkel I have a Pixel 8a and I still can't get it to work!
Trying to verify with passport. In the next after face recognition, it comes up with
- Your phone or tablet is rooted.
- The APP are installed outside of Google Play.
- Your Google Play version is to old.
- Your phone do not support Google Play Services.
- Edited
Maybe this have something to do with it. The build number of my GOS is 2024062000.
It is outside the scope that are listet on your Github lbschenkel
Proxima I have the same version installed. I only update the gist opportunistically, not on every new LOS version.
lbschenkel I now managed to replicate your findings. I installed the app in a completely new user profile and tried to activate it. Went through all the steps and in the final one, I got the message you're referring to.
So it looks like the app is doing different — and more stringent — checks at activation time than at launch time. So if you are like me and have a profile already activated, the app continues to work but apparently you can no longer activate it for new installations.
I'm not sure exactly what the app is looking for. If it's Play Integrity, then it's game over.
With that said, perhaps this check is only for the passport/ID scan flow and if you manage to activate your MitID via an alternative way (such as a visit to the citizen center), the app perhaps can still work. That will need to be investigated.
I'll put a prominent notice in the gist about this.
lbschenkel @Proxima: can you do some experiments? Can you check the gist and try to install previous versions of the app via Aurora, and check if you can activate through them? Keep going until you find one that works, and if you do, report which version that was.
Unfortunately I can't do that experiment myself because I have a single GOS device which is my daily driver, so I can't downgrade the app and I'm not willing to lose my activated MitID.
- Edited
lbschenkel @Proxima: before you waste a lot of time doing this experiment, actually try something else first. Open the app properties for MitID and enable the switch named Exploit protection compatibility mode. Make sure to force close the app and try activating again.
I have done that in a new profile and the error no longer showed up for me. Hopefully it will do it for you as well, and then it's good news as we do have a workaround to keep MitID working and they didn't decide (yet) to pull the trigger on Play Integrity.
Can both you and @MentalM try this and report back?