BankID stopped working, possibly after version 4.7.7

engstat

I can also confirm the problem with 4.7.7, and that using Aurora and downgrading to 4.7.6 (1748331101) temporarily solves the issue. I will have to use a separate device for BankID if this is not fixed by the developers, as I don't want to run a outdated client to log into my bank and other related services.
There might also be a way to contact the developers at teknikinfo@bankid.com according to https://support.bankid.com/en/technical-issues-and-problems/beta-test-bankid-for-android,

DeletedUser370

engstat There might also be a way to contact the developers at [teknikinfo@bankid.com](mailto:teknikinfo@bankid.com) according to https://support.bankid.com/en/technical-issues-and-problems/beta-test-bankid-for-android,

That is the Swedish BankID app, an entirely different app and it's not the same developer.

TrustExecutor

DeletedUser370
Maybe it is a good reason to already now contact the swedish counterpart and urge them to not implement Play Integrity API, but instead use hardware attestation as per GrapheneOS instructions.

engstat

DeletedUser370 You are absolutely correct

DeletedUser370

Ok, to summarize what we've found so far:

Version 4.7.7 is gradually rolling out to all users
4.7.7 is not crashing on stock Pixel OS
Enabling exploit protection compatibility mode does not fix it
Disabling exploit protection compatibility mode and enabling secure app spawning and then rebooting does not fix it
It's unclear whether or not the app is now enforcing Play Integrity in the mode where it disallows alternative operating systems, or whether this is an app bug which arises on GrapheneOS and not stock OS
When 4.7.7 is opened, GrapheneOS displays a notification that the app used the Play Integrity API, but this message also appeared in older versions
We can reach out to BankID by leaving a negative review mentioning the crash in the Play Store entry (without posting a URL; will get the review banned), contact the email address under "App support" in the Play Store entry, and reach out to your bank and get them to forward your feedback to BankID.

Tulips

DeletedUser370
Got same problem here on my xiaomi eu rom (non root) wdck.aw: 00 at wdck.b.a(Unknown Source:172) at wdck.b.b(Unknown Source:0)

Bankid Norway.

ujjayi

Don’t know if it’s relevant in any way, but the error code I got when 4.7.7 somehow was not crashing all the time on my phone was the BID-2033 code that should indicate a bad data connection. Would there be any sense in taking that into account? Because there’s also a separate error for unsupported systems, or rooted and jailbroken systems anyway.

Mengine

A new version 4.7.8 is released and seems to have solved the issue

DeletedUser370

Mengine Can confirm, 4.7.8 works fine for me.

ujjayi

Yep, I even got a mail back from Bidbax, saying he fully supported GOS's mission and a thank you for reporting. What still doesn't work on GOS is "raskere BankID" with biometrics. Not sure if it's some there's some missing permission in Play services (it says to verify biometrics with Play Services on the very top of the last step)

DeletedUser370

ujjayi Yep, I even got a mail back from Bidbax, saying he fully supported GOS's mission and a thank you for reporting.

Was this a representative of BidBax? Not an auto-reply from a machine? I actually didn't come around to send them an email, just a one-star review.

ujjayi

DeletedUser370 yep, was a reply and signature from a person with a name @bidbax.no, clearly not an auto-reply, so that's one good thing 🙂

TrustExecutor

ujjayi

This is awesome.

schklom

To people who have an issue on version 4.7.8: you need to have the base keyboard enabled instead of anything else like Heliboard. Enabling any keyboard other than the base one on the code device authentication phase results in BankID redirecting you to the bankid webpage where it says your device lacks security.

« Previous Page