Fixed
Status Update
Comments
ph...@monzo.com <ph...@monzo.com> #2
this issue was created using original issue https://issuetracker.google.com/issues/389970341#comment2
.
but i am not sure that described text above is the same as in original issue:
also doesn't work
https://example.com/path/detail?token=123 in all versions.
pattern:
https://example.com/path/.*?token={id}
P.S. original issue also has test project https://issuetracker.google.com/389970341#attachment62385890
sp...@google.com <sp...@google.com>
ap...@google.com <ap...@google.com> #3
It's essentially the same cause - navigation is prioritizing the wrong deeplink when they share the same action.
sp...@google.com <sp...@google.com>
sp...@google.com <sp...@google.com>
sp...@google.com <sp...@google.com>
ap...@google.com <ap...@google.com> #4
Fixed internally and will be available in navigation-2.8.8
Description
The workaround that forces strong biometrics on old devices without platform support for specifying the required strength of the authenticator is only applied when the authenticator is exactly
BIOMETRIC_STRONG
.It should also be applied when using
BIOMETRIC_STRONG | DEVICE_CREDENTIAL
.