I have two apps that seems to missbehave due to seemingly try to find another app (Swedish BankID) to adapt the user interface.
I know that other apps can successfully trigger the opening of said app using registered app links, but it feels like these apps also tries to look for the existance of that app.
Is this actively blocked in e/os (causing a difference in behavior compared to normal Android), and/or is there a way to control this? I couldn’t find any permission settings that seemed to control this.
You might first check the other three threads found from Search swedish bank id … but yes Banking apps will typically use intermediate methods which turn out to be Google dependent.
I was being unclear. The BankID app in itself works fine, and most other apps can utilize it as a mean of authentication without any problems. This includes my banking app (which is different) and other payment related apps (Swish being one of them). So all the app linking and everything is correct and as expected.
It’s just the two other apps that instead of just trying to open a link that the other app would act on, they seem to try and first figure out if the BankID app is installed (because the UI and the options available differs from my old phone).
So I’m wondering what hacky solution the use for this that doesn’t work here and if there is a workaround that someone might think of.
no, /e/OS hides some system environment properties, but for checking on apps it would work like standard Android. There’s two ways to check for other apps:
either by defining the appid in their manifest that it wants to query for, or
to see all apps, ask for the QUERY_ALL_PACKAGES permission (subject to playstore approval)
I think the first is what you see with apps checking for BankID. You can verify by looking at the querying apps manifest.
You could post an obfuscated screenshot to illustrate what you mean UI wise that is misbehaving / not as expected
