Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random notifications bug #881

Open
ethylmorphine opened this issue Nov 11, 2017 · 4 comments
Open

Random notifications bug #881

ethylmorphine opened this issue Nov 11, 2017 · 4 comments

Comments

@ethylmorphine
Copy link

@ethylmorphine ethylmorphine commented Nov 11, 2017

Notifications may act weird sometimes, i.e. there is only single message incoming but you get 2 or more push notifications. Another interesting thing happens when you switch from tor to direct connection because this will change OMEMO key. So, if you use the account with tor only, after disabling tor you will still receive notifications but not messages itself (your key is different and you buddy don’t know the new key).
This problem is very frustrating, it seems it is solvable only via implementation of MAM though.

@chrisballinger
Copy link
Member

@chrisballinger chrisballinger commented Nov 11, 2017

  1. Are they the static "New Message!" notifications or do they include the content as well?
  2. As far as sharing OMEMO keys, I think it's better to keep everything isolated between accounts. You're right that it will only be solved properly once MAM is in place, and we show better key-change notifications on the other end.
@ethylmorphine
Copy link
Author

@ethylmorphine ethylmorphine commented Nov 11, 2017

No contents at all. Furthermore, notification may pop up just because buddy get online.

@ghost
Copy link

@ghost ghost commented Nov 19, 2017

I noticed the "random notifications bug" too. Nearly all messages are arriving with 3 or more notifications, especially if ChatSecure was previously stopped. Only one notification contains the message. The others are the static "New Message!". It also displays sometimes the static "New Message!" notification when another ChatSecure user starts typing. Unfortunately, there are also cases where there is no particular reason for the static notification. It is really annoying when using ChatSecure in conjunction with the Apple Watch (I now the Apple Watch is evil, but my mom loves her), as one constantly expects to find a new message at ChatSecure.

@chrisballinger
Copy link
Member

@chrisballinger chrisballinger commented Nov 19, 2017

@orwell1984 When the "New Message!" notifications appear is basically out of our control and is dependent on the XMPP server you're using sending out those notifications at strange times. The best I can suggest is make sure you're using this patch, but I'm guessing you already are. You could put some logs in mod_cloud_notify to log all the stanzas that are triggering push to track down the stanzas that are causing unwanted pushes, and then submit a patch to help filter those out.

If multiple notifications are appearing, this is likely because the device is registered multiple times. This can be solved by going to account settings -> Server Info -> Reset Push.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.