github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-11-09 10:34:18 -06:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

Passkeys are not working correctly with Lowes.com, the Lowe's iOS app, and/or the v2024.3.3 BitWarden beta app #1841

New Issue
Closed
opened 2025-11-26 22:59:31 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-26 22:59:31 -06:00
Owner
Copy Link
Copy Source

Originally created by @ZPNRG on GitHub (Apr 7, 2024).

Steps To Reproduce

Passkeys are not really working correctly for Lowes.com and/or the Lowe's iOS app. I do not know if the problem is with the Lowe's website backend, the Lowe's app (and/or backend), or the BitWarden iOS app (v2024.3.3, which is currently in beta).

Lowe's iOS app v24.4.2
Windows 10 v22H2 (Build 19045.4170)
Brave v1.64.116
BitWarden Chrome extension v2024.2.1

If I create a Passkey from Windows using Brave and save it to BitWarden (via the Chrome/Brave BitWarden extension), then I can log in and out of Lowes.com in Windows/Brave just fine using the Passkey. I can also log into the Lowe's iOS app fine using my Lowe's username/password. The app then bugs me about setting up a Passkey, which has already been done.

So, finally, I decided to set up a Passkey from the Lowe's iOS app and save it to my iOS BitWarden app, overwriting the Passkey that had already been created from Windows/Brave and stored in BitWarden (via the Chrome/Brave extension). I can then log into the Lowe's iOS app using the Passkey stored in BitWarden fine. However, if I then try to log into Lowes.com from Windows/Brave, my BitWarden Chrome/Brave extension says it doesn't have a Passkey for Lowes.com and I cannot fall-back to the username/password. So, I cannot log in.

After all of that, I went back and re-created the Passkey from Windows using Brave and saved it to BitWarden (via the Chrome/Brave BitWarden extension), overwriting the Passkey that had been created via the Lowe's iOS app. Then, I could again log in and out of Lowes.com in Windows/Brave just fine using the Passkey. I could also again log into the Lowe's iOS app fine using my Lowe's username/password. Sadly, again, the Lowe's iOS app then bugs me about setting up a Passkey, which has already been done.

Expected Result

Should be able to create Passkey and save it using Windows/Brave/Chrome BitWarden extension and it work properly both on Windows/Brave and in the Lowe's iOS app. Or create via the Lowe's iOS app and save it to BitWarden using the BitWarden iOS app and then it work (be recognized) properly on iOS and in Windows/Brave on Lowes.com.

Actual Result

Described above.

Screenshots or Videos

No response

Additional Context

No response

Operating System

iOS

Operating System Version

17.4.1

Device

iPhone 15 Pro Max

Build Version

2024.3.3

Beta

  • Using a pre-release version of the application.
Originally created by @ZPNRG on GitHub (Apr 7, 2024). ### Steps To Reproduce Passkeys are not really working correctly for Lowes.com and/or the Lowe's iOS app. I do not know if the problem is with the Lowe's website backend, the Lowe's app (and/or backend), or the BitWarden iOS app (v2024.3.3, which is currently in beta). Lowe's iOS app v24.4.2 Windows 10 v22H2 (Build 19045.4170) Brave v1.64.116 BitWarden Chrome extension v2024.2.1 If I create a Passkey from Windows using Brave and save it to BitWarden (via the Chrome/Brave BitWarden extension), then I can log in and out of Lowes.com in Windows/Brave just fine using the Passkey. I can also log into the Lowe's iOS app fine using my Lowe's username/password. The app then bugs me about setting up a Passkey, which has already been done. So, finally, I decided to set up a Passkey from the Lowe's iOS app and save it to my iOS BitWarden app, overwriting the Passkey that had already been created from Windows/Brave and stored in BitWarden (via the Chrome/Brave extension). I can then log into the Lowe's iOS app using the Passkey stored in BitWarden fine. However, if I then try to log into Lowes.com from Windows/Brave, my BitWarden Chrome/Brave extension says it doesn't have a Passkey for Lowes.com and I cannot fall-back to the username/password. So, I cannot log in. After all of that, I went back and re-created the Passkey from Windows using Brave and saved it to BitWarden (via the Chrome/Brave BitWarden extension), overwriting the Passkey that had been created via the Lowe's iOS app. Then, I could again log in and out of Lowes.com in Windows/Brave just fine using the Passkey. I could also again log into the Lowe's iOS app fine using my Lowe's username/password. Sadly, again, the Lowe's iOS app then bugs me about setting up a Passkey, which has already been done. ### Expected Result Should be able to create Passkey and save it using Windows/Brave/Chrome BitWarden extension and it work properly both on Windows/Brave and in the Lowe's iOS app. Or create via the Lowe's iOS app and save it to BitWarden using the BitWarden iOS app and then it work (be recognized) properly on iOS and in Windows/Brave on Lowes.com. ### Actual Result Described above. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System iOS ### Operating System Version 17.4.1 ### Device iPhone 15 Pro Max ### Build Version 2024.3.3 ### Beta - [X] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:59:31 -06:00
GiteaMirror commented 2025-11-26 22:59:32 -06:00
Author
Owner
Copy Link
Copy Source

@ZPNRG commented on GitHub (Apr 7, 2024):

NOTE: I did submit this feedback via the TestFlight feedback option, but having used many app in beta via TestFlight for almost 10 years, I've found that submitting feedback either doesn't work or is very flaky. I have no idea if the submitted feedback was received or not. So, I'm creating this ticket to make sure the issue I am seeing is documented. The problem might not at all be on BitWarden's end. It might be purely with the Lowes.com website and/or the Lowe's iOS app itself. That I do not know. But I'm reporting to you since the BitWarden iOS app with Passkeys support is in beta and I am testing it.

@ZPNRG commented on GitHub (Apr 7, 2024): NOTE: I did submit this feedback via the TestFlight feedback option, but having used many app in beta via TestFlight for almost 10 years, I've found that submitting feedback either doesn't work or is very flaky. I have no idea if the submitted feedback was received or not. So, I'm creating this ticket to make sure the issue I am seeing is documented. The problem might not at all be on BitWarden's end. It might be purely with the Lowes.com website and/or the Lowe's iOS app itself. That I do not know. But I'm reporting to you since the BitWarden iOS app with Passkeys support is in beta and I am testing it.
GiteaMirror commented 2025-11-26 22:59:32 -06:00
Author
Owner
Copy Link
Copy Source

@SergeantConfused commented on GitHub (Apr 8, 2024):

Hi @ZPNRG,

Thank you for this report. This matter has been escalated for further investigation; If you have any further information that you think may assist us, please feel free to post it below.

Thank you again,

@SergeantConfused commented on GitHub (Apr 8, 2024): Hi @ZPNRG, Thank you for this report. This matter has been escalated for further investigation; If you have any further information that you think may assist us, please feel free to post it below. Thank you again,
GiteaMirror commented 2025-11-26 22:59:32 -06:00
Author
Owner
Copy Link
Copy Source

@micahblut commented on GitHub (Apr 17, 2024):

@ZPNRG thank you for raising this issue here and in the testflight feedback! We've done some investigating and it looks like the issues lies in the implementation of passkeys between the Lowes app and website, which are using different RpIds when being set up. I suggest submitting some feedback to the role provider (Lowes) as I imagine this issue would be affecting users regardless of whether they are using Bitwarden or not.

@micahblut commented on GitHub (Apr 17, 2024): @ZPNRG thank you for raising this issue here and in the testflight feedback! We've done some investigating and it looks like the issues lies in the implementation of passkeys between the Lowes app and website, which are using different RpIds when being set up. I suggest submitting some feedback to the role provider (Lowes) as I imagine this issue would be affecting users regardless of whether they are using Bitwarden or not.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No labels bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#1841