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.

        Proxima Can't test using QR-code right now but logging in to my bank on phone with MitID worked just fine

          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?).

            I have pixel 8 and works fine.

            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.

                Proxima Face recognition?

                Maybe try going to MitID logs and se if anything useful is there

                  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.

                                  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?

                                      lbschenkel Sorry to say, now I can't get past the face recognition state, the APP just crashes and every thing else I have tried don't work either.

                                          Proxima OK, I want to confirm that you have done this:

                                          1. Uninstalled the app (*)
                                          2. Installed the app again, but did not open it (*)
                                          3. Opened the app info and enabled the switch Exploit protection compatibility mode
                                          4. Opened the app and went through the motion of scanning the document

                                          At least for me, I was able to do it once I have done the above. The error mentioning that the device is "rooted or compromised" no longer shows up at the final activation step.

                                          (*) Reason for this is because I saw in the logs for my MitID account mentioning of "permanently blocking the installation" when I've done the failing experiment, so better to start fresh with a new installation.

                                              lbschenkel When I switched off Exploit protection compatibility mode. I was again able to get to the error message.

                                              Every time I make a try, I force stop the APP, Clear cache, Re-install the APP, first then I turned on the Exploit compatibility mode.

                                                  Proxima All right. Well, it's weird. We'll need to wait for other GOS users to try and chime in.

                                                  P.S.: You didn't use the word "uninstall" but "re-install". In case you didn't uninstall the app, please make sure you did that just to eliminate all doubt.

                                                      Proxima Thanks for that. The wording strongly implies that they decided to use Play Integrity for new activations since June 12. But then again, how did it work on my device after setting the compatibility options? Was it a fluke?

                                                      We will need other reporters to get a complete picture of what is the situation. The complication now that the check is at the time of activation is that we need local users to test, as they need to scan their documents and to have a CPR number. Before, since the app checked at launch, anyone could install and launch and verify if it was working.

                                                      I may try again with my device but I'm a bit wary to do it because I'm actually doing activations and revoking them and this is tied to my real identity, and who knows if that might trigger some anti-fraud algorithms.