Are you really sure the app you are having problems with now is still the same version that used to work?
This Bug is still an Issue in SFOS 4.6.0.13.
This would be very cool to get fixed in the next release. Shouldn’t be that difficult to make AppSupport think it is screen looked…
5 Likes
I saw it also in android forums. So the bug is in the underlying Android (lineage or aosp i don’t know?
It’s not a “bug” per se, more like an “adaptation with unintended consequences”. Sailfish’s AppSupport neutered the ability of the Android layer to have its own lock PIN, since Sailfish already has that ability on its own. However, Android apps can obviously only see the Android settings, so for them, the lock PIN is deactivated, which becomes a problem once apps mandate an activated lock PIN (as the German broker “Smartbroker+” does, in my case).
Unfortunately, this issue hasn’t been tackled with the latest update to 4.6.0.15 either. @jovirkku I know the issue is “tracked,” but is it actually on someone’s agenda?
3 Likes
Not tackled in Sailfish OS 5 either :\
The missing ability to set a lock PIN inside the Android layer also thwarts any possibility to have 2FA “passkey” support (WebAuthn - Wikipedia) for Android apps (e.g. Firefox, which supports passkeys on Android 14 and upwards) in the future - as brought up here in April: Android Support Passkey configuration and lock screen.
1 Like
Passkeys are funamentally flawed. All it does on top of a half-decent password manager is that the client software promises a few things. There are no enforcement mechanisms at all. I.e. Only one factor is actually authenticated. From a security or even general developer perspective, that’s completely insane to advertise as a feature, let alone call 2FA.
So this only furthers the argument that there is a strong correlation between silly apps and enforcing lockscreen password.
I’m not a fan of passkeys either, unfortunately some organizations are enforcing their usage (as my university, since today) without alternative.
1 Like
The German automobile club ADAC has changed banks for its Visa card. It is now Solaris Bank. When paying with the ADAC Visa, the purchase must now be confirmed online or in the app. However, this app also requires an Android PIN…
2 Likes
We should create a list of affected apps (and the number of downloads according to Google Play, as a measuring stick for their prominence):
ADAC Kreditkarte (100,000+ downloads)
Danske ID - Danske Bank (500,000+ downloads)
Eurail/Interrail Rail Planer (1 million+ downloads)
Microsoft Authenticator (100 million+ downloads)
SMARTBROKER+ Aktien & ETF (50,000+ downloads)
I will gladly update this list with further entries, just tell me which apps are affected (or if they no longer are). 
1 Like
Danske ID works if you use an old version (1.6.2) with Aurora Store. If you choose the “Manual Download” option then put in 1690000023) then you’ll get 1.6.2.
1 Like
Yes, I’ve seen your post in the Banking app thread, but it is highly questionable if Danske Bank will allow the usage of older versions down the line, that’s why I am keeping it on the list. It’s of course good that there is this workaround for the time being, however being able to use the latest version is obviously the better scenario.
Microsoft Authenticator
2 Likes
Eurail/Interrail Rail Planer (1 million+ downloads) is another app that requires a lock pin in order to add a Eurail/Interrail Mobile Pass.
2 Likes
Source?
I’m getting no google results for that requirement, and i have no issues.
Beyond that, it seems exceedingly stupid of them since everything even remotely sensitive is behind BankID anyway.
2023 I was not able to start Swish app because of this error. I currently have no Sailfish device (waiting for official 10V image). So I can not confirm, that it is the same with current version, but I can not imagine, that the requirement has been dropped.
I’m using Swish 5.17.1, which is from 2024 without any such issues.
Barring the XA2 gap between old AlienDalvik and AAS, and a particularly silly BankID version, i have had continued access to both since the beginning.
I can imagine that quite easily when they remembered everything is behind BankID.
The latest version is 6.0.0, are you able to update to it and tell me if the lock pin requirement remains absent?
Not interested in gambling 
These shitty apps can break if you look at them wrong.
…but having been removed after some arbitrary 2023 version sounds promising.
Edit: and on secondary phone i had laying around, it installs and starts without complaints - i obviously didn’t enroll.