[PM-44587] [Critical] Native Android passkey creation is still broadly broken — “missing asset links” across most apps
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 20/100
- issue の種類
- バグ
- 明瞭さ
- 説明が足りない
- 活発さ
- 活発
- 領域
- authentication, mobile
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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.
- 主要言語
- Kotlin
- スター
- 9.6k
- フォーク
- 1.1k
- 平均マージ
- 2日 13時間
- マージ済み PR(30日)
- 52
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
bitwarden/android のほかの issue
-
app:password-manager bug-passkey
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
bitwarden/android#7575 · コメント 4 件 ·
メンテナーはふだん 1 日以内に返信
-
app:password-manager bug-passkey
難易度 4/5 3〜5日 初心者へのやさしさ 22/100
bitwarden/android#7558 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
app:password-manager bug
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
bitwarden/android#7525 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
app:password-manager bug-passkey
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
bitwarden/android#7513 · コメント 4 件 ·
メンテナーはふだん 1 日以内に返信
-
[PM-45169] Autofill crash on Android 10 in 2026.9.1 — InlinePresentationSpec NoClassDefFoundErrorオープンapp:password-manager bug
難易度 3/5 1〜2日 初心者へのやさしさ 45/100
bitwarden/android#7489 · コメント 9 件 · リアクション 2 件 ·
メンテナーはふだん 1 日以内に返信
bitwarden/android の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 86/100
liberation-data/drivine-cypher-spec#67 ·
メンテナーはふだん 1 日以内に返信
-
feature
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
-
documentation good first issue help wanted P2 roadmap-v4
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
maziyarpanahi/openmed#5425 ·
メンテナーはふだん 3 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
OneBusAway/vehicle-positions#250 ·
メンテナーはふだん 1 日以内に返信
-
android cleanup good first issue
難易度 1/5 1〜3時間 初心者へのやさしさ 86/100