Richard_M
(Richard M)
March 19, 2025, 8:04pm
1
Starting this morning, when I go into the devices tab in the Bitwarden Vault, I get multiple error pop ups stating " An error has occured. Invalid device data". The popus then go away.
I rebooted cleared cache on all browsers I tested (Edge, Chrome and Firefox) along with trying on a mobile based browser.
Any idea what this is? Also the devices sign is showing me logged in an older session not the current one, so it is not accurate. I see no unusual activity in my sign ins. Thanks
Hi Richard and welcome to the community!
An error has occured. Invalid device data
I am getting the same thing, and I think itโs a bug. I tried on a test account which didnโt have this problem, so I am not sure how to file a bug that could be duplicated. I am planning to ignore it since I donโt usually look at this screen.
There was a bug report about this:
opened 11:42PM - 22 Mar 25 UTC
closed 12:16PM - 25 Mar 25 UTC
bug
web
### Steps To Reproduce
1. Go to Settings -> Security -> Devices
### Expected โฆ Result
Shows list of previous log-ins, including Android's, not throwing up errors.
### Actual Result
The list shown doesn't include previous Android's logins, throwing up errors "An error has occured. Invalid device data," possibly the number of errors relating to the the number of Android logins that have been logged.
### Screenshots or Videos

### Additional Context
This also has been reported in the community:
https://community.bitwarden.com/t/2fa-fido2-not-working-on-android/83009
### Operating System
Windows
### Operating System Version
Windows 11 Pro 24H2 26100.3194
### Web Browser
Firefox
### Browser Version
128.8.0esr
### Build Version
2025.3.0
### 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.
And that was recently closed, as there will be a fix with the next releases:
main
โ fix/check-device-id-falsy-values
opened 05:43PM - 20 Mar 25 UTC
## ๐๏ธ Tracking
Follow up from feedback for https://bitwarden.atlassian.neโฆ t/browse/PM-18757
## ๐ Objective
Checks the device `id` and `creationDate` for empty strings (or any falsey values) since they are strings (defined in `libs/common/src/auth/abstractions/devices/views/device.view.ts`).
## โฐ Reminders before review
- Contributor guidelines followed
- All formatters and local linters executed and passed
- Written new unit and / or integration tests where applicable
- Protected functional changes with optionality (feature flags)
- Used internationalization (i18n) for all UI strings
- CI builds passed
- Communicated to DevOps any deployment requirements
- Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team
## ๐ฆฎ Reviewer guidelines
- ๐ (`:+1:`) or similar for great changes
- ๐ (`:memo:`) or โน๏ธ (`:information_source:`) for notes or general info
- โ (`:question:`) for questions
- ๐ค (`:thinking:`) or ๐ญ (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
- ๐จ (`:art:`) for suggestions / improvements
- โ (`:x:`) or โ ๏ธ (`:warning:`) for more significant problems or concerns needing attention
- ๐ฑ (`:seedling:`) or โป๏ธ (`:recycle:`) for future improvements or indications of technical debt
- โ (`:pick:`) for minor or nitpick changes
1 Like