I would think that the likely change was in Android Studio perhaps not in the version available to amateurs but the Entrrprise versions where we cannot see the change logs.
My assertion is about how easy it is for Google to
provide devs with a quick link to this “user recorded” Date of Birth and
assert that this is “Safe enough for a bank to rely upon for the purpose of this legislation”.
On the other hand many privacy focussed individuals do not want their DoB recorded in their “Owner” record.
Same in Texas. I downloaded the Chase app from Aurora and tested it on a Fairphone 6+ with stock Android, with Google Play Services and the Play Store disabled, and got the same age-related message.
Chase bank app has adopted forced age-verification, via Google Play Store (ironic, as a privacy/security action …).
It’s broken in MicroG:
[com.chase.sig.android] Age verification fails #3876
whether e/os needs an upstream fix to MicroG, or works on a local/downstream fix is a separate question.
unclear if they’re aware; haven’t yet found a bug @ e/os … still looking
Thanks for the information. An e/OS user in Paris, France, bypassed the age-related error message (requirement) in the U.S. Chase banking app by switching the VPN to Dallas, TX, and reaching the login screen. Not sure if this helps with efforts to resolve this issue or bug. Thanks!
Hii, im very new to murena os, im thinking about buyng a second hand phone, but my bank in not so common its bcc , i see that mycartabcc could have some problems with digital payments or 3DS system, do you have any updates?
Belgium banking apps on /e/OS (Fairphone 4)
Working fine: VDK, Argenta, KBC, Belfius, Itsme, Triodos, Viva, …
After install always first go to settings > apps > select your app > “Open by default” > select all “links to open in this app”. Then login to the app and continue configuration.
