-
Notifications
You must be signed in to change notification settings - Fork 982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The synced data is not displayed correctly for a synced user returning from offline #19454
Comments
VolodLytvynenko
changed the title
The synced data is not correctly dispalaydd for synced user after returning from offline
The synced data is not correctly displayed for synced user after returning from offline
Mar 29, 2024
VolodLytvynenko
changed the title
The synced data is not correctly displayed for synced user after returning from offline
The synced data is not displayed correctly for a synced user returning from offline
Mar 29, 2024
cammellos
added
E: Mobile Release 2.28
and removed
E: Mobile Release 2.28
E: Mobile Release 2.29
labels
Apr 2, 2024
@VolodLytvynenko Can we validate this is still reproducible? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably this issue will be fixed together with #19455
Steps:
Device A
andDevice B
are syncedDevice B
goes offlineDevice A
performs the following actions:User1
User2
User3
, but doesn't approve itActual result
i. The approved contact request from
User1
is not shown in the Activity Center forDevice B
, but in fact both users are mutual contactsii. The declined Contact request from
User2
is not shown in Activity Center forDevice 2
iii. The received a contact request from
User3
is not shown in Activity center and if profile ofUser3
is opened, the 'send request' button is shown instead of 'Contact request is pending'What
Device 1
sees in the Activity centerWhat
Device 2
sees in the Activity centerExpected result:
All data should for synced
Device B
should be shown in the same way as forDevice A
The text was updated successfully, but these errors were encountered: