Receiving message notifications painfully

[712ZHEN]

Code of conduct

• I have read and agree to adhere to the Code of Conduct

Self-training on how to write a bug report

• I have learned how to write a bug report

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When another user sent me a message, my mobile phone didn't receive the message until 26 minutes later (I specially made an observation record).

Expected Behavior

When another user sends me a message, my mobile phone can receive the message notification within a few seconds (just like the other party's iPhone).

Steps To Reproduce

No response

Android Version

android15(Color15)

Session Version

1.30.3(4365-433836)

Anything else?

At this time, my mobile phone is in a state of off screen; in addition, I have done a full set of background operations related to the application - allowing background operation, not optimizing the battery of the application, joining the background cleaning whitelist, unlimited traffic use, background locking, turning off battery hibernation optimization, etc.

OPPO-OP591D-API35-v1.30.3-1769150486448.zip

[ThomasSession]

Thanks for the report.
Are you using slow mode or fast mode?
Slow mode does not have direct push notifications, so we poll at regular interval and then create a notification when there are new messages.
The polling is limited by the system itself and will happen at most about every 30min, hence 'Slow' mode. The limitation doesn't come from us but from the system which doesn't allow background work to happen too often, and some system will even reduce the amount of work that can be done in the bg.
We might implement a foreground notification so that we can perform more polling in slow mode.

If you are using fast mode and still not getting quick notifications then there may be another issue, but fast mode should work very quickly.

[0xDDDDDD]

I just had this exact issue but I received the message an entire day later (about 22 hours). I've never had this before and was surprised to find someone else had the same issue. Including logs.

To help you ID the message since i have multiple chats:
Yesterday (26th) at 16:42 i recieved message, I replied at 16:46, then i got no response. Opened the chat this morning and there was nothing.
About 10 minutes ago i got a message from that person but the timestamp is 16:47 yesterday so they actually replied right after I did, but I didn't get it until today.

Additional: I received a message from them 2 minutes or so after yesterdays message finally came through so im not sure if todays message, prompted yesterdays message to come through but the messages coming so close together makes me think that may have something to do with it.

Xiaomi-surya-API31-v1.30.3-1769522751251.zip

[ThomasSession]

Thanks for sharing the logs, we'll have a look and see if we can find any clues as to why this happened.

[712ZHEN]

Thanks for the report. Are you using slow mode or fast mode? Slow mode does not have direct push notifications, so we poll at regular interval and then create a notification when there are new messages. The polling is limited by the system itself and will happen at most about every 30min, hence 'Slow' mode. The limitation doesn't come from us but from the system which doesn't allow background work to happen too often, and some system will even reduce the amount of work that can be done in the bg. We might implement a foreground notification so that we can perform more polling in slow mode.

If you are using fast mode and still not getting quick notifications then there may be another issue, but fast mode should work very quickly.

actually, I am using fast mode.

[ThomasSession]

actually, I am using fast mode.

I can see a lot of errors in the logs failing to reach the seed nodes. You likely are having issues creating a viable path.
Can you check if the dot attached to your own avatar on the home screen is green?
Are you in a location where censorship could be blocking access to Session?
We are reworking our networking layer so hopefully our next update might be able to help with some of those issues.