When a secondary device is paired via the encryption key, the store isn't automatically selected

[pavlenex]

I played a bit with having two apps, a slave pairing to a master. It seems that slave (secondary) device, once paired doesn't initiate a store selected which leads to blank state and it's difficult for user to know that they don't have store selected, check the video.

Screen.Recording.2024-11-25.at.11.51.42.mov

To replicate:

1. Deploy two apps in dev enviroment
2. Invite the user and connect to app 1
3. In App 1 go to encryption key and copy
4. In app 2 log in to the same server and user as app 1, you will see encription screen key which I believe overwrittes our store selection... and that could be where the problem is
5. Paste encription key
6. See the problem, user is logged in but store not selected

The expected behaviour here should be to pair and have exactly the same store selected automatically. cc @dennisreimann @Kukks

[pavlenex]

According to Kukks:

This is because we dont back up the logged in user data in itself because we want each device to have its own login token. Maybe we can separate the token from the account info