Replies: 3 comments 1 reply
-
That's probably because Monal tries to do periodic syncs in the background every few hours to compensate for lost pushes. Could you test if those spurious sync errors persist with Monal 5.3.4? If it persists: does your server use a csi module (for prosody these are mod_csi_simple or mod_csi_battery_saver) and support XEP-0198 (mod_smacks in prosody)? |
Beta Was this translation helpful? Give feedback.
-
Thanks for the quick response, i took some time testing the new behavior. After updating to version 5.3.4 the Error messages were way fewer. In case it still matters i am using prosody with One complaint i still have is that i periodically get complaints from people using my server and monal that "my server isn't working properly" because of these notifications. I would suggest changing the body of these notifications to something along the lines of "you may have missed messages", similar to how whatsapp used to handle this (maybe they still do, i wouldn't know). A button to disable these notifications is no longer something i would introduce because they are no longer seemingly random. |
Beta Was this translation helpful? Give feedback.
-
You'll probably like these two commits, too: |
Beta Was this translation helpful? Give feedback.
-
First of all, thank you all for developing and maintaining this app :)
I get multiple "could not synchronize" push notifications daily, probably because during school I have very poor Internet, and the app can't connect to my xmpp server during the 30s granted by Apple. Curiously though, almost all of the time i get these push notifications, I didn't actually receive any new messages (as confirmed by my laptop, which has proper internet). I understand that it is important to notify users of potentially missed messages, like mentioned in #864, but for some users muting these notifications entirely, may be a better solution.
In short:
Beta Was this translation helpful? Give feedback.
All reactions