element-android icon indicating copy to clipboard operation
element-android copied to clipboard

Messages are not arriving

Open kittykat opened this issue 2 years ago • 5 comments

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 avatar Aug 09 '22 09:08 kittykat

The issue is still persisting for me

kittykat avatar Aug 10 '22 09:08 kittykat

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.

witchent avatar Aug 10 '22 10:08 witchent

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

another-time avatar Aug 10 '22 17:08 another-time

Same issue

dm-msk avatar Aug 11 '22 09:08 dm-msk

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

sigma2017 avatar Aug 11 '22 21:08 sigma2017

Can confirm this is occurring on Android and not on desktop

kylrth avatar Aug 12 '22 21:08 kylrth

Experiencing same issue on Android

nlnw8 avatar Aug 12 '22 21:08 nlnw8

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

dreaddr avatar Aug 13 '22 03:08 dreaddr

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

opusforlife2 avatar Aug 14 '22 20:08 opusforlife2

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...

nolimbsdotdev avatar Aug 15 '22 21:08 nolimbsdotdev

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

bmarty avatar Aug 17 '22 15:08 bmarty

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

th0mcat avatar Aug 17 '22 20:08 th0mcat

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

immanuelfodor avatar Aug 18 '22 11:08 immanuelfodor

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.

bmarty avatar Aug 18 '22 15:08 bmarty

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

git-bruh avatar Aug 18 '22 15:08 git-bruh

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

dm-msk avatar Aug 30 '22 11:08 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.

twouters avatar Aug 30 '22 13:08 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.

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

dm-msk avatar Aug 30 '22 13:08 dm-msk

@dm-msk can you send a rageshake please?

bmarty avatar Aug 30 '22 13:08 bmarty

rageshake

i've sended rageshake with "ticket 6782" theme

dm-msk avatar Aug 30 '22 13:08 dm-msk

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.

bmarty avatar Aug 30 '22 14:08 bmarty

Yes, this has been fixed now for me since 1.4.34

kylrth avatar Aug 30 '22 16:08 kylrth

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.

z411 avatar Feb 10 '23 03:02 z411

@z411 You're looking for #7876.

opusforlife2 avatar Feb 10 '23 16:02 opusforlife2

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

cpot avatar Feb 17 '23 14:02 cpot

still occurs on android, AMA for info

EntityinArray avatar Jul 05 '23 13:07 EntityinArray

Why is this not reopened?

akuckartz avatar Jul 15 '23 14:07 akuckartz

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

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

CRK1918 avatar Jan 05 '24 01:01 CRK1918