PIN is required after switching between profiles

traveller

After the recent (or prior-to-recent) update, some of my profiles started requiring me to enter pin, not allowing to use fingerprint unlock - when I switch out of that profile to another one, and want to switch back. This is becoming very inconvenient, and I risk showing my pin to the CCTV cameras, as I may need to switch frequently.

I understand this is not graphene fault, rather Android devs have broken something again? Does anyone else experience this inconvenience? Do you know what may be causing it? (maybe, the phone may be running out of RAM and needs to shut down the profile or something?)

Pixel 9 Pro

n3t_admin

traveller I was always under the impression that the fingerprint unlock after switching profiles was a bug/glitch and PIN should be entered? Maybe it actually was and it's fixed now...

de0u

traveller I think I've read some reports that sometimes it's possible to "go back" from the PIN-entry keyboard and try the fingerprint "again". But, though I do have a low-security profile with fingerprint unlock for GPS navigation, I don't use it very often, so this isn't something I have a lot of experience with.

traveller

n3t_admin I was always under the impression that the fingerprint unlock after switching profiles was a bug/glitch and PIN should be entered? Maybe it actually was and it's fixed now...

It was like that in the past, but it wasn't the case for the past year, up until a recent update a week ago.
I am wondering if anyone knows what may be causing this (some specific app perhaps?) and whether it is possible to mitigate this issue?

harp

Fingerprint is always a secondary unlocking method beside PIN or password as primary method. The secondary method can only be available, when the profile to unlock was unlocked before and were allowed to run in the background. If a profile was turned off by "end session" or after changing profiles and running in background is not allowed, always the primary unlocking method has to be entered.

traveller

harp thanks. The main profile was marked as "Not running in the background" for some reason, it could got turned off by accident (or it could be android update that now "ends session" for the profile if it's not marked as running in the background, and the profile is changed?). In any case after enabling running in the background, it seems that now the profile doesn't lose the fingerprint unlock option.

de0u thanks, yes, I used that trick in the past :)

JayJay

traveller

I am experiencing same.
Where do you find that option for main profile?
I thought main was always running and can never be disabled/enabled.

traveller

JayJay Sorry for confusion, I call "main" a secondary user profile, and I didn't experience fingerprint issues with the owner profile. (I do not use the actual "owner" profile for anything other than system configuration and "app distribution" to other profiles (basically treating it like "root" user on Unix)).