Hi @henfredemars@infosec.pub,

The official statement from Google can be found here: https://support.google.com/pixelphone/thread/241474288

As for the bug eport itself, that is available on their issue tracker here:
https://issuetracker.google.com/issues/305766503
https://issuetracker.google.com/issues/307592536

The repos issue tracker is slightly more up to date.

There are some banking apps and apps in general that may be problematic. For such cases, here are the possible work around solutions.

You’re quite welcome.

No issues with running the RSA Authenticator (SecurID) app on both the Pixel 6 and 8 on the latest Android 14 build of GrapheneOS.

See previous reply for details as to why it wasn’t working for non-GrapheneOS users as well - over a year ago is when it started being problematic.

It works as far as I can tell. However, it wasn’t always the case.

My company also mentioned that GrapheneOS isn’t supported by them.

Version 4.3.12 is - I just installed it on both the Pixel 6 and the new Pixel 8, both running the latest GrapheneOS builds with Android 14.

they don’t support grapheneos though, specifically said the app won’t work on it

In the summer of 2022, numerous issues arose for non-GrapheneOS users as well, as reflected in the reviews. This was because the SecurID update began utilizing the Play Integrity API to detect non-certified OS/devices. The Play Integrity API has since replaced the now-obsolete SafetyNet attestation API.

Here’s a crowd-sourced list of international banking apps that are compatible with GrapheneOS:
https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/

The issue tracker has slightly more current banking app reports:
https://github.com/PrivSec-dev/banking-apps-compat-report

Some banking apps may be problematic and here are some possible workaround solutions:
https://discuss.grapheneos.org/d/8330-app-compatibility-with-grapheneos