No notification on receiving messages

[LakshyAAAgrawal]

Just to test it, i sent a message on Riot from a friends phone( which was a riot iOS ) to my phone while my own phone switched off. When I switched my phone on, there was no notification of any message on my phone. When I opened Riot, then it displayed unread message and also an Android notification.

I am using Google play version.

[geromueller]

Happens onmy phone as well. Using:

• googleplay version and currently 0.8.11-dev.
• AOSPExtended on Redmi4X with microG. All other apps work fine, including GCM.

Riot does not even register for Notifications! Uninstalled and cleared data and cache multiple times.

[oblak-be]

Hi

I just created a github account to confirm this behavior, as all users I have introduced riot to, complain about not receiving notifications after a while. I can provide data for all individual devices used, but I know it's a mix of android and iphone users.

I think a solid notification implementation is key for wider user adoption, as user stop using the app because they basically forget about it :-P.

It would be nice to see this fixed soon, really appreciate the work that is put to into this!

[oblak-be]

wow i didn't expect this to get picked up so quickly, cool!

[ParitoshBh]

Sharing a common scenario that's happening with me (and those I am inviting to use RIOT).

I am in the middle of moving away from Whatsapp, Signal, etc. and at the same time asking family members to install and start using RIOT (server end is already up and running). Most of the things work pretty well except for notifications. As mentioned above, majority of users end up not getting any sort of notifications from RIOT on their devices (all are android users) and thereby fallback to using the traditional Whatsapp app for sending message or initiating a call.

Even though there's nothing wrong with RIOT app itself but the fact that its presence is sort of lost (in a sense) and it not being able to deliver notifications reliably garners negative points. Note that there's an option to tinker around with Notification Privacy settings (or something along the lines) but the default setup isn't reliable enough.

Please note that I am not trying to downplay what developers are doing and/or trying to do but this is more of pointing out an adoption issue.

[manuroe]

@ganfra, @bmarty , is #2451 the fix for the issue initially described here ( When I switched my phone on, there was no notification of any message on my phone.)?

[rjurga]

This is probably related. I have two phones (LineageOS 15.1, Android 8.1.0, installed through Google Play) with Riot in low detail notifications mode. Neither phone receives notifications at all, and then if Riot is started manually, the backlog of notifications appear at that moment. This is true for text messages, but also for voice calls, the phone doesn't ring at all unless the app is started manually first.

[dvb15]

I have the same on my wife's phone (Meizu m2, Flyme OS v6.2.0.0G, Android 5.1). Even if I left Riot-im running before the phone locks the screen, no notification is played or shown.

Background sync helps, but the messages takes about a minute or two to come... And the voice call too! Heavy load on the servers?

[bmarty]

@manuroe yes, I think so

[bmarty]

Pb is still there...

[bmarty]

To check in next Sprint

[BloodyIron]

Yeah, some of my friends are reporting mixed notifications too.

So, Sprint 13 is when this is going to get baked in? That's going to be a new release of the app?

[BloodyIron]

Hmm, also may be related to the lazy room sync stuff going on. One of my friends reports he got alerts when the room loaded later or something. It's rather inconsistent and hard to reproduce.

[bmarty]

We figure out that signal is sending bad priority format

Cf. https://github.com/matrix-org/sygnal/blob/master/sygnal/gcmpushkin.py#L92

According to https://firebase.google.com/docs/cloud-messaging/concept-options it should look like: "android":{"priority":"normal"}. It has maybe change...

That's would explain why notification are not displayed when Riot is killed or after Device Boot

[oblak-be]

great job, thanks for figuring out!! Hopefully this fixes it :-)

…

On 08/29/18 15:33, Benoit Marty wrote: We figure out that signal is sending bad |priority| format Cf. https://github.com/matrix-org/sygnal/blob/master/sygnal/gcmpushkin.py#L92 According to https://firebase.google.com/docs/cloud-messaging/concept-options it should look like: "android":{"priority":"normal"}. It has maybe change... That's would explain why notification are not displayed when Riot is killed or after Device Boot — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2266 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AnDfajtKn3PT1nAG4_Xfm5uHheV9chV0ks5uVpg1gaJpZM4UAlJH>.

