Me as well. Though i cannot get the new redirect function to work to open the app

3 months later

Hi there

I’m a new GrapheneOS user who’s trying to de-Google as much as I can, and I have some of insights to add.

You actually DO need Google Play Services in order to activate your MitID app, but when that is done, GPS can be safely uninstalled. MitID activation is the process of registering the app as a valid authentication device, and you need your username as well as a temporary password from mitid.dk in order to do this. The GPS requirement only becomes apparent when you have correctly entered your username and the temporary password, where you are greeted with this dialog:

“MitID app can not be activated
MitID app can not be activated without Google Play services, which are missing from your device.”

So we’ll need GPS from the GOS Apps app, though all the Google apps can be installed without giving any permissions whatsoever (not even network), and MitID will accept that. When you reach the screen about notifications, just close MitID (if you accept, the app will freeze, but you can still just close it at that point). Next time MitID is opened, it’ll be ready for use and the Google apps you installed can be uninstalled with no issue (so I’m guessing this method is just as good as if the Google apps were never installed, since no network permissions were given? I’d need an expert to confirm that).

I know this thread is about MitID, but I’ll quickly make a note about some other apps that use MitID as well: Danske Bank, MobilePay and Digital Post all work without Google apps installed (MobilePay will claim that it needs GPS, but works fine without). e-boks does not work without GPS, as the app crashes the moment you log in (I did not test how much it takes to get e-boks working).

Finally, thank you @lbschenkel for maintaining this knowledge base. Since MitID is mandatory in Denmark, having a source like this is great for Danes who are unsure if they’ll even be able to use a privacy and security focused OS. It certainly helped convince me.

Model: 7a
Build number: TQ3A.230805.001.2023080800
MitID version: 3.1.1 (85)

    BetaCube Thank you for the remarks regarding initial activation; I have updated the gist to reflect that and link to your post.

      a month later

      BetaCube Great advice, thanks a lot. I really missed having mitid on my main profile and I think having GPS installed for 5 min. w/o any permission whatsoever, isn't too big of a compromise, or at least it's more than offset by the convenience of having mitid in the main profile.

      Regarding e-boks, I tested every GOS-specific settings I could think off like 'hardened app spawning' and 'native code debugging' and I even tested it on a profile with GSF (but without GPS) and e-boks still crashes within 1 minute so I've given up on having it installed on my main profile.

        6 days later

        There is a new version of the MitID app on the Play Store: 3.2.1.

        Any brave soul that wants to be a guinea pig and install it and report if it opens, or if it complains about anything?

          lbschenkel tried twice. Works, no issues discovered. Newest stable GraphenOS version.

              3.2.1 crashes on start with a segfault on shiba build 2023101900:

              type: crash
osVersion: google/shiba/shiba:14/UD1A.230803.041/2023101900:user/release-keys
package: dk.mitid.app.android:94
process: dk.mitid.app.android
processUptime: 0 + 0 ms
installer: com.android.vending

signal 11 (SIGSEGV), code 2 (SEGV\_ACCERR), fault addr 0x00000079de64f000

backtrace:
      #00 pc 000000000000e14c  /data/app/~~IeO11yeB0d7qTFXKznSNag==/dk.mitid.app.android-QzCC-8Clbbslr3rX4p3hQw==/base.apk (offset 0x27f5000)

              I can provide (specific) info from a full bug report if needed. 3.2.1 worked fine on shiba with the stock OS.

                zfnmxt it seems to work for the previous user comment on it. Have you tried any of these workarounds.

                Grkrz tried twice. Works, no issues discovered. Newest stable GraphenOS version

                Also, I'll be adding a couple more possible solutions to that README and I'll update it on the front end side of things on privsec.dev/banking later today.

                For now, here is this suggestion too:

                Make sure native debugging is enabled, and if that's not the issue then try the per-app exploit protection compatibility mode. If neither of those work, leave both enabled and try disabling secure app spawning temporarily to see if that gets the app working after a reboot. You should leave secure app spawning enabled but it's worth seeing if this GrapheneOS feature is the cause of the compatibility issue. The app may be detecting the different spawning mechanism and refusing to run with it.

                      akc3n

                      Thanks for your reply. Unfortunately, nothing you mentioned fixed the crashing. Since I didn't add it in my original post and the workarounds you mentioned mention it---I did install from Google Play.

                      It could be an issue specific to the GOS builds for the Pixel 8/8P (if anyone has an 8/8P please chime in with whether or not MitID segfaults for you).

                        Happy to report that version 3.1.1 works on the Pixel 8. (See the gist in the original post for the requisite version numbers for manual download from Aurora.)

                          zfnmxt That's great to hear. Glad you got it working.
                          Quick side note, Please keep in mind that apps can check if they were installed from the Play Store and can choose to refuse to work if they were not installed from the Play Store.
                          Recently mentioned on a tweet: Twitter / Nitter

                          Edit: strike through sidenote

                          For App compatibility with GrapheneOS, please see a detailed recent post explaining the context of this comment here on point #0 - https://discuss.grapheneos.org/d/8330-app-compatibility-with-grapheneos

                            Tried once more to make sure it works, and it does.
                            Version 3,2,1
                            Pixel 6
                            GOS 2023101300

                            I can confirm that it works for me as well, updated the Gist.

                            zfnmxt: My understanding is that you're on non-stable version of GOS, correct? Have you had the chance to test 3.2.1 with stable 2023101300 in the Pixel 8? I'm interested to know if this crash happens with the stable build as well, because then I want to document that in the Gist.

                            Anyone else here with Pixel 8 and stable build who wants to test version 3.2.1 and report what happens?
                            And alternatively: anyone else here running the alpha build and not Pixel 8, do you want to try out 3.2.1 and report?

                                lbschenkel

                                Have you had the chance to test 3.2.1 with stable 2023101300 in the Pixel 8?

                                There is no 2023101300 build for the Pixel 8 and support for it is still only "experimental".

                                    zfnmxt Right, I was not aware. I thought that you perhaps were an early adopter.

                                      5 days later

                                      zfnmxt I noticed that the latest 20231023 release is no longer experimental for Pixel 8. Are you willing to upgrade to this release and test the two scenarios below?

                                      1. checking if MitID 3.1.1 still works (I expect it will, there is no reason to break)
                                      2. upgrading to MitID 3.2.1 to see if it works now

                                      Naturally you may lose your MitID if step 2 does not work, will need to uninstall, reinstall 3.1.1 and re-enroll. I'm not sure if you're willing to do that.

                                      Otherwise it would be nice if anybody who has a Pixel 8 + 20231023 could try installing MitID and reporting if it crashes or if it shows any error message during startup.

                                        1. 3.1.1 works on 20231023 on the Pixel 8.

                                        2. Note that 3.2.2 was just released with "Bugfixes for Pixel 8/8A + Android 14" as a release note (I guess they mean 8/8 Pro). Unfortunately I can't try the update (nor 3.2.1) until my backup MitID code generator arrives. Should be soon; I'll update then.

                                        Curiously some users on 8/8 Pro are reporting crashing on 3.2.1 like I saw, presumably on the stock OS, so maybe the issue was GOS-agnostic afterall.

                                        Someone with Pixel 8 please report if version 3.2.2 works with 20131023. Given that this particular version was released to address issues with Pixel 8, I am assuming that it should work.