[GH-ISSUE #5340] Add passkey support for Grab app #21508

Closed
opened 2026-04-16 22:02:08 -05:00 by GiteaMirror · 7 comments
Owner

Originally created by @Edmund52 on GitHub (Jun 10, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/5340

Origin

Native Application (non-browser app)

Web URL or App name

com.grabtaxi.passenger

Passkey Action

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

Build Information

© Bitwarden Inc. 2015-2025

Version: 2025.5.0 (20269)
📱 TECNO TECNO CM7 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.05-rc20@1e665db8aeb92989bdc7e312506cddd4887cde8e
💻 build source: bitwarden/android/actions/runs/15300207138/attempts/1

Additional Information

Bitwarden shows passkey is not supported for this app

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 @Edmund52 on GitHub (Jun 10, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/5340 ### Origin Native Application (non-browser app) ### Web URL or App name com.grabtaxi.passenger ### Passkey Action - [x] Creating new passkey (Registration) - [ ] Signing in (Authentication) ### Build Information © Bitwarden Inc. 2015-2025 Version: 2025.5.0 (20269) 📱 TECNO TECNO CM7 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.05-rc20@1e665db8aeb92989bdc7e312506cddd4887cde8e 💻 build source: bitwarden/android/actions/runs/15300207138/attempts/1 ### Additional Information Bitwarden shows passkey is not supported for this app ### 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:02:08 -05:00
Author
Owner

@bitwarden-bot commented on GitHub (Jun 10, 2025):

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

<!-- gh-comment-id:2957478489 --> @bitwarden-bot commented on GitHub (Jun 10, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-22552
Author
Owner

@abergs commented on GitHub (Jun 10, 2025):

Thanks for posting this @Edmund52.
I don't know Grab, but are you able to create a passkey using the browser extension / iOS and use that to sign in to the android app?

Just trying to understand if it's only "creating a new passkey" that doesn't work.

<!-- gh-comment-id:2957926120 --> @abergs commented on GitHub (Jun 10, 2025): Thanks for posting this @Edmund52. I don't know Grab, but are you able to create a passkey using the browser extension / iOS and use that to sign in to the android app? Just trying to understand if it's only "creating a new passkey" that doesn't work.
Author
Owner

@Edmund52 commented on GitHub (Jun 10, 2025):

I cannot create passkey on the website because seems like this is only on the app only, although you can login food.grab.com with passkey. I don't have IOS devices to test.

https://engineering.grab.com/embracing-passwordless-authentication-with-passkey

based on this website seems like only google password manager and icloud are supported?

<!-- gh-comment-id:2958270725 --> @Edmund52 commented on GitHub (Jun 10, 2025): I cannot create passkey on the website because seems like this is only on the app only, although you can login food.grab.com with passkey. I don't have IOS devices to test. https://engineering.grab.com/embracing-passwordless-authentication-with-passkey based on this website seems like only google password manager and icloud are supported?
Author
Owner

@rmcdowell-bitwarden commented on GitHub (Jun 13, 2025):

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:2969458823 --> @rmcdowell-bitwarden commented on GitHub (Jun 13, 2025): 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

@Edmund52 commented on GitHub (Jun 28, 2025):

© Bitwarden Inc. 2015-2025

Version: 2025.6.0 (20358)
📱 TECNO TECNO CM7 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.06-rc21@b5b022caaad33390c31b3021b2c1205925b0e1a2
💻 build source: bitwarden/android/actions/runs/15831797213/attempts/1

I tried it again and it showed this

Image

<!-- gh-comment-id:3014831210 --> @Edmund52 commented on GitHub (Jun 28, 2025): © Bitwarden Inc. 2015-2025 Version: 2025.6.0 (20358) 📱 TECNO TECNO CM7 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.06-rc21@b5b022caaad33390c31b3021b2c1205925b0e1a2 💻 build source: bitwarden/android/actions/runs/15831797213/attempts/1 I tried it again and it showed this ![Image](https://github.com/user-attachments/assets/acddeeb2-d2f1-42ca-bfda-91a6e8e7ccec)
Author
Owner

@Edmund52 commented on GitHub (Jun 29, 2025):

@rmcdowell-bitwarden can you test it again? because it shows passkey operation failed because relying party cannot ve identified.

would appreciate any response, i will open a new issue in wednesday assuming 2 working days.

<!-- gh-comment-id:3016753234 --> @Edmund52 commented on GitHub (Jun 29, 2025): @rmcdowell-bitwarden can you test it again? because it shows passkey operation failed because relying party cannot ve identified. would appreciate any response, i will open a new issue in wednesday assuming 2 working days.
Author
Owner

@rmcdowell-bitwarden commented on GitHub (Jun 30, 2025):

@Edmund52 I tested this again and I still receive the same result on the most recent version, this would make sense as the pull request (https://github.com/bitwarden/android/pull/5363) that closed this was not included in our most recent release (version 2025.6.0). You can see the items that were addressed here: https://github.com/bitwarden/android/releases

The ID in our internal system for this is: PM-22552 (which is included in the bitwarden-bot response when a new issue is opened).

I am not a member of our Engineering team, but this was probably resolved after the deadline for inclusion in the release of version 2025.6.0

I would expect this to be included in our next major release, you can subscribe to our Bitwarden releases notes, which will notify you when a new version of Bitwarden has been released. https://bitwarden.com/help/releasenotes/

<!-- gh-comment-id:3017639481 --> @rmcdowell-bitwarden commented on GitHub (Jun 30, 2025): @Edmund52 I tested this again and I still receive the same result on the most recent version, this would make sense as the pull request (https://github.com/bitwarden/android/pull/5363) that closed this was not included in our most recent release (version 2025.6.0). You can see the items that were addressed here: https://github.com/bitwarden/android/releases The ID in our internal system for this is: PM-22552 (which is included in the bitwarden-bot response when a new issue is opened). I am not a member of our Engineering team, but this was probably resolved after the deadline for inclusion in the release of version 2025.6.0 I would expect this to be included in our next major release, you can subscribe to our Bitwarden releases notes, which will notify you when a new version of Bitwarden has been released. https://bitwarden.com/help/releasenotes/
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#21508