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".
Status of MitID app
zfnmxt Right, I was not aware. I thought that you perhaps were an early adopter.
5 days later
- Edited
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?
- checking if MitID 3.1.1 still works (I expect it will, there is no reason to break)
- 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.
- Edited
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
9 days later
- Edited
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.
lbschenkel thanks for your input!
it seems theat it is just not working for pixel7pro?
as on my xiaomi mi9t pro on the same mitid version scanning of the passport works.
it is a Danish passport.
and reading with ReadID me, works fine :(
LGXerxes Does it fail to scan at all, or does it show an error after scanning?
lbschenkel
it scans, the dots fill up. but it is thinking.
then at some point it complains about to many tries and i have to start over again.
my thought was that it tries to validate some data somewhere but it is not able to reach it. but i think I've removed all hardening on mitid and give alot of accesses to GPS and play store.
11 days later
Just a FYI: new MitID version 3.2.3 works in GrapheneOS versions 20231031 and 20231115.
I had the same issue with MitID on GrapheneOS. It said my device is rooted, but it's not. I updated GrapheneOS recently, so maybe that's the prob. Can someone with an older GrapheneOS version check if MitID works for them It seems like there might be a hiccup with the MitID app on GrapheneOS. The message about the device being rooted popped up, but the phone isn't rooted. Could be an update thing. Maybe someone with an older GrapheneOS version can check if the app works without showing that message? If it's just happening after the recent update, might be a bug. Could really mess things up for folks in Denmark if it's not sorted out.
Nowediff Which version of MitID and GrapheneOS? This should not be happening in recent versions of MitID:
https://gist.github.com/lbschenkel/4199be415f2a139b64688ae74c92a7fc
I am no longer able to login to the site with MitID. I can enter the code of MitID but nothing happen afterwards.
- Edited
I can confirm that MitID login flow is currently broken in Vanadium: the MitID app itself works but when control is back to Vanadium, it does not redirect to the post-login page.
I could reproduce this when trying to login in mitid.dk and when trying to login in my bank app. Switching default browser to either Firefox or Chrome fixed the issue.
I tried to relax every possible setting in Vanadium but I could still not make it work.
Note that I am 100% certain that Vanadium used to work months ago. In fact, to login to my bank app I was forced to change default browser from Firefox to Vanadium because with Firefox it always got stuck in the post-login phase, in a similar way that it is happening now. Now the situation has reversed.
I am not quite sure if this is due to something changing in Vanadium, or due to the changes that happened with the MitID login flow when the barcodes were introduced. It used to be that you could login by entering your name and manually switching to the MitID app to authenticate; now you are forced to push the button to open the app from the login form. This change might have been the one that stopped working in Vanadium for whatever reason. I'm inclined to say that either way, this is a Vanadium bug.
[deleted]
lbschenkel This may be because of some Vanadium patch for privacy