Banking app refuses to launch due to untrusted store

sir

It appears that the problem has been identified and Consorsbank is working on it => LINK or LINK

HawkEy3

sir unfortunately looks like they're not working on it but it is intended

schweizer Thanks, but that's not very helpful I'm already actively using my work profile and don't want to install Play Store there either. But I agree that Consorsbank is so far the first and only banking app I encounter that checks its install source.

Alternative is probably only a tan generator

rofeki8011

There is now a main thread on their Subreddit discussing this issue https://www.reddit.com/r/Consorsbank/comments/1p909w1/consorsbank_schr%C3%A4nkt_app_nutzung_ein/

schweizer

HawkEy3 but that's not very helpful I'm already actively using my work profile and don't want to install Play Store there either.

I do not know what you understood from my text but I gave you an instruction on how to install the app in your work profile without installing any google there.

MetropleX

HawkEy3 schweizer 's instructions here will allow use of the banking app in work profile without play services being there as mentioned in their reply to you.

Apps on a device share the app source across profiles while being isolated from each other with various instances, which is why updating an app in one user updates it across all users. Doing the steps they mention will update it in the work profile while also changing the install source to Play Store for it to function if that is all they're checking.

HawkEy3

Ah sorry, then I misunderstood. I thought by "second profile" you mean the "work profile"
But then you need a google account and Play Store in your main (private) profile?

schweizer

HawkEy3 But then you need a google account and Play Store in your main (private) profile?

No. That is the whole point. I was not entirely clear. I should have written "create a new additional secondary profile". That profile will later have the sole purpose of updating your apps. It does not matter whether your work profile is the owner or not. Just follow the steps one by one and you will see it works. Trust us a little bit.

HawkEy3

I see thanks, to be honest I didn't know that was possible, found a guide here. Still sceptical of installing google services on any profile.

schweizer

HawkEy3 Still sceptical of installing google services on any profile.

I can understand. If your bank requires google and you want to continue to use it you must take a decision.

On the technical side you can register your google account on a free wifi such as coffee shop and use a fake name. Once it is set up it runs on Tor. I think this is the maximum privacy achievable with your boundary conditions.

akc3n

rofeki8011 Since the last update of my banking app (Consorsbank), it no longer starts. The error “The application was not installed from a trusted store (A053)” now appears in the app.

Could you please provide the app id for said banking app?
Is it related to this one specifically? https://github.com/PrivSec-dev/banking-apps-compat-report/issues/168

HawkEy3 See https://seprand.github.io/articles/best-user-profile-setup/ and another note, we list our features on our site, including https://grapheneos.org/features#improved-user-profiles

schweizer Once it is set up it runs on Tor.

HawkEy3 It would be very unwise to use anything related to banking or personal accounts via Tor.

HawkEy3

using adb to change the installation source worked for me, like described here
https://www.kuketz-forum.de/t/android-ohne-google-account-nutzen/13204/19
though, installation source didn't change to "play store" but to "app installed from microG Companion (via shell)" but hey, it's working.... for now.

MetropleX

HawkEy3

As a warning to others, it is not advised to use USB Debugging:

ADB exposes an enormous amount of attack surface.
If you have ADB access, you can enable perf events, but there's a lot more attack surface via ADB than that and it's as close as it gets to having root access without an exploit.
ADB has near full control of the device, but isn't meant to actually have root access on a production build. It can be used to do everything you can do via the UI but also far more which expose a lot of attack surface.
ADB isn't advisable on a production device either way.

We don't support it.

HawkEy3

MetropleX Thanks for the input, that's true. I advice to only enable USB Debugging when needed and disable it afterwards, that's what I do.

akc3n thanks for the guides.
I didn't mention Tor though.