Page MenuHomePhabricator

[client-backup] implement backup handler
ClosedPublic

Authored by kamil on Aug 29 2023, 2:52 AM.
Tags
None
Referenced Files
F6178705: D9003.id30752.diff
Wed, Apr 23, 4:50 AM
Unknown Object (File)
Tue, Apr 22, 2:16 AM
Unknown Object (File)
Mon, Apr 21, 4:18 PM
Unknown Object (File)
Sun, Apr 20, 2:41 AM
Unknown Object (File)
Sat, Apr 19, 2:39 PM
Unknown Object (File)
Sat, Apr 19, 1:39 PM
Unknown Object (File)
Sat, Apr 19, 11:31 AM
Unknown Object (File)
Sat, Apr 19, 11:29 AM
Subscribers

Details

Summary

For now in UserData we store UserStore. Each time it changes we upload a new backup.

Depends on D9002

Test Plan

Test both successful and failed uploads.

image.png (789×391 px, 74 KB)

image.png (803×392 px, 87 KB)

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil edited the test plan for this revision. (Show Details)
kamil published this revision for review.Aug 29 2023, 4:05 AM
native/backup/backup-handler.js
38

What do you think?

54

Even if it's opt-in we probably don't need to display the alert on success

native/backup/backup-handler.js
54

We have so much alert spam already 😅

  • remove success info
  • rename some vars
native/backup/backup-handler.js
38

I'm not convinced, sha256Hash is more current hash, value from AsyncStorage is recent as it was computed previously 😅

54

okay, I wanted to check how frequent data is backed up - but we can always check this in backup service logs

michal added inline comments.
native/backup/backup-handler.js
38

What about mostRecentlyUploadedBackupHash? :P

This revision is now accepted and ready to land.Sep 4 2023, 8:31 AM
This revision was automatically updated to reflect the committed changes.