[GH-ISSUE #6293] [PM-30106] Password Protected Export can't be imported #50504

Closed
opened 2026-05-01 13:16:48 -05:00 by GiteaMirror · 9 comments
Owner

Originally created by @pamperer562580892423 on GitHub (Dec 22, 2025).
Original GitHub issue: https://github.com/bitwarden/android/issues/6293

Steps To Reproduce

  1. Android app: Go to Settings --> Vault --> Export
  2. Export your personal vault (!) as a password protected JSON.
  3. Go to (e.g.) the web vault and try to import it (as Bitwarden JSON) and into "My vault".

I don't know if this matters for reproduction or not, but I tried to import into a folder.

Expected Result

The export gets imported successfully.

Actual Result

Though the passwords should be identical (I tested it several times and there shouldn't be any typos involved), I get an import error:

Image

Screenshots or Videos

Additional Context

This (https://www.reddit.com/r/Bitwarden/comments/1pt0kf7/error_when_trying_to_import_encrypted_json_file/) report on Reddit made me test it myself, so it's not only one person experiencing this as it seems.

PS: And I reported this in the Android section now, as I would (primarily) think that the Android app seems to have some kind of an exporting-bug. - But of course, it could also be, that the web vault has an importing-bug here... Or both...

PPS: The file password is a passphrase that also contains special characters, but nothing too "fancy". As I tested it with my own vault data, I didn't want to test for now if it would work with a modified password e.g. only consisting of letters.

Build Version

2025.12.0

What server are you connecting to?

EU

Self-host Server Version

(not self-hosting)

Environment Details

© Bitwarden Inc. 2015-2025

Version: 2025.12.0 (21003)
📱 Fairphone FP5 🤖 15@35 📦 prod
🧱 commit: bitwarden/android/release/2025.12-rc40@f02b374e989600a8458d2884abd2526244241c8a
💻 build source: bitwarden/android/actions/runs/19830126705/attempts/1
🦀 SDK: 1.0.0-3928-2cca3d46
🌩 Server: 2025.12.0 @ EU

--> And the web vault I tested the import on was the current EU server region web vault version 2025.12.0.

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 @pamperer562580892423 on GitHub (Dec 22, 2025). Original GitHub issue: https://github.com/bitwarden/android/issues/6293 ### Steps To Reproduce 1. Android app: Go to Settings --> Vault --> Export 2. Export your personal vault (!) as a password protected JSON. 3. Go to (e.g.) the web vault and try to import it (as Bitwarden JSON) and into "My vault". I don't know if this matters for reproduction or not, but I tried to import into a folder. ### Expected Result The export gets imported successfully. ### Actual Result Though the passwords should be identical (I tested it several times and there shouldn't be any typos involved), I get an import error: <img width="558" height="326" alt="Image" src="https://github.com/user-attachments/assets/4b073384-3596-4800-909d-7a8e9f2afce4" /> ### Screenshots or Videos ### Additional Context This (https://www.reddit.com/r/Bitwarden/comments/1pt0kf7/error_when_trying_to_import_encrypted_json_file/) report on Reddit made me test it myself, so it's not only one person experiencing this as it seems. **PS: And I reported this in the Android section now, as I would (primarily) think that the Android app seems to have some kind of an exporting-bug. - But of course, it could also be, that the web vault has an importing-bug here... Or both...** PPS: The file password is a passphrase that also contains special characters, but nothing too "fancy". As I tested it with my own vault data, I didn't want to test for now if it would work with a modified password e.g. only consisting of letters. ### Build Version 2025.12.0 ### What server are you connecting to? EU ### Self-host Server Version (not self-hosting) ### Environment Details © Bitwarden Inc. 2015-2025 Version: 2025.12.0 (21003) 📱 Fairphone FP5 🤖 15@35 📦 prod 🧱 commit: bitwarden/android/release/2025.12-rc40@f02b374e989600a8458d2884abd2526244241c8a 💻 build source: bitwarden/android/actions/runs/19830126705/attempts/1 🦀 SDK: 1.0.0-3928-2cca3d46 🌩 Server: 2025.12.0 @ EU --> And the web vault I tested the import on was the current EU server region web vault version 2025.12.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.
GiteaMirror added the bugapp:password-manager labels 2026-05-01 13:16:48 -05:00
Author
Owner

@bitwarden-bot commented on GitHub (Dec 22, 2025):

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

<!-- gh-comment-id:3682536979 --> @bitwarden-bot commented on GitHub (Dec 22, 2025): Thank you for your report! We've added this to our internal board for review. ID: [PM-30106](https://bitwarden.atlassian.net/browse/PM-30106) [PM-30106]: https://bitwarden.atlassian.net/browse/PM-30106?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
Author
Owner

@maxkpower commented on GitHub (Dec 22, 2025):

Thanks for raising this issue! I was able to reproduce it on our end, we've prioritized the fix and are investigating.

<!-- gh-comment-id:3682916902 --> @maxkpower commented on GitHub (Dec 22, 2025): Thanks for raising this issue! I was able to reproduce it on our end, we've prioritized the fix and are investigating.
Author
Owner

@pamperer562580892423 commented on GitHub (Dec 22, 2025):

@maxkpower Ha, that was quick. Thanks!

<!-- gh-comment-id:3682971062 --> @pamperer562580892423 commented on GitHub (Dec 22, 2025): @maxkpower Ha, that was quick. Thanks!
Author
Owner

@pamperer562580892423 commented on GitHub (Dec 22, 2025):

@maxkpower Ah, if you even can say that at this point, I think it would be good to know for iOS users, if it's also an issue on the iOS mobile app.

<!-- gh-comment-id:3682982795 --> @pamperer562580892423 commented on GitHub (Dec 22, 2025): @maxkpower Ah, if you even can say that at this point, I think it would be good to know for iOS users, if it's also an issue on the iOS mobile app.
Author
Owner

@maxkpower commented on GitHub (Dec 22, 2025):

I was able to replicate it on iOS as well.

<!-- gh-comment-id:3683270891 --> @maxkpower commented on GitHub (Dec 22, 2025): I was able to replicate it on iOS as well.
Author
Owner

@quexten commented on GitHub (Dec 24, 2025):

Related SDK fix: https://github.com/bitwarden/sdk-internal/pull/636

<!-- gh-comment-id:3690234369 --> @quexten commented on GitHub (Dec 24, 2025): Related SDK fix: https://github.com/bitwarden/sdk-internal/pull/636
Author
Owner

@aj-rosado commented on GitHub (Dec 30, 2025):

The sdk fix has been integrated into the mobile versions on https://github.com/bitwarden/android/pull/6300 and https://github.com/bitwarden/ios/pull/2217 and this will be fixed on the next release. 🎉

Thank you for your contribution.

<!-- gh-comment-id:3699009663 --> @aj-rosado commented on GitHub (Dec 30, 2025): The sdk fix has been integrated into the mobile versions on https://github.com/bitwarden/android/pull/6300 and https://github.com/bitwarden/ios/pull/2217 and this will be fixed on the next release. 🎉 Thank you for your contribution.
Author
Owner

@tennkou commented on GitHub (Apr 3, 2026):

Is there any way to restore or decrypt the encrypted files exported from this version of the app?

<!-- gh-comment-id:4183086414 --> @tennkou commented on GitHub (Apr 3, 2026): Is there any way to restore or decrypt the encrypted files exported from this version of the app?
Author
Owner

@tennkou commented on GitHub (Apr 3, 2026):

Is there any way to restore or decrypt the encrypted files exported from this version of the app?

I have solved this problem by writing a Python script to decrypt the wrongly formatted JSON, so there is no need to pay attention to it again.

<!-- gh-comment-id:4183375146 --> @tennkou commented on GitHub (Apr 3, 2026): > Is there any way to restore or decrypt the encrypted files exported from this version of the app? I have solved this problem by writing a Python script to decrypt the wrongly formatted JSON, so there is no need to pay attention to it again.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#50504