Messages are not arriving

[kittykat]

Steps to reproduce

1. Be actively chatting with someone in a DM
2. Sometimes see typing notifications for a long time, sometimes not see anything to indicate that the other person is sending a message
3. See the timeline not updating
4. Swipe the app up to close it and then open it again (see green loading screen)
5. Open DM and see messages that were sent minutes ago

Outcome

What did you expect?

I can have a live conversation

What happened instead?

I had to keep closing/opening the app to see my messages

The problem was happening on 8th August between 23:25 and 23:45

Your phone model

No response

Operating system version

Android 11

Application version and app store

1.4.31 playstore

Homeserver

matrix.org

Will you send logs?

Yes

Are you willing to provide a PR?

No

[kittykat]

The issue is still persisting for me

[witchent]

I have this issue since a few days, though sadly I don't know when exactly it started.
I don't know if it is related, but the presence updates seem wonky as well, and this started around the same time.
The messages show fine in Element-Web, but Element Android needs to be force closed to see them.
Using self hosted synapse in my case.

[another-time]

I've been having this same issue over the past few days. Both on element android and desktop on fedora.

[dm-msk]

Same issue

[sigma2017]

Same behavior, no updates on the matrix synapse server side, looks like the issue is on the client side.

[kylrth]

Can confirm this is occurring on Android and not on desktop

[nlnw8]

Experiencing same issue on Android

[dreaddr]

Experiencing the same issue, messages are not syncing with the homeservers and need a full app refresh to fetch new messages.

[opusforlife2]

Should F-Droid users avoid updating from 1.4.25 for now, to be on the safe side?

[nolimbsdotdev]

I have the same problem and I think it is also linked to #6823 where you cannot edit your own messages after sending. It's like the client isn't syncing correctly...

[bmarty]

I did not find any suspicious logs in the rageshake :/. Will have a second look later.

[th0mcat]

Seeing this on Element Android (F-Droid, develop and main builds), but not on desktop.

[immanuelfodor]

Very annoying to converse with somebody then accidentally find out later there were other messages that I didn't see 🤦‍♂️😃

[bmarty]

OK, I can repro:

• Kill the app
• Receive a message with a Push. the notification is displayed.
• Start the app

With this scenario, the SyncThread is not started, so the app is not syncing to get new messages. If Push are received for new messages, they are ignored, since the app is in foreground.

Working on a fix right now.

[git-bruh]

The 'mark read' option in any push notification doesn't work either BTW, not sure if that would be covered by the fix for this

[dm-msk]

Still no sync after update.
Ensure SyncThread is started when the app is launched after a Push has been received. (#6884)

[twouters]

Still no sync after update. Ensure SyncThread is started when the app is launched after a Push has been received. (#6884)

I haven't had this issue since updating to 1.4.34, are you sure you're on the correct version? Could also be a different issue or I've been lucky so far.

[dm-msk]

Still no sync after update. Ensure SyncThread is started when the app is launched after a Push has been received. (#6884)

I haven't had this issue since updating to 1.4.34, are you sure you're on the correct version? Could also be a different issue or I've been lucky so far.

Same version. Desktop version shows new messages, Android app still silent at this moment.

[bmarty]

@dm-msk can you send a rageshake please?

[dm-msk]

rageshake

i've sended rageshake with "ticket 6782" theme

[bmarty]

Thanks.
I see lots of logs like this: /SYNC/SyncTask: Incremental sync request parsing, 0 room(s) 0 toDevice(s) in your rageshake, so I think there is an issue with your homeserver. You may want to do a clear cache from the app: Settings/General/Clear cache to try to fix this.

[kylrth]

Yes, this has been fixed now for me since 1.4.34

[z411]

Persists for me; I can see in debugging information that the SyncThread is idle. I have to restart the application. Also many times I don't get timely push notifications or voice calls. I'm using MIUI so I wonder if it's killing the thread, although I have it with all restrictions disabled.

[opusforlife2]

@z411 You're looking for #7876.

[cpot]

Still having this issue (or similar) on latest version for Android 1.5.24, dedicated homeserver, Android 13

Very annoying, please fix it, killing reputation of Element

[EntityinArray]

still occurs on android, AMA for info

[akuckartz]

Why is this not reopened?

[CRK1918]

I can receive message, but not sent, it something to do with this

I can't see it in my end, but in the sender, what is that icon means?

[bestrocker221]

The issue still persist for me as well on android, it happens at random times and the fix is always to force close the app and restart it. No notable logs from server side seem to be relevant.

[CRK1918]

I can receive message, but not sent, it something to do with this

I can't see it in my end, but in the sender, what is that icon means?

Sorry, false alarm for this, this just shows when I turn on Do Not Disturb (or ignore) for someone.