[PB-4737]: fix/add userUuid to BackupData structure #1613
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Deploying drive-web with
|
| Latest commit: |
0e58cd0
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://fd4e4548.drive-web.pages.dev |
| Branch Preview URL: | https://fix-include-uuid-in-account.drive-web.pages.dev |
jzunigax2
changed the title
jzunigax2
force-pushed
the
fix/include-uuid-in-account-recovery-v2
branch
from
a6e324c to
cf56488
Compare
|
CandelR
approved these changes
Aug 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add a new field to the backup file json, called userUuid. This is in order to perform a check on the backend, and avoid the user potentially uploading an incorrect backup file in the rare case they have multiple Internxt accounts.
This change is backwards compatible in case #1508 goes live without this fix. Meaning that backup files that are in the new json format but dont have this new uuid field are still allowed to go through, we just simply don't perform this validation in those cases
Related Issues
https://inxt.atlassian.net/browse/PB-4737
Related Pull Requests
Checklist
Testing Process
Saved the new backup file format. Edited the uuid purposely making it not match and verify account recovery doesnt go through. Alternatively, removed the uuid field from the backup file and checked that recovery goes through
Additional Notes