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?
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.
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).
3.2.1 launches on a Pixel 6 on a profile with Sandboxed Google Play.
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?
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.
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?
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.
3.1.1 works on 20231023 on the Pixel 8.
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.
I can confirm that 3.2.2 works on 20131023.
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.
Pixel 8 UD1A.230803.041.2023102300
Mitid 3.2.2
Works totally fine. I do not have a Danish ID so I didn't proceed too far into the app but I can confirm that the app opens and seems to behave quite nicely.
lbschenkel I can also confirm 3.2.2 fully works on the Pixel 8 with build UD1A.230803.041.2023102300
is it just me that cannot get it to sign in?
pixel 7 pro
when scanning the passport it just fails after a minute or two.
tried from aurora aswell as google play store.
gps has network access.
everything is updated to latest as of now, which according to the gist should work?
Version 23.35.14 (190400-561707045)
LGXerxes I just to point out that if you can reach the point of scanning the passport without the app complaining that you are rooted, the app is "working" in the sense that it would have behaved the same way as stock Android and it is not refusing to work due to detecting something different with GrapheneOS.
That said, which country's passport are you trying to read? Is it failing to read it at all or does it give an error after reading? Can you try to read your passport using ReadID Me to see if that works?
Although MitID claims to support any biometric passport, I have multiple citizenships and the app just works for one passport but does not work for another: it reads the passport but then it shows an error and does not proceed. I know it is the app rejecting the passport and not the passport failing to read because the passport can be read successfully via ReadID.