[bmarty]

Look like is not the root cause of the issue, priority is well set to "1" (= "high") when receiving push.

[olymk2]

Agreed I still get multiple reports of people not getting the notifications on riot, unfortunately it generally just works for me seems there is a bigger issue going on here, its actually stopping us using matrix / riot users are using hangouts because the notifications work there :/

[echto]

No notification LED on Android on 8.1.0. very annoying.

[echto]

Any news?

[BloodyIron]

Has this been addressed?

[echto]

I installed the latest dev version today to see if things improved and they are actually worse. I receive no notifications at all. I only receive new messages when opening the app. I'm sorry to say this but it appears this app is getting worse and worse. The build I installed today was Build #2447 (Oct 18, 2018 2:14:46 PM).

[BillCarsonFr]

Hi All,

I am trying to consolidate info from this discussion.
I need to be able to reproduce this in order to investigate more, so I will need your help.

@rjurga You said you are receiving notification now, Are you still using 'Low detail notification' mode?

@BloodyIron Regarding notification for messages already read on desktop. Can you please open a new issue for this feature request? The idea I guess is to delay mobile notifications a bit, and don't send them if message has been read on desktop.

@Wykks I will investigate on this. Maybe there is an issue while setting up FCM, and the fallback might launch the Fdroid behaviour (this is just speculation, i will check).

@echto Regarding the LED, can you open a new issue on this, 'Add LED light Notification'. If you can add more info on your expectation for lights (for what kind of notifications? colors?) it will be great, thx.
Are you still not receiving any notification? Can you give me more information on your device?

Also, for everyone, can you tell me if you are not receiving notifications at all, or you are receiving only some notifications?

I will also open a new Issue regarding text copy in the notification settings screen. Current text copy is referring to GCM, but GCM is not used anymore (FCM now)

[BloodyIron]

@BillCarsonFr the issue for me seems to have happened only once so far. If it happens more, I'll create a new ticket :)

[BillCarsonFr]

@ BloodyIron thanks.
As for now I have noticed issues with notifications on devices that have agressive battery optimisation (huawei/honor), and it’s affecting other apps on the device, no notifications.
It can be solved by changing the optimisation settings, and tell the device to not shutdown riot (settings is device/brand/model specific)

[Wykks]

No notification for me. (on both onplus 6 and oneplus 5t, but battery optimisation shouldn't be a problem when using FCM right? Other messaging apps doesn't have this issue). Notifications comes when I start the app.

Using riot from play store and encryption enabled if that matters.

Edit: Okay, I reinstalled the app completely and it works fine now, and I don't have the persistent notification anymore.

[BillCarsonFr]

Yes @Wykks , battery optimisation is affecting the app even if using FCM, I can reproduce it and it’s affecting other apps (like tg).
I am happy that it is working for you now, and at the same time sad that I cannot see why it was not working ;)
Can you report a bug by shacking your device so I can investigate your logs? Thx.

[Wykks]

Done, but since I reinstalled the app I don't know if you will see anything usefull. I should have done this before, sorry

[fearedbliss]

