lbschenkel I just updated to 3.3.1 and hence my post above yours, I still hare trouble getting MitID to work in my main profile without Google Play.

In my second profile with google play services, MitID version 3.3.1 works.

Vanadium: 122.0.6261.43.0
GOS: 2024020500

Update: Actually it seems that 3.3.1 partially solves my problem in my non-GSF profile. Now I can at least approve login requests made from another device. Still no luck with login requests made from vanadium though.

      I upgraded mine to 3.3.1 and I can confirm that authentication is working when using either Vanadium or Firefox.
      Updated gist.

      trilogy6202 I never attempted to use MitID without Play Services, so I can't really help. Another user did try and it looked like Play Services was only needed for activation, and not authentication, but it's also possible that things have changed since then or there will be bugs due to being an unsupported/untested configuration (from MitID perspective).

          lbschenkel This is still true. I installed GPS to make MitID work, then after signup, I uninstalled GPS and the app works for authentication. Last time i updated the app though, with GPS installed, it broke the app.

          So my conclusion from tests are that GPS is needed for initial launch/after update - but not in general use
          The jump from web to app though does only work sometimes, which is why it makes sense to set method to numbers instead of QR code

          Hope this helps

              @lbschenkel I don't need to use this app but I just have to say big thanks for putting in this amount of commitment to solving this problem.

              lbschenkel To tell the truth my MitID app hadn't been working for months (I would get an error saying "Bad connection to MitID").
              Fortunately I had followed your suggestion of getting a code viewer long before this happened.

              But Duckduck 's advice of temporarily reinstalling GPS after updating the app has restored it to life. Thank you very much!

              It does however seem that now (unlike what was the case when I posted my previous comment) the Google apps need network permission when you first open MitID after installing/updating. As soon as MitID is in a working state the Google apps can be uninstalled / have their permissions revoked (like Duckduck said).

                  a month later
                  a month later

                  I can confirm the findings by others. GPS needs to have Network Permission while setting up the MitId-app, but GPS does not need Network Permission after initial setup**.

                  ** Scanning QR-codes to authenticate on another device, e.g. desktop or laptop, works without Network Permission to GPS. Swiping to authenticate on the same device the MitId-app is installed on (phone with GOS in this case) only works for me when GPS have Network Permission. Without Network Permission for GPS I'm offered to scan a QR-code (which I can not do on the phone's screen, with the phones camera ...). The swiping issue might the issue mentioned by lbschenkel

                    2 months later

                    lbschenkel Hi again, after a while. I have now all my apps running on my GOS phone and only MitID to go. I have received the (made in China :( ) code dongle. And will activate that in the next 48 hrs, as they have a 24 hr cooldown on adding/changing the MitID device options. But, during my trip through the website, I noticed that it is apparently now possible to have MitID active on 3 different devices. (they write the option of own phone, tablet and your workphone. I seems to be just a matter of applying now on their website and 'add' an extra phone. So my plan is to activate my code dongle (As a back up device), test that for a bit. Then I will attempt to apply for adding the MitID app on my GOS phone. I will post my results here in this thread, as I go along.

                      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 :)

                      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.

                        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.

                            5 days later

                            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.

                                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.

                                    4 days later

                                    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.