Not fixed in 4.3.0.12 sadly. I have an app from my health insurance that is not complaining anymore about root but is missing the device lock setting now
If you are talking about Office 365 related MFA, it’s possible to use any other auth application, too, when configuring it in O365 account settings. If the company policy hasn’t disallowed that, or course.
Microsoft Auth has Support for passwords since some time now, I guess roundabout a year. So it’s not just the former Authenticator-only any more, it can show your passwords storefin Edge, payment Info and adresses.
So sorry for the confusion - what I wanted to say is that every function except the primary Authenticator function is blocked by the App itself cause of the missing device lock rights.
any news on that? Just encountered the same problem with my banking app - Code cant be set in Android security settings (Message after entering Pin:“screen lock has already been changed”) - and whatever i try it just says: screen lock: none.
Same problem while working with google sheets. This bug just blocks the ability to use some very usefull services. I reverted my other phone to previous version of SFOS just to set the android pin and than updated just because I need to use it. For newer devices it is even harder.
I cannot see why such a simple issue is left without attentions for so long time…
I had the same issue too. I tested the app on AppSupport before buying a ticket and all looked fine. I bought an interrail mobile ticket via the website afterwards, having full faith in the Sailfish AppSupport, but I could not add it due the lock screen requirement. That came as an unwanted surprise to me.
I had to take an old (ungoogled/LineageOS) Android phone with me on the travels, with a broken screen held in place by tape, just for the mobile interrail ticket. But I ended up having a nice trip. Although next time I am going for the physical ticket that they will mail to you.
My banking app got updated and now this problem surfaced for me too. I’d really like this bug to be fixed if it actually worked in a previous SailfishOS release. It’s been more than a year since this regression appeared.