My girlfriend and I are still experiencing this issue, we both have Pixel 3 (Android) with latest stable riot. I've turned off battery optimizations for my app and I sometimes receive the messages and their notifications and sometimes I don't. Sometimes the messages take a free hours to arrive (eventual consistency but that's a long delay and unacceptable for daily use as an instant messenger), sometimes I would see all the messages download when I open it, and recently I've started noticing that if I don't open the app for a long time, it seems that it like it's starting up again (I see the riot multi colored logo loading screen).

[agherzan]

I encounter the same issue on two phones. One on oxygen os 9.0.13 (android 9) and one on lineage os 16. Neither show any notifications if the app is closed. Turned off battery optimisation to no result. I'm on riot 0.9.1.

[echto]

I believe the problem may be with synapse and not riot-android. I updated my HS on May 7 and seven days later, on May 14, notifications ceased occurring for all users on my HS. Restarting the HS did not correct the issue. Notifications had been working reliable since they were fixed in riot-android. Restoring to the previous version of synapse corrected the notification issue and notifications have been working reliably again.

…

On May 14, 2019 10:11:16 AM PDT, Andrei Gherzan ***@***.***> wrote: I encounter the same issue on two phones. One on oxygen os 9.0.13 (android 9) and one on lineage os 16. Neither show any notifications if the app is closed. Turned off battery optimisation to no result. I'm on riot 0.9.1. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #2266 (comment)

[BloodyIron]

@echto what version before and after of synapse are we talking about here?

[geromueller]

Hi, check out #3162, with 0.99.4 it seems to work again

[geromueller]

false alarm. Notifications DO NOT appear if app is not running...

[echto]

I downgraded back to version 0.99.1.1. The version I updated to is 0.99.3.2. Notifications stopped occuring after 7 days. Rerverting back to 0.99.1.1 resolved the issue.

…

On May 15, 2019 9:29:11 AM PDT, BloodyIron ***@***.***> wrote: @echto what version before and after of synapse are we talking about here? -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #2266 (comment)

[joram-berger]

I think my problem is the same as this issue (both Riot apps on Android and for the iphone):
The phone makes a sound when new messages arrive, but the Riot icon has no indication of new messages. So if my friends realize that they got some message, they unlock their phone, look at the apps and see no indication what so ever that Riot has new messages. Then they look at Whatsapp and give up searching what it was. That way, new users overlook messages and loose interest in the Riot app.

[UralZima]

Hello. As I understood, new versions from F-DROID (microG) don't have background service code anymore, it don't ask for a permission, so that's why it is not working. Because of this, I am using version 0.8.26, which still have background service code... The downgrade was painful, needed to recreate all keys, verify again with everyone, because on android downgrade is not possible, only uninstall and install again.

Now I have another problem... I can't call anymore to IOS users. It seems they upgraded to latest versions, and connection never establishes.
Do new versions have this background service code back? or riot-foss is totally broken and depend from google??? Can I safely upgrade and have notifications working?

[fearedbliss]

Not sure why this was closed. The riot android app definitely has flaky notifications. It usually works but sometimes people do message me saying that they haven't received notifications (and this is with my running Synapse 1.4.1 and Riot Android 0.9.8 - the other use is also running Riot Android 0.9.8). I do believe there is usually a combination of issues for users whether it is the Android app not having correct permissions or a bug in synapse, but I don't think all of these issues are resolved. I think this ticket should remain open in order to keep track and perform a wider investigation.

[BloodyIron]

Not sure why this was closed. The riot android app definitely has flaky notifications. It usually works but sometimes people do message me saying that they haven't received notifications (and this is with my running Synapse 1.4.1 and Riot Android 0.9.8 - the other use is also running Riot Android 0.9.8). I do believe there is usually a combination of issues for users whether it is the Android app not having correct permissions or a bug in synapse, but I don't think all of these issues are resolved. I think this ticket should remain open in order to keep track and perform a wider investigation.

Have you guys rage-shake reported the bugs? if not, you should, IMO.

[ghost]

This is still an issue. Running Android 10, with 0.9.12 Riot.im app.

Friend sends me a message, and I don't receive any notifications of it. Happens daily, multiple times per day.

[huguesdk]

i can confirm this. i have several friends on different homeservers, all with riot.im from google play, and many of them don’t receive notifications (even though all notification debug tests pass). is it possible that the app gets killed somehow and never restarted? most of these people don’t use riot often. someone even tried to exclude riot from battery optimizations, but it didn’t help.

[UralZima]

That's why I am still at 0.8.26 version and will never upgrade!!! Because they changed the method and android is killing app anyway. I don't understand, why to not recover old method with persistent notification and background sync? battery is ok with 15-30 sec autosync in settings.