Where does this message get dispatched? Is that in a later diff?

As far as I am concerned you can get these data directly by calling library API and defining them here is redundant. cc @kamil

Same as here: https://phab.comm.dev/D11044#inline-67443. Calls to sqliteQueryExecutor need special error handling.

I think you even should. THe library doesn't give guarantees that persist will be stored under this key every time.

Sorry, I missed this comment. I've been dispatching the message manually for now:

const response = await databaseModule.schedule({
  type: workerRequestMessageTypes.BACKUP_RESTORE,
  authMetadata: {
    userID: currentUserInfo.id,
    deviceID: 'dummy',
    accessToken: 'dummy',
  },
  backupID: 'XXX',
  backupDataKey:'XXX',
  backupLogDataKey: 'XXX',
});

But it might make sense to add some testing staff-only screen (like tunnelbroker or backup on native) to call it (with backupID, backupDataKey, backupLogDataKey specified by the user).

You can see that the library:

• Creates the key from combination of rootKey and rootKeyPrefix link
• The default value for rootKeyPrefix is persist: link

While the library exposes the default value in the constants file, I think the way I did it here is safer.

If in the future for some reason of the comm developer will want to change the key prefix they will realise that they need to change the restore logic too.

I'm passing the rootKeyPrefix defined here as a config to the redux persist so the library can't change it without us noticing -> that would be a breaking change.