You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So far, I have only observed this behavior using a passkey on amazon.com.
From an iPhone, use the Bitwarden app to log into Amazon using a previously created Amazon account passkey.
Sync the vault from within the Bitwarden app.
Expected Result
It is expected that the "Created" timestamp for the login's passkey entry does not change from its actual creation timestamp.
Actual Result
In Bitwarden, the "Created" timestamp for the passkey is replaced with the current log-in time. (This only appears after syncing or logging out/in).
The created date shown by Amazon for the passkey does not change, and comparing the passkey value in unencrypted vault exports before and after logging into the Amazon account with the passkey confirm that the passkey does not change, i.e. a new one was not in fact created.
Screenshots or Videos
No response
Additional Context
Only observed so far on amazon.com. Does not occur when logging into amazon.com using Chrome extension (2024.10.1) (on macOS).
Build Version
2024.10.0 (1651)
Environment Details
iPhone SE 3rd Generation.
iOS 18.0.1
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.
The text was updated successfully, but these errors were encountered:
Steps To Reproduce
So far, I have only observed this behavior using a passkey on amazon.com.
Expected Result
It is expected that the "Created" timestamp for the login's passkey entry does not change from its actual creation timestamp.
Actual Result
In Bitwarden, the "Created" timestamp for the passkey is replaced with the current log-in time. (This only appears after syncing or logging out/in).
The created date shown by Amazon for the passkey does not change, and comparing the passkey value in unencrypted vault exports before and after logging into the Amazon account with the passkey confirm that the passkey does not change, i.e. a new one was not in fact created.
Screenshots or Videos
No response
Additional Context
Only observed so far on amazon.com. Does not occur when logging into amazon.com using Chrome extension (2024.10.1) (on macOS).
Build Version
2024.10.0 (1651)
Environment Details
iPhone SE 3rd Generation.
iOS 18.0.1
Issue Tracking Info
The text was updated successfully, but these errors were encountered: