Triodos Bank UK

[ph00lt0]

Is there an existing issue for this?

• I have searched the existing issues

App name

Triodos Bank UK

Link to app

https://play.google.com/store/apps/details?id=com.triodos.bankinguk

App version

2.12.1

Country of the app

United Kingdom

Build Number

TP1A.220624.014.2022082400

Device

• Pixel 6a
• Pixel 6 Pro
• Pixel 6
• Pixel 5a
• Pixel 5
• Pixel 4a (5G)
• Pixel 4a
• Pixel 4 XL
• Pixel 4
• Pixel 3a XL
• Pixel 3a
• Pixel 3 XL
• Pixel 3

Google Play installed

• Installed
• Not installed

Google Play services Network permission revoked?

• Revoked
• Not revoked
• I did not have Google Play services installed

SafetyNet Enforcement

• Enforced
• Not enforced
• Unsure

Native code debugging

• Enabled
• Disabled

Stock OS compatibility

• Works
• Does not work
• Not tested

Profile app tested in

• Main user profile
• Secondary user profile
• I used a work profile device manager app (Please mention more details about it down below like the app)

Description of the app's functionality

All functions work as expected.

Are there any extra notes you think users should know about?

No response

ADB logcat of the app if necessary

No response

[akc3n]

Thanks @ph00lt0

[treequell]

A recent update to this app seems to have created a memory corruption bug uncovered by GrapheneOS.

When I open the app (version 3.52.1) with exploit protection compatibility mode disabled, the app crashes upon launch. If I enable the exploit protection compatibility mode the app functions as expected. Prior to this update, the app functioned as expected even with the exploit protection compatibility mode disabled.

Tested on:

• Pixel 7 running GrapheneOS TQ1A.230205.002.2023030400
• App installed in owner profile
• Google Play Store and sandboxed Google Play Services all with network permission
• Secure app spawning enabled
• Native code debugging disabled

[floatingatoms]

Hello, not sure whether you wanted a new issue for this but this app now requires native code debugging to be enabled. I'm currently on version 4.7.7 but a previous version is what triggered it.