android, desktop, ios: clear migration errors for oversized database and low storage#7059
Open
Narasimha-sc wants to merge 1 commit into
Open
android, desktop, ios: clear migration errors for oversized database and low storage#7059Narasimha-sc wants to merge 1 commit into
Narasimha-sc wants to merge 1 commit into
Conversation
Narasimha-sc
force-pushed
the
nd/migrate-device-size-checks
branch
from
5cd1403 to
e715afa
Compare
Narasimha-sc
force-pushed
the
nd/migrate-device-size-checks
branch
from
e715afa to
5ff8651
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Migrating a database whose archive exceeds the 5 GB XFTP hard limit only failed at the upload step with a generic, unactionable "Error uploading the archive" — after the whole archive had already been exported — and there was no check for free disk space before exporting. The migration upload path never validated the archive size before upload (the core's hard-limit rejection surfaced only as a raw error string) and never checked available storage. This adds a clear "database is too large" error before upload and an advisory low-storage confirmation before export, on Android, desktop and iOS.