TL;DR
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
A report says ASN’s Android banking app blocks devices running non-Google operating systems, including GrapheneOS. The supplied source does not include a statement from ASN confirming the policy or explaining its technical basis; a separate debate about security checks concerns EPI and Wero, not ASN directly.
Dutch bank ASN reportedly blocks its Android banking app on devices running non-Google operating systems, including GrapheneOS, according to a report pointing to a GitHub compatibility issue. The supplied material does not include a direct statement from ASN, so the bank’s exact policy, reasons and scope are not independently established here.
The report describes an access problem for customers using Android systems that do not rely on Google’s software services. It specifically names GrapheneOS, a privacy- and security-focused Android operating system. The material does not provide the app version, error message, affected device models or a test record confirming how widely the block occurs.
The linked discussion centers on the security checks used by banking and payment apps. One contributor argues that Android’s hardware key attestation can provide evidence about verified boot and the identity of an app, while Play Integrity supplies a separate verdict through Google. That technical argument is the contributor’s account, not an ASN explanation, and the discussion as supplied does not establish which checks ASN uses.
The source also recounts a separate exchange with EPI, the operator of Wero. According to the contributor, EPI said hardware key attestation does not establish app or operating-system integrity and cited that as a reason for using Play Integrity. The contributor disputes that description. This exchange concerns EPI and Wero; it should not be treated as confirmation of ASN’s policy or rationale.
Banking Access Beyond Google Android
If the reported restriction is in place, customers using GrapheneOS or other non-Google Android builds may be unable to use ASN’s mobile banking app, even if their devices support Android applications. That can make access to routine banking depend not only on having a compatible phone, but also on its software configuration and the checks an app developer accepts.
The dispute matters beyond one bank because app-based security screening can affect whether people can use financial services on privacy-focused or differently configured devices. Play Integrity is a Google service; hardware key attestation is an Android mechanism that developers can validate themselves. Each approach has different implementation and maintenance requirements, but the supplied discussion does not show which one ASN uses or whether another check is responsible.
For customers, the practical question is whether ASN offers another supported way to access accounts. For developers and regulators, the broader issue is how a security policy balances fraud prevention, auditability and compatibility. The available material does not establish that ASN’s reported block is a security judgment about GrapheneOS itself.
Popular right now
Bose QuietComfort Ultra Earbuds (2nd Gen) – Wireless Noise‑Cancelling Earbuds with Mic, Immersive Audio, USB‑C Charging, Up to 6 Hours Batte
Ninja CREAMi Scoop & Swirl 13-in-1 Ice Cream and Soft Serve Maker (NC701)
Dyson Cyclone V10 Origin Cordless Vacuum
As an affiliate, we earn on qualifying purchases.
The Attestation Debate Behind the Report
Android’s key attestation API can return a certificate chain containing information about a cryptographic key and, depending on the device and implementation, details such as verified boot state and the app identity associated with key creation. An app or service that relies on this evidence must validate the certificate and decide which keys, devices and states to accept. The GitHub contributor says GrapheneOS publishes verified-boot key hashes that could be used in such a policy.
Play Integrity offers a different route: an application requests a verdict from Google, which can report whether a device meets specified integrity criteria. The contributor describes it as simpler to implement and easier to present to auditors, while arguing that independently validating attestation gives developers more control. Those are observations from one developer, not a comparative assessment established by independent testing in the supplied material.
The contributor also describes testing Play Integrity with 64 beta-tester verdicts and says none returned the strongest verdict, while emphasizing that the sample was limited. Those figures apply only to that developer’s test group; they do not establish how ASN’s app behaves, how common particular verdicts are, or whether ASN relies on Play Integrity.
“Hardware key attestation “proves a key was generated in a TEE or StrongBox but not app or OS integrity.””
— A contributor to the linked GitHub discussion, describing EPI’s stated reasoning
ASN’s Checks and Customer Impact
The supplied source does not include ASN’s response, documentation of its Android compatibility rules, or a technical analysis of its app. It is therefore unclear whether the reported block is deliberate, which devices and operating-system versions are affected, or whether the issue reflects Play Integrity, another security check, or a temporary compatibility problem.
It is also unclear how many customers have encountered the restriction and whether ASN provides a workaround, such as web banking or another supported device. The GitHub discussion’s technical claims and the contributor’s test results are not evidence of ASN’s own configuration. Confirmation from the bank and reproducible app testing would be needed to settle those points.
Confirmation From ASN Needed
The next step is for ASN to clarify its app requirements, identify any supported alternatives and explain whether the reported restriction is intended. A direct bank response, updated compatibility guidance or a documented change to the app would help customers determine whether their devices can be used.
Until then, users affected by the reported block should check ASN’s official support channels before relying on a particular workaround. The supplied material gives no date for a policy change or further announcement, so the app’s current compatibility status remains unconfirmed.
Key Questions
Does ASN block GrapheneOS?
The report says ASN’s Android app blocks GrapheneOS and other non-Google Android systems. The supplied material does not include confirmation from ASN or enough test details to establish the restriction’s full scope.
Has ASN explained why the app is blocked?
No explanation from ASN appears in the supplied source. The discussion includes a separate debate about EPI and Wero’s use of Play Integrity, which does not confirm ASN’s reason.
What is the difference between key attestation and Play Integrity?
Key attestation provides certificate-based information about a hardware-backed key and may include device boot-state and app-identity details. Play Integrity returns a verdict through Google. Developers must implement and interpret either system; the GitHub contributor’s claims about their relative strengths are their technical argument, not an ASN policy statement.
Can customers still access ASN banking without the Android app?
The supplied material does not say whether ASN offers web banking or another supported option for affected customers. Users should check ASN’s official support guidance for current account-access options.
Source: github.com
