Page MenuHomePhabricator

[CommCoreModule] avoid calling Backup Service to get backup secrets
ClosedPublic

Authored by kamil on Nov 22 2024, 2:23 AM.
Tags
None
Referenced Files
F3521251: D14002.id.diff
Mon, Dec 23, 2:46 AM
Unknown Object (File)
Tue, Dec 17, 10:39 PM
Unknown Object (File)
Sat, Dec 14, 2:25 PM
Unknown Object (File)
Fri, Dec 13, 8:39 PM
Unknown Object (File)
Fri, Dec 13, 1:47 AM
Unknown Object (File)
Mon, Dec 9, 10:40 PM
Unknown Object (File)
Sat, Dec 7, 9:26 PM
Unknown Object (File)
Sat, Dec 7, 3:10 PM
Subscribers

Details

Summary

Part of ENG-9656

It was identified in https://phab.comm.dev/D13849#387643.

We don't need to call the Backup Service, we have the data locally.

retrieveBackupKeys will be refactored later in the stack and used in the Restore protocol to fetch the User Keys from the backup service.

Depends on D14001

Test Plan

Tested creating backup and secondary device login

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
native/profile/secondary-device-qr-code-scanner.react.js
180–182

Previously we had validation because we received a string, which was downloaded from the Blob service and decrypted. Right now we have a JSI object so there is need to validate this.

kamil published this revision for review.Nov 22 2024, 4:00 AM
This revision is now accepted and ready to land.Tue, Nov 26, 1:30 AM