[GH-ISSUE #6454] [PM-31493] Failed to create a new passkey for MyJCB Android app #21708

Open
opened 2026-04-16 22:18:19 -05:00 by GiteaMirror · 14 comments
Owner

Originally created by @isseis on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6454

Origin

Native Application (non-browser app)

Web URL or App name

jp.co.jcb.my

Passkey Action

  • Creating new passkey (Registration)
  • Signing in (Authentication)

Build Information

Version: 2026.10 (21141)
Operating System: 16 (36)
Device: samsung SM-F956Q

Additional Information

The app is for a credit card user issued by JCB, so it'd be difficult to reproduce this in developers' environment (unless they have a JCB issued credit card)

How to reproduce

  1. Run MyJCB app
  2. Click "MyPage" link in the bottom bar
  3. Scroll down to "Application Config" menu, and click "Login configuration" menu
  4. Click "Passkey" button
  5. Click "Register" button
  6. Bitwarden shows a pop up dialog to create a passkey
  7. Fingerprint authentication to start Bitwarden app
  8. Create a new login data and save it
  9. Bitwarden app is closed, and move back to the MyJCB app
  10. Failure dialog is shown

According to the flight log captured in Bitwarden Android app, Digital asset link validation succeeded.

Digital asset link validation result: linked = true

However, Bitwarden SDK throws an exception com.bitwarden.fido.Fido2ClientException$InvalidOrigin: Invalid origin: InvalidAssetLinkUrl immediately after that.

Full stack trace

WARNING – p0 – com.bitwarden.sdk.BitwardenException$Fido2Client: v1=com.bitwarden.fido.Fido2ClientException$InvalidOrigin: Invalid origin: InvalidAssetLinkUrl
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:15)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.FfiConverter$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13)
	at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2)
	at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2)
	at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2)
	at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:79)
	at com.bitwarden.sdk.Bitwarden_uniffiKt.access$uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiRustCallAsync(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:186)
	at com.bitwarden.sdk.ClientFido2Client.register$suspendImpl(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:122)
	at com.bitwarden.sdk.ClientFido2Client.register(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at androidx.lifecycle.n0.a(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:111)
	at androidx.lifecycle.n0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:104)
	at androidx.lifecycle.n0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:69)
	at kv.e.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:51)
	at kv.c.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:59)
	at h4.q0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:382)
	at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8)
	at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115)
	at hv.v0.v0(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:24)
	at hv.k.o(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:93)
	at hv.k.q(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:3)
	at jv.i.a(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:7)
	at jv.g.I(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:76)
	at jv.g.i(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:53)
	at jv.g.h(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:97)
	at com.bitwarden.ui.platform.base.BaseViewModel.trySendAction(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:3)
	at np.v4.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:145)
	at com.bitwarden.ui.platform.components.util.ThrottledClickKt$throttledClick$1$1$1.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:41)
	at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8)
	at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115)
	at h4.u0.q0(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:24)
	at h4.t0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:3)
	at android.os.Handler.handleCallback(Handler.java:995)
	at android.os.Handler.dispatchMessage(Handler.java:103)
	at android.os.Looper.loopOnce(Looper.java:273)
	at android.os.Looper.loop(Looper.java:363)
	at android.app.ActivityThread.main(ActivityThread.java:10060)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @isseis on GitHub (Feb 1, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6454 ### Origin Native Application (non-browser app) ### Web URL or App name jp.co.jcb.my ### Passkey Action - [x] Creating new passkey (Registration) - [ ] Signing in (Authentication) ### Build Information Version: 2026.10 (21141) Operating System: 16 (36) Device: samsung SM-F956Q ### Additional Information The app is for a credit card user issued by JCB, so it'd be difficult to reproduce this in developers' environment (unless they have a JCB issued credit card) How to reproduce 1. Run MyJCB app 2. Click "MyPage" link in the bottom bar 3. Scroll down to "Application Config" menu, and click "Login configuration" menu 4. Click "Passkey" button 5. Click "Register" button 6. Bitwarden shows a pop up dialog to create a passkey 7. Fingerprint authentication to start Bitwarden app 8. Create a new login data and save it 9. Bitwarden app is closed, and move back to the MyJCB app 10. Failure dialog is shown According to the flight log captured in Bitwarden Android app, Digital asset link validation succeeded. ``` Digital asset link validation result: linked = true ``` However, Bitwarden SDK throws an exception `com.bitwarden.fido.Fido2ClientException$InvalidOrigin: Invalid origin: InvalidAssetLinkUrl` immediately after that. Full stack trace ``` WARNING – p0 – com.bitwarden.sdk.BitwardenException$Fido2Client: v1=com.bitwarden.fido.Fido2ClientException$InvalidOrigin: Invalid origin: InvalidAssetLinkUrl at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:15) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.FfiConverter$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13) at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2) at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2) at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2) at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:79) at com.bitwarden.sdk.Bitwarden_uniffiKt.access$uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiRustCallAsync(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:186) at com.bitwarden.sdk.ClientFido2Client.register$suspendImpl(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:122) at com.bitwarden.sdk.ClientFido2Client.register(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at androidx.lifecycle.n0.a(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:111) at androidx.lifecycle.n0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:104) at androidx.lifecycle.n0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:69) at kv.e.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:51) at kv.c.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:59) at h4.q0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:382) at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8) at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115) at hv.v0.v0(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:24) at hv.k.o(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:93) at hv.k.q(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:3) at jv.i.a(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:7) at jv.g.I(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:76) at jv.g.i(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:53) at jv.g.h(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:97) at com.bitwarden.ui.platform.base.BaseViewModel.trySendAction(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:3) at np.v4.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:145) at com.bitwarden.ui.platform.components.util.ThrottledClickKt$throttledClick$1$1$1.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:41) at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8) at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115) at h4.u0.q0(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:24) at h4.t0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:3) at android.os.Handler.handleCallback(Handler.java:995) at android.os.Handler.dispatchMessage(Handler.java:103) at android.os.Looper.loopOnce(Looper.java:273) at android.os.Looper.loop(Looper.java:363) at android.app.ActivityThread.main(ActivityThread.java:10060) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975) ``` ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the bug-passkeyapp:password-manager labels 2026-04-16 22:18:19 -05:00
Author
Owner

@bitwarden-bot commented on GitHub (Feb 1, 2026):

Thank you for your report! We've added this to our internal board for review.
ID: PM-31493

<!-- gh-comment-id:3830054938 --> @bitwarden-bot commented on GitHub (Feb 1, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-31493](https://bitwarden.atlassian.net/browse/PM-31493) [PM-31493]: https://bitwarden.atlassian.net/browse/PM-31493?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Author
Owner

@sshadminBW commented on GitHub (Feb 1, 2026):

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

<!-- gh-comment-id:3832237368 --> @sshadminBW commented on GitHub (Feb 1, 2026): Hi there, Thank you for your report! I was able to reproduce this issue, and I have flagged this to our engineering team. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these. Thanks once again!
Author
Owner

@Asutorufa commented on GitHub (Feb 6, 2026):

same problem here with telegram


2026-02-06 18:53:34:570 – ERROR – g – Failed to register FIDO2 credential.
com.bitwarden.sdk.BitwardenException$Fido2Client: v1=com.bitwarden.fido.Fido2ClientException$InvalidOrigin: Invalid origin: InvalidAssetLinkUrl
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:15)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.FfiConverter$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13)
	at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2)
	at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2)
	at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2)
	at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:79)
	at com.bitwarden.sdk.Bitwarden_uniffiKt.access$uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiRustCallAsync(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:186)
	at com.bitwarden.sdk.ClientFido2Client.register$suspendImpl(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:122)
	at com.bitwarden.sdk.ClientFido2Client.register(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at androidx.lifecycle.n0.a(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:111)
	at androidx.lifecycle.n0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:104)
	at androidx.lifecycle.n0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:69)
	at kv.e.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:51)
	at kv.c.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:59)
	at h4.q0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:382)
	at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8)
	at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115)
	at hv.v0.v0(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:24)
	at mv.b.j(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:142)
	at hv.a0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:123)
	at hv.b0.x(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:23)
	at hv.b0.y(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13)
	at nq.c3.q(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:53)
	at nq.c3.p(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:71)
	at nq.t2.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:118)
	at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8)
	at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115)
	at android.os.Handler.handleCallback(Handler.java:995)
	at android.os.Handler.dispatchMessage(Handler.java:103)
	at android.os.Looper.loopOnce(Looper.java:273)
	at android.os.Looper.loop(Looper.java:363)
	at android.app.ActivityThread.main(ActivityThread.java:10060)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
 – com.bitwarden.sdk.BitwardenException$Fido2Client: v1=com.bitwarden.fido.Fido2ClientException$InvalidOrigin: Invalid origin: InvalidAssetLinkUrl
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:15)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.FfiConverter$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13)
	at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2)
	at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2)
	at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2)
	at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:79)
	at com.bitwarden.sdk.Bitwarden_uniffiKt.access$uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiRustCallAsync(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:186)
	at com.bitwarden.sdk.ClientFido2Client.register$suspendImpl(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:122)
	at com.bitwarden.sdk.ClientFido2Client.register(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1)
	at androidx.lifecycle.n0.a(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:111)
	at androidx.lifecycle.n0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:104)
	at androidx.lifecycle.n0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:69)
	at kv.e.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:51)
	at kv.c.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:59)
	at h4.q0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:382)
	at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8)
	at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115)
	at hv.v0.v0(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:24)
	at mv.b.j(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:142)
	at hv.a0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:123)
	at hv.b0.x(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:23)
	at hv.b0.y(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13)
	at nq.c3.q(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:53)
	at nq.c3.p(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:71)
	at nq.t2.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:118)
	at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8)
	at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115)
	at android.os.Handler.handleCallback(Handler.java:995)
	at android.os.Handler.dispatchMessage(Handler.java:103)
	at android.os.Looper.loopOnce(Looper.java:273)
	at android.os.Looper.loop(Looper.java:363)
	at android.app.ActivityThread.main(ActivityThread.java:10060)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
