I update android regularly, using a dirty flash of the system partition.
Every time I update the OS, enpass starts up asking for the fingerprint. But the fingerprint is not even configured in android, and more important, enpass was configured for password and not for fingerprint, before the OS update. As a result, enpass cannot be started.
I am forced to configure the fingerprint in android. After this, upon first start, enpass disables the fingerprint stating that there are multiple fingerprints configured, and reverts back to the password method. At this point enpass can be used.
This behaviour seems inconsistent to me.