[PM-44587] [Critical] Native Android passkey creation is still broadly broken — “missing asset links” across most apps

Aperta
  • Qualcosa non va?
#7,451 5 commenti 2 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
android, kotlin
Ambito
authentication, mobile

Direzione di ricerca

The report describes passkey creation failures across multiple native Android apps but does not identify a code location, failing test, or reproducible app-specific case. Start by reviewing the linked reports (#4733, #5322, #6443, and #5329) and investigating the missing asset-links failure; done would require identifying and resolving the underlying recurring failure, with validation that passkey creation works across affected apps.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

app:password-manager bug-passkey
Origin

Native Application (non-browser app)

Web URL or App name

Multiple native Android applications

Passkey Action
  • Creating new passkey (Registration)
  • Signing in (Authentication)
Build Information

Latest stable release: Bitwarden Password Manager 2026.9.1 (21929)

Additional Information

Bitwarden's Android passkey support has been broken or unreliable across native apps for far too long.

The problem is still present in the latest stable release. In practice, the vast majority of native apps I have tried that support passkey creation cannot create and save a passkey through Bitwarden. They consistently fail with the same error:

Passkey operation failed because of missing asset links

This is not a minor compatibility issue. Passkeys are a core credential-management feature.
If a credential manager cannot reliably create and store credentials, that is a core product failure.

There is already a clear history of recurring failures:

  • "#4733" — asset-link failures across Amazon, PayPal and Google.
  • "#5322" — Bitwarden 2025.5.0 broke third-party app passkeys while 2025.4.0 worked.
  • "#6443" — another broad passkey regression in 2026.1.0; downgrading fixed it.
  • "#5329" — WhatsApp passkey failures have been reported since June 2025 and have recurred.

These reports span different apps, devices and releases, yet the same class of failure is still happening today.

@bitwarden/team-android @SaintPatrck

It is unacceptable that such a fundamental feature has remained this unreliable for this long, with similar failures repeatedly reaching stable releases.

A credential manager failing at credential creation is not an edge case. It is a total failure of one of the product's core responsibilities.

It also raises serious questions about Bitwarden's QA and release-validation process. If the same class of authentication failure can repeatedly reach stable releases over such a long period, then the current regression testing and release gates are clearly not sufficient for a feature this critical.

This is not another new app-specific bug report. The bugs have already been reported repeatedly. The concern is that the underlying product-quality problem has still not been resolved.

Please treat this as a high-severity reliability issue rather than continuing to handle affected apps one by one as isolated compatibility problems.

The questions are simple:

  • Why has this core functionality been allowed to remain unreliable for so long?
  • Why do similar failures keep reaching stable releases?
  • Why has the QA process failed to catch these regressions before release?
  • What is being done to prevent this from continuing?
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.
Lingua principale
Kotlin
Stelle
9.6k
Fork
1.1k
Merge medio
2g 16h
PR unite (30g)
51

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di bitwarden/android

Tutte le issue di bitwarden/android

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.