Redundant Push Notifications

[m2x4m4l42n]

With the current release 5.0.1 running on iOS 13.3.1 , I receive 2 Push Notifications saying "New Message!" for every new message and a third with the actual message preview if the Application is open in the background. I read in #1067 that the app utilizes low priority APNs notifications for background fetching is this related to that? i tested this with multiple servers but the result is the same.

[chrisballinger]

You're probably double-registered for push notifications, you'll need to reset your push account:

Account Settings -> Server Information -> Reset Push

[m2x4m4l42n]

Thanks for the quick reply! Unfortunately resetting the push account does not resolve the Issue. It reregisters automatically and i instantly get double notifications again

[chrisballinger]

Do you have more than one account set up on the device? Is your server using ejabberd or prosody?

[m2x4m4l42n]

The server is running ejabberd 18.12.1-2~bpo9+1 and its the only active account. As i mentioned i wiped and reinstalled the app and tried to set up a different account on a different server which ran Prosody 0.10.2 and had the same problem.

[Aubermean]

Same problem over here. If John sends me a message saying 'Hi' I get two notifications:

Chatsecure John: Hi

Chatsecure You have a new message!

I am using OMEMO. The greater issue for me is that I don't want the sender and message body in my notifications for privacy reasons.

I have also reset push notifications, it didn't help.

[ALFriedman]

We don't use the ChatSecure push server (and I'm not sure if the Reset Push notifications affects this), but I know that if we have at any time used both the App Store version and the TestFlight version, we'll get double notifications and thus need to do a reset in our push server. (I can't remember if this is just because of a different push token or a different device ID.)

[woutd]

Same problem here. It seems very random I get notifications of a "new message" but there is none. Enabled OMEMO Group Encryption. Other XMPP clients are using Conversations on Android. Using Prosody 0.11.5, not sending body or sender. In server logs I see:

May 12 21:19:10 c2s801881240	warn	The client says it handled 3 new stanzas, but we only sent 2 :)
May 12 21:35:39 c2s80201d100	warn	The client says it handled 12 new stanzas, but we only sent 11 :)
May 12 22:03:50 c2s80214f140	warn	The client says it handled 5 new stanzas, but we only sent 4 :)
May 12 22:03:55 c2s80214f140	warn	The client says it handled 1 new stanzas, but we only sent 0 :)
May 12 22:12:50 c2s803dbf600	warn	The client says it handled 4 new stanzas, but we only sent 3 :)

Might it be caused by other events... like "online/offline" or "typing"?

[ALFriedman]

@woutd regarding the stanzas in server logs, you may want to look at: https://github.com/ChatSecure/ChatSecure-iOS/issues/979 and https://github.com/robbiehanson/XMPPFramework/issues/1101

[sammy007]

Can confirm redundant notifications. Running 20.04 ejabberd.

[woutd]

I have contacts using Conversations client, and I think it is related with "typing" and/or "message received" notifications in my case.