keycard account restored by seed phrase gets no contact requests and neither 1-1 messages nor contacts resulting from accepted crs elsewhere

[86doteth]

Bug Report

Problem

this is about the keycard account for 86.eth which lives on always-on ubuntu desktop relay client which i imported on mobile through seed phrase to be able to use my wallet with dapps.

contact requests and dms arrive fine on desktop but not on mobile, also not the contacts that result from accepting requests on desktop. community fetching works fine on mobile so it just seems to be everything 1–1 thats bugged.

sometimes after a day or so a subset of messages i either sent or should receive do arrive. but these are only in a chat with 86doteth-test my other account which was already a contact before i imported. none of the messages or contacts from recently received contact requests ever came through on mobile.

it seems that for the chats with existing contacts once the messages do arrive sending and receiving goes reasonable and close to realtime. it looks like when i do some action on status desktop at some point then mobile becomes ‘out of sync’ again

Expected behavior

receive everything i receive on any other device i have this account on in close to realtime

everything i send should appear for the recipient in close to realtime and not a day later

Actual behavior

i get none of the contact requests or messages and contacts resulting from those requests that i do receive on other devices.

from chats already open before import only a fraction of the messages that i either sent or should receive come through maybe a day later.

Reproduction

1. have a desktop keycard account with some active chats, contacts and communities, one of the the contacts controlled by you for testing
2. import this account by seedphrase into mobile
3. use some other account to send cr to this account. you wont see the cr at all on mobile. when accepting on desktop and sending some chats back and forth, neither the chat, contact or received messages will be seen on mobile
4. use one of the contacts you control to chat with. observe that messages sent from mobile dont arrive within seconds or even minutes but probably a day or so later. same for messages that should be received (on desktop they arrive instantly)

Additional Information

• Status version: 2.31
• Operating System: iOS

[churik]

Reminder to @churik to reply on this one

[churik]

@86doteth thank you for reporting!
Until the sync of keycard account is not possible on mobile I doubt that the issue can be resolved, as technically you need to pair your devices to be able to get all the data on both.
@ilmotta the sync/pairing of keycard account from desktop is in the scope of 2.33?

[churik]

related issue: #21812

[86doteth]

@86doteth thank you for reporting! Until the sync of keycard account is not possible on mobile I doubt that the issue can be resolved, as technically you need to pair your devices to be able to get all the data on both. @ilmotta the sync/pairing of keycard account from desktop is in the scope of 2.33?

@churik might be that fixing sync will autosolve this. but my experience with mobile+desktop v1 and desktop-desktop v2 has been that even when unsynced at least messages still arrived pretty fast on both devices with same profile. so i thought maybe more is going on here

[ilmotta]

@churik @86doteth, we have a considerably long list of features that will require syncing to work reliably. Those that depend on syncing we have decided to descope for 2.33 because we are working on other missing features, which we consider fundamental (e.g. mobile user can't yet join a community with a keycard and is essentially stuck on the mobile app). Another thing to keep in mind is that we accumulated a series of bugs from 2.32 cycle that should be addressed for 2.33 and more keycard bugs will surely be identified until 2.33 is out.

[86doteth]

@churik @86doteth, we have a considerably long list of features that will require syncing to work reliably. Those that depend on syncing we have decided to descope for 2.33 because we are working on other missing features, which we consider fundamental (e.g. mobile user can't yet join a community with a keycard and is essentially stuck on the mobile app). Another thing to keep in mind is that we accumulated a series of bugs from 2.32 cycle that should be addressed for 2.33 and more keycard bugs will surely be identified until 2.33 is out.

getting keycard features working first makes sense

i probably misunderstood how much sync is needed to fix this bug. jonathan once said sync still occurs for unpaired accounts, so i guess sync is some kind of subset of pairing functionality that is always needed when handling multiple instances. based on my mentioned experience with multiple desktop instances i thought two unpaired status instances should always have smooth message fetching independent from each other. but i guess things properly worked for those unpaired desktop instances only bc pairing and with that sync was already fully implemented on desktop. probably makes sense then indeed for mobile to work on both sync+pairing in a dedicated release and fix all these multi-instance bugs