<!-- gh-comment-id:3859841605 --> @Asutorufa commented on GitHub (Feb 6, 2026): same problem here with telegram ``` 2026-02-06 18:53:34:570 – ERROR – g – Failed to register FIDO2 credential. com.bitwarden.sdk.BitwardenException$Fido2Client: v1=com.bitwarden.fido.Fido2ClientException$InvalidOrigin: Invalid origin: InvalidAssetLinkUrl at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:15) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.FfiConverter$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13) at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2) at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2) at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2) at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:79) at com.bitwarden.sdk.Bitwarden_uniffiKt.access$uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiRustCallAsync(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:186) at com.bitwarden.sdk.ClientFido2Client.register$suspendImpl(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:122) at com.bitwarden.sdk.ClientFido2Client.register(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at androidx.lifecycle.n0.a(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:111) at androidx.lifecycle.n0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:104) at androidx.lifecycle.n0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:69) at kv.e.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:51) at kv.c.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:59) at h4.q0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:382) at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8) at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115) at hv.v0.v0(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:24) at mv.b.j(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:142) at hv.a0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:123) at hv.b0.x(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:23) at hv.b0.y(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13) at nq.c3.q(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:53) at nq.c3.p(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:71) at nq.t2.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:118) at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8) at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115) at android.os.Handler.handleCallback(Handler.java:995) at android.os.Handler.dispatchMessage(Handler.java:103) at android.os.Looper.loopOnce(Looper.java:273) at android.os.Looper.loop(Looper.java:363) at android.app.ActivityThread.main(ActivityThread.java:10060) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975) – com.bitwarden.sdk.BitwardenException$Fido2Client: v1=com.bitwarden.fido.Fido2ClientException$InvalidOrigin: Invalid origin: InvalidAssetLinkUrl at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:15) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.read(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.FfiConverter$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13) at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.liftFromRustBuffer(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2) at com.bitwarden.sdk.FfiConverterRustBuffer$DefaultImpls.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:6) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.FfiConverterTypeBitwardenError.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2) at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:2) at com.bitwarden.sdk.BitwardenException$ErrorHandler.lift(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:79) at com.bitwarden.sdk.Bitwarden_uniffiKt.access$uniffiCheckCallStatus(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at com.bitwarden.sdk.Bitwarden_uniffiKt.uniffiRustCallAsync(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:186) at com.bitwarden.sdk.ClientFido2Client.register$suspendImpl(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:122) at com.bitwarden.sdk.ClientFido2Client.register(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:1) at androidx.lifecycle.n0.a(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:111) at androidx.lifecycle.n0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:104) at androidx.lifecycle.n0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:69) at kv.e.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:51) at kv.c.c(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:59) at h4.q0.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:382) at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8) at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115) at hv.v0.v0(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:24) at mv.b.j(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:142) at hv.a0.invoke(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:123) at hv.b0.x(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:23) at hv.b0.y(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:13) at nq.c3.q(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:53) at nq.c3.p(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:71) at nq.t2.invokeSuspend(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:118) at xr.a.resumeWith(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:8) at hv.j0.run(r8-map-id-02fdf5f89272614ec878de7adda5f42926f9802f10b5d99996c77817a23b127e:115) at android.os.Handler.handleCallback(Handler.java:995) at android.os.Handler.dispatchMessage(Handler.java:103) at android.os.Looper.loopOnce(Looper.java:273) at android.os.Looper.loop(Looper.java:363) at android.app.ActivityThread.main(ActivityThread.java:10060) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975) ```
Author
Owner

