App screen is not reliably hidden in app switcher about keepassium HOT 4 CLOSED

Thank you for the feedback!

Closing the app will sometimes, especially when closing the app right after unlocking through FaceID, not show the splash

Just to be sure: is it "especially" or "only"?

I can confirm the "only" case: if the app is minimized during Face ID animation, the UI might appear uncovered. This is due to a technical challenge:

• Face ID prompt appears as a separate system-controlled window above KeePassium.
• When it appears, the system notifies the app that it was just sent to background/minimized.
• After a successful Face ID scan, the system notifies the app about success, but still shows Face ID animation for 1-2 seconds (depending on device).
• During this time, the app is in a limbo state: it already knows Face ID was successful, but the app is still "in background".
• Unlocking the app immediately proved to be a bad idea: once Face ID animation finishes and KeePassium becomes the "foreground" app, it would detect that was just switched to and needs to lock up. This causes Face ID prompts to appear repeatedly.
• To work around this issue, the app delays unlocking by a second (or two). This prevents racing conflicts between Face ID notifications and app state transitions.

But as a side effect, if you minimize the app during Face ID animation, the app switcher screenshot might indeed catch the app unlocked after the Face ID delay. The best solution I can offer at the moment is to avoid minimizing the app during Face ID animation... (aka "just avoid holding it in that way".)

Have you noticed other scenarios where the issue occurs?

from keepassium.

@bob-lobster , any feedback on the questions above?

from keepassium.

Thanks for your reply and sorry for not getting back directly.

I indeed can‘t replicate it in any other scenario.

I have tried replicating it in other apps though.

In my banking app it never happens. In Microsoft Authenticator it is harder to replicate but can happen with the right timing.

Since it is a niche scenario I agree it can be worked around.

from keepassium.

Thank you for the update. In this case I will close this as a known limitation.

from keepassium.