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

Abierto
  • ¿Algo no está bien?
#7,451 5 comentarios 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
android, kotlin
Área
authentication, mobile

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Kotlin
Estrellas
9.6k
Forks
1.1k
Merge medio
2 d 13 h
PR fusionados (30 d)
52

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de bitwarden/android

Todos los issues de bitwarden/android

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.