Tested multiple GSIs. Bank app won't work only on this AOSP
ap-gitx opened this issue · 3 comments
Acknowledgements
- I have chosen an appropriate title.
- All requested information has been provided properly.
- This is not a feature request.
- This issue is not a duplicate of an existing issue.
- The issue is solely related to this GSI.
- This issue occurs with the latest available build.
- I am not running a custom vendor on my device.
- This issue is not kernel related.
- This issue is not related to Magisk/KernelSU/APatch.
Info
- Device: redmi note 7
- GSI version: latest
- Vendor version: latest
Expected Behavior
I install my banking app, but when opening it for the first time it complains that the device is insecure. I tried 6 other GSIs but all was fine. What could that be? is /system/etc/security/otacerts.zip signed with what keys? If I give you the app name, could you have a look at it or can't be bothered? Thanks ponces
Current Behavior
Install app --> complains, won't work
Possible Solution
No response
Steps to Reproduce
- install app
- swear
Logs
No response
Additional context
No response
Is insecure because of what? Builds are being signed with private keys and they weren't until now so that's more secure than before.
If you are talking about root detection, Play Integrity is passing out of the box and I won't bother with other root detection methods.
Sorry, but this is not a bug.
What can be done from the users side to resolve this?
I would start by explaining what you mean by "won't work". Then, I would gather some logs to understand the real issue behind the "won't work" idea. And finally, I would try to understand how this could be workaround... Many apps rely on obsolete libs to identify if the device is "secure" (in their perspective) or not. Most of these libs are achieving this by doing it in stupid ways.