Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android Timeout #146

Open
Erseni opened this issue Nov 21, 2024 · 5 comments
Open

Android Timeout #146

Erseni opened this issue Nov 21, 2024 · 5 comments

Comments

@Erseni
Copy link

Erseni commented Nov 21, 2024

Describe the issue

On Android i can register with my fingerprint, but i cannot sign in. There is a Timeout and

Reproduction Steps

  1. Go to https://webauthn.io/
  2. Register your fingerprint
  3. Click on Authenticate and there is a timeout Error

The operation either timed out or was not allowed. See: https://www.w3.org/TR/webauthn-2/#sctn-privacy-considerations-client.

Expected behavior

It should prompt for my fingerprint

Code Samples + WebAuthn Options and Responses

Default Options on webauthn.io

Dependencies

  • OS: Galaxy S22+ Android 14
  • Browser: latest Brave, latest Chrome
  • Authenticator: Fingerprint or any other options
@Cyrille37
Copy link

Cyrille37 commented Nov 21, 2024

I got the same error but with "register" on my Samsung A41 Android 12 with Chrome 128 & Firefox 132 😞

But I got the same error at https://www.passkeys.io, https://webauthn.me and other demo sites with same environment ... (demos list)

@Cyrille37
Copy link

If this test page is a reference, it gives bad news for my device : https://featuredetect.passkeys.dev/

@Cyrille37
Copy link

It works with Samsung and Android 14.

@neochae1
Copy link

neochae1 commented Nov 27, 2024

Android Chrome latest version 131.0.6778.81 does not works.
Removing the update makes it work with version 118.0.5993.80.

Galaxy S21 Ultra 5G, Android 14

@neochae1
Copy link

I am experiencing a similar issue to the one described in the following link: https://simplewebauthn.dev/docs/packages/browser#troubleshooting

In Chrome versions 126 and below, the platform indicates when there is no passkey present. However, starting with version 127 and in subsequent versions, an error is returned when there is no passkey.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants