It's possible for a SIWE account to not have backup secrets. What happens in that case?

In this diff, I'm moving this code from one place to another and adding a place where I call it but behind a flag. I don't know what will happen if the secrets aren't there - this code was introduced in https://phab.comm.dev/D11716 so I think @marcin has more context.

Yes it is possible if user logs in but decides to skip backup message generation. We decided to use alert store to remind user to generate backup message every 24 hours if they decide to skip.

What happens in that case?

Now that backup feature works via buttons (for staff users only) it will just show alert informing that backup secrets are missing. Once I complete my backup and app lifecycle goal upload button will be deprecated and SIWE user will jest see the reminder on regular basis.

This check alone is not enough - we need to check if we are running on a primary device. Do we currently have a way to check for this information?

Important question - is this code going to execute after succesfull log in? If s that it is not going to work correctly for SIWE since SIWE user must create new backup message after log in and the screen where is happens is rendered base on information stored in Redux.

"If s" should be "If so".

I talked to @bartek and @kamil about this and you should check AuxUserStore to get information whether backup should be created. Potentially we have to expose it as a function in config.js to returns false on web and checks redux on native.

@kamil when is AuxUserStore going to be populated by identity service? Is it correct for @tomek to use it here to check if migrations are running on primary device?

After Device list updates are disseminated to all peersAuxUserStore (deviceList to be precise) should be automatically updated after receiving updates from other peers (including own devices).

Checking if we're primary device should be easier, it's the primary device's responsibility to sign and broadcast the device list updates so when this code is running we should have the newest knowledge of being/not being the primary device, but unfortunately, this mechanism is not yet well defined or designed. (cc. @bartek)

Don't forget to rename to createTestBackup