@pamperer562580892423 commented on GitHub (Feb 6, 2026):

@isseis @sshadminBW @rmcdowell-bitwarden As some other GitHub issues about passkey creation and authentication failures on several apps now were closed as duplicates of this issue - and it seems to be a more widespread issue with Android app 2026.1.0 (and 2026.1.1?) - I would like to suggest to change the title of this topic to something more general (instead of mentioning a specific app only), to reflect that this issue now stands for issues with passkey usage on other apps also - and so that the likelihood of opening more duplicates to this issue here might be reduced.

My suggestion would be something like this for a new title:

"Passkey creation and authentication fails on apps with Android app 2026.1.0"

<!-- gh-comment-id:3861914184 --> @pamperer562580892423 commented on GitHub (Feb 6, 2026): @isseis @sshadminBW @rmcdowell-bitwarden As some other GitHub issues about passkey creation and authentication failures on several apps now were closed as duplicates of this issue - and it seems to be a more widespread issue with Android app 2026.1.0 (and 2026.1.1?) - I would like to suggest to change the title of this topic to something more general (instead of mentioning a specific app only), to reflect that this issue now stands for issues with passkey usage on other apps also - and so that the likelihood of opening more duplicates to this issue here might be reduced. My suggestion would be something like this for a new title: "Passkey creation and authentication fails on apps with Android app 2026.1.0"
Author
Owner

@FranLa commented on GitHub (Feb 6, 2026):

Info
If the title of this PR changes to "Passkey creation and authentication fails on apps with Android app 2026.1.0" as suggested above I can - just to confirm that it is version-related - inform you of that with 2026.1.0 I could not authenticate (on Android) to for example the Microsoft OneNote app with the passkey in Bitwarden (but just fine with the passkey in Google Password Manager).
I then uninstalled 2026.1.0 and installed 2025.12.1 and now it works just fine again (as it did before I upgraded to 2026.1.0.
I wrote about this in more details in community.bitwarden.com ( https://community.bitwarden.com/t/bitwarden-android-app-2026-1-0-issues-with-passkeys-both-with-apps-and-with-some-browsers ) and got some great comments including a link to this PR - so therefore I add this info here as well

<!-- gh-comment-id:3862596816 --> @FranLa commented on GitHub (Feb 6, 2026): Info If the title of this PR changes to "Passkey creation and authentication fails on apps with Android app 2026.1.0" as suggested above I can - just to confirm that it is version-related - inform you of that with 2026.1.0 I could not authenticate (on Android) to for example the Microsoft OneNote app with the passkey in Bitwarden (but just fine with the passkey in Google Password Manager). I then uninstalled 2026.1.0 and installed 2025.12.1 and now it works just fine again (as it did before I upgraded to 2026.1.0. I wrote about this in more details in community.bitwarden.com ( https://community.bitwarden.com/t/bitwarden-android-app-2026-1-0-issues-with-passkeys-both-with-apps-and-with-some-browsers ) and got some great comments including a link to this PR - so therefore I add this info here as well
Author
Owner

@Asutorufa commented on GitHub (Feb 7, 2026):

Update bitwarden Android to 2026.1.1 solve my problem.

<!-- gh-comment-id:3864003349 --> @Asutorufa commented on GitHub (Feb 7, 2026): Update bitwarden Android to 2026.1.1 solve my problem.
Author
Owner

@n0rc commented on GitHub (Feb 7, 2026):

Update bitwarden Android to 2026.1.1 solve my problem.

Can't confirm: 2026.1.1 still does not work for me with Fennec while 2025.12.1 does.

<!-- gh-comment-id:3864795607 --> @n0rc commented on GitHub (Feb 7, 2026): > Update bitwarden Android to 2026.1.1 solve my problem. Can't confirm: 2026.1.1 still does not work for me with Fennec while 2025.12.1 does.
Author
Owner

@FranLa commented on GitHub (Feb 7, 2026):

Info If the title of this PR changes to "Passkey creation and authentication fails on apps with Android app 2026.1.0" as suggested above I can - just to confirm that it is version-related - inform you of that with 2026.1.0 I could not authenticate (on Android) to for example the Microsoft OneNote app with the passkey in Bitwarden (but just fine with the passkey in Google Password Manager). I then uninstalled 2026.1.0 and installed 2025.12.1 and now it works just fine again (as it did before I upgraded to 2026.1.0. I wrote about this in more details in community.bitwarden.com ( https://community.bitwarden.com/t/bitwarden-android-app-2026-1-0-issues-with-passkeys-both-with-apps-and-with-some-browsers ) and got some great comments including a link to this PR - so therefore I add this info here as well

As I mentioned in the quoted chat entry I first downgraded to 2025.12.1 and then I was able to log in to the OneNote app (and other apps) again.
Inspired by others testing 2026.1.1 I today installed "Password Manager 2026.1.1 (21176)", and now everything works for me. That includes the before mentioned OneNote app, but also the LinkedIn app which did'nt work with 2026.1.0 either.
And the passkey login in the mobile Firefox browser worked all the time - with 2026.1.0, with 2025.12.1 and also with "2026.1.1 (21176)".
I don't use the Fennec browser (since n0rc mentioned that he still has problem with Fennec), so I can't comment on than (but a bit strange because afaik Fennic is based on Firefox).

So ... looking gooooood (to me at least)👍

<!-- gh-comment-id:3864812827 --> @FranLa commented on GitHub (Feb 7, 2026): > Info If the title of this PR changes to "Passkey creation and authentication fails on apps with Android app 2026.1.0" as suggested above I can - just to confirm that it is version-related - inform you of that with 2026.1.0 I could not authenticate (on Android) to for example the Microsoft OneNote app with the passkey in Bitwarden (but just fine with the passkey in Google Password Manager). I then uninstalled 2026.1.0 and installed 2025.12.1 and now it works just fine again (as it did before I upgraded to 2026.1.0. I wrote about this in more details in community.bitwarden.com ( https://community.bitwarden.com/t/bitwarden-android-app-2026-1-0-issues-with-passkeys-both-with-apps-and-with-some-browsers ) and got some great comments including a link to this PR - so therefore I add this info here as well As I mentioned in the quoted chat entry I first downgraded to 2025.12.1 and then I was able to log in to the OneNote app (and other apps) again. Inspired by others testing 2026.1.1 I today installed "Password Manager 2026.1.1 (21176)", and now everything works for me. That includes the before mentioned OneNote app, but also the LinkedIn app which did'nt work with 2026.1.0 either. And the passkey login in the mobile Firefox browser worked all the time - with 2026.1.0, with 2025.12.1 and also with "2026.1.1 (21176)". I don't use the Fennec browser (since n0rc mentioned that he still has problem with Fennec), so I can't comment on than (but a bit strange because afaik Fennic is based on Firefox). So ... looking gooooood (to me at least)👍
Author
Owner

@pamperer562580892423 commented on GitHub (Feb 7, 2026):

@n0rc:

Update bitwarden Android to 2026.1.1 solve my problem.

Can't confirm: 2026.1.1 still does not work for me with Fennec while 2025.12.1 does.

You're in the wrong "issue" here with that, as this issue here is about passkey issues with apps.

The passkey issue with some browsers is tracked in this other GitHub issue: https://github.com/bitwarden/android/issues/6463

<!-- gh-comment-id:3864813739 --> @pamperer562580892423 commented on GitHub (Feb 7, 2026): @n0rc: > > Update bitwarden Android to 2026.1.1 solve my problem. > > Can't confirm: 2026.1.1 still does not work for me with Fennec while 2025.12.1 does. You're in the wrong "issue" here with that, as this issue here is about passkey issues with **apps**. The passkey issue with some browsers is tracked in this other GitHub issue: https://github.com/bitwarden/android/issues/6463
Author
Owner

@pamperer562580892423 commented on GitHub (Feb 9, 2026):

2026.1.1 seems to fix this issue for me also. PS: Though only tested with one app (WhatsApp)!

<!-- gh-comment-id:3873277708 --> @pamperer562580892423 commented on GitHub (Feb 9, 2026): 2026.1.1 seems to fix this issue for me also. PS: Though only tested with one app (WhatsApp)!
Author
Owner

@isseis commented on GitHub (Feb 10, 2026):

I've verified that I could create passkey for MyJCB app with 2026.1.1.

I'm still experiencing "failed to create a new passkey" error in other apps, but according to the logs, the root cause appears to be different.

Bitwarden Android - Password Manager
Log Start Time: 2026-02-10 09:42:24:662
Log Duration: 1h
App Version: 2026.1.1 (21176)
Build: release/standard
Operating System: 16 (36)
Device: samsung SM-F956Q
Fingerprint: samsung/q6qjpnw/q6q:16/BP2A.250605.031.A3/F956QOPU1CYKD:user/release-keys
2026-02-10 09:42:24:668 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-02-10 09:42:24:668 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-02-10 09:42:24:686 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute
2026-02-10 09:42:27:293 – DEBUG – c – App is backgrounded
2026-02-10 09:42:33:005 – DEBUG – a – Parsing AssistStructure -- 6320
2026-02-10 09:42:33:005 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 6320
2026-02-10 09:42:33:007 – DEBUG – d – Autofill request success: Unfillable -- 6320
2026-02-10 09:42:35:236 – DEBUG – BitwardenCredentialProviderService – Create credential request received.
2026-02-10 09:42:36:667 – DEBUG – c – App is foregrounded
2026-02-10 09:42:36:673 – DEBUG – a – MainActivity destination changed: com.x8bit.bitwarden.ui.platform.feature.rootnav.RootNavigationRoute
2026-02-10 09:42:36:681 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute
2026-02-10 09:42:36:692 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-02-10 09:42:36:693 – DEBUG – a – RootNavScreen destination changed: nq.k0/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute
2026-02-10 09:42:36:710 – DEBUG – BitwardenNetworkClient – --> GET https://digitalassetlinks.googleapis.com/v1/assetlinks:check?source.web.site=https%3A%2F%2Fmonex.co.jp&target.androidApp.packageName=jp.co.monex.comprehensive&target.androidApp.certificate.sha256Fingerprint=10%3A40%3A80%3A57%3AFE%3AF5%3A72%3AE3%3AC4%3A52%3ABF%3AC3%3A8D%3AD5%3A38%3AC4%3ACF%3AA4%3ABD%3AED%3A86%3A89%3A80%3AE4%3AD1%3A57%3A0F%3AA5%3AC3%3A5E%3A3D%3A84&relation=delegate_permission%2Fcommon.handle_all_urls
2026-02-10 09:42:36:852 – DEBUG – BitwardenNetworkClient – <-- 200 https://digitalassetlinks.googleapis.com/v1/assetlinks:check?source.web.site=https%3A%2F%2Fmonex.co.jp&target.androidApp.packageName=jp.co.monex.comprehensive&target.androidApp.certificate.sha256Fingerprint=10%3A40%3A80%3A57%3AFE%3AF5%3A72%3AE3%3AC4%3A52%3ABF%3AC3%3A8D%3AD5%3A38%3AC4%3ACF%3AA4%3ABD%3AED%3A86%3A89%3A80%3AE4%3AD1%3A57%3A0F%3AA5%3AC3%3A5E%3A3D%3A84&relation=delegate_permission%2Fcommon.handle_all_urls (143ms, unknown-length body)
2026-02-10 09:42:36:853 – DEBUG – m – Digital asset link validation result: linked = false
2026-02-10 09:42:39:114 – DEBUG – c – App is backgrounded
2026-02-10 09:42:42:181 – DEBUG – c – App is foregrounded

digitalassetlinks.googleapis.com fetched contents from https://monex.co.jp./.well-known/assetlinks.json. The content-type in the response header of https://monex.co.jp./.well-known/assetlinks.json was "text/plan", which should be "application/json", I guess.

<!-- gh-comment-id:3874720420 --> @isseis commented on GitHub (Feb 10, 2026): I've verified that I could create passkey for MyJCB app with 2026.1.1. I'm still experiencing "failed to create a new passkey" error in other apps, but according to the logs, the root cause appears to be different. ``` Bitwarden Android - Password Manager Log Start Time: 2026-02-10 09:42:24:662 Log Duration: 1h App Version: 2026.1.1 (21176) Build: release/standard Operating System: 16 (36) Device: samsung SM-F956Q Fingerprint: samsung/q6qjpnw/q6q:16/BP2A.250605.031.A3/F956QOPU1CYKD:user/release-keys 2026-02-10 09:42:24:668 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-02-10 09:42:24:668 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-02-10 09:42:24:686 – DEBUG – a – VaultUnlockedNavBarScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.settings.about.SettingsAboutRoute.Standard in com.x8bit.bitwarden.ui.platform.feature.settings.SettingsGraphRoute 2026-02-10 09:42:27:293 – DEBUG – c – App is backgrounded 2026-02-10 09:42:33:005 – DEBUG – a – Parsing AssistStructure -- 6320 2026-02-10 09:42:33:005 – DEBUG – BitwardenAutofillService – Begin processing Autofill fill request -- 6320 2026-02-10 09:42:33:007 – DEBUG – d – Autofill request success: Unfillable -- 6320 2026-02-10 09:42:35:236 – DEBUG – BitwardenCredentialProviderService – Create credential request received. 2026-02-10 09:42:36:667 – DEBUG – c – App is foregrounded 2026-02-10 09:42:36:673 – DEBUG – a – MainActivity destination changed: com.x8bit.bitwarden.ui.platform.feature.rootnav.RootNavigationRoute 2026-02-10 09:42:36:681 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.splash.SplashRoute 2026-02-10 09:42:36:692 – DEBUG – a – RootNavScreen destination changed: com.x8bit.bitwarden.ui.platform.feature.vaultunlockednavbar.VaultUnlockedNavbarRoute in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-02-10 09:42:36:693 – DEBUG – a – RootNavScreen destination changed: nq.k0/{encodedData} in com.x8bit.bitwarden.ui.platform.feature.vaultunlocked.VaultUnlockedGraphRoute 2026-02-10 09:42:36:710 – DEBUG – BitwardenNetworkClient – --> GET https://digitalassetlinks.googleapis.com/v1/assetlinks:check?source.web.site=https%3A%2F%2Fmonex.co.jp&target.androidApp.packageName=jp.co.monex.comprehensive&target.androidApp.certificate.sha256Fingerprint=10%3A40%3A80%3A57%3AFE%3AF5%3A72%3AE3%3AC4%3A52%3ABF%3AC3%3A8D%3AD5%3A38%3AC4%3ACF%3AA4%3ABD%3AED%3A86%3A89%3A80%3AE4%3AD1%3A57%3A0F%3AA5%3AC3%3A5E%3A3D%3A84&relation=delegate_permission%2Fcommon.handle_all_urls 2026-02-10 09:42:36:852 – DEBUG – BitwardenNetworkClient – <-- 200 https://digitalassetlinks.googleapis.com/v1/assetlinks:check?source.web.site=https%3A%2F%2Fmonex.co.jp&target.androidApp.packageName=jp.co.monex.comprehensive&target.androidApp.certificate.sha256Fingerprint=10%3A40%3A80%3A57%3AFE%3AF5%3A72%3AE3%3AC4%3A52%3ABF%3AC3%3A8D%3AD5%3A38%3AC4%3ACF%3AA4%3ABD%3AED%3A86%3A89%3A80%3AE4%3AD1%3A57%3A0F%3AA5%3AC3%3A5E%3A3D%3A84&relation=delegate_permission%2Fcommon.handle_all_urls (143ms, unknown-length body) 2026-02-10 09:42:36:853 – DEBUG – m – Digital asset link validation result: linked = false 2026-02-10 09:42:39:114 – DEBUG – c – App is backgrounded 2026-02-10 09:42:42:181 – DEBUG – c – App is foregrounded ``` `digitalassetlinks.googleapis.com` fetched contents from `https://monex.co.jp./.well-known/assetlinks.json`. The content-type in the response header of `https://monex.co.jp./.well-known/assetlinks.json` was "text/plan", which should be "application/json", I guess.
Author
Owner

@ToniCipriani commented on GitHub (Feb 10, 2026):

Tested EQ Bank and AliExpress, both worked fine with 2026.1.1 installed from Github.

<!-- gh-comment-id:3880389674 --> @ToniCipriani commented on GitHub (Feb 10, 2026): Tested EQ Bank and AliExpress, both worked fine with 2026.1.1 installed from Github.
Author
Owner

@ReinForce64 commented on GitHub (Feb 22, 2026):

Not working in bitwarden 2026.2 on android.

"An error has occurred.
Passkeys are not supported for this app."

When trying to add a passkey for notion.

<!-- gh-comment-id:3940989398 --> @ReinForce64 commented on GitHub (Feb 22, 2026): Not working in bitwarden 2026.2 on android. "An error has occurred. Passkeys are not supported for this app." When trying to add a passkey for notion.
Author
Owner

@pamperer562580892423 commented on GitHub (Feb 22, 2026):

@ReinForce64:

"An error has occurred. Passkeys are not supported for this app."

When trying to add a passkey for notion.

The Notion app might have never worked... I don't think there is a separate GitHub issue for it, but it was at least mentioned in this comment by a BW developer (@SaintPatrck).

<!-- gh-comment-id:3941201563 --> @pamperer562580892423 commented on GitHub (Feb 22, 2026): @ReinForce64: > "An error has occurred. Passkeys are not supported for this app." > > When trying to add a passkey for notion. The Notion app might have never worked... I don't think there is a separate GitHub issue for it, but it was at least mentioned [in this comment](https://github.com/bitwarden/android/issues/5329#issuecomment-3557970040) by a BW developer (@SaintPatrck).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#21708