🚧 feat(Mobile): Use client side hash to check if asset exists in remote before backup #9306
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.
Allows Client to check for asset existence in remote server by making use of asset SHA-1 checksum along with API implemented in #2072
Fixes #1553
Problem statement:
When reinstalling immich app, or when asset backup already exists on immich server (through icloudpd and immich-cli for example) the client app uploads all the assets from the device which then get deduplicated from the server-side. Resulting in unnecessary upload of 20k+ assets, wasted bandwidth and time.
Change:
Assets that are already on the server are ignored and not uploaded to the server
Tests: