Bug Push Notification - Githubissues

tigase / siskin-im

(M) Public Project of Tigase Messenger for iOS devices based on Tigase Swift XMPP library.

GNU General Public License v3.0

176 stars 37 forks source link

Bug Push Notification #234

Open dikiw311 opened 1 year ago

dikiw311 commented 1 year ago

Describe the bug

Cannot get the push notification if application on Background / Terminate

Expected behavior

Can receive the push notification if the application stay in background / terminate

Details (please complete the following information):

Siskin Version: 7.3.3
iOS version 15.7.8
iPhone model iPhone 7

licaon-kter commented 1 year ago

Server software?

woj-tek commented 1 year ago

@dikiw311 why do you terminate (swipe away) the application? This only causes more problems - longer startup and higher battery drain overal!

hantu85 commented 1 year ago

Swiping application away is detected by the operating system (iOS) and it disables showing notifications from the stopped application. Have you swiped it out or just moved to using other application?

Is your server supporting Push notifications? If not, this will not work.

MedicMomcilo commented 7 months ago

As the OP didn't provide more details, I'll share my data. My friend has an account on my server and is not receiving notifications on his iPhone.

server software: prosody 0.12
the notifications stop even if the application is not swiped (in server side logs we can see that the client stops re-authenticating as soon as the application is not in the foreground)
ios-specific notification modules have been installed and configured specifically: - https://modules.prosody.im/mod_cloud_notify - https://modules.prosody.im/mod_cloud_notify_encrypted - https://modules.prosody.im/mod_cloud_notify_priority_tag - https://modules.prosody.im/mod_cloud_notify_filters

HumanG33k commented 7 months ago

Not sure my friend notification bug (no notification when app background/close). For my case we use ejabberd. iPhone 13 / version : ios 16.1.1 Siskin IM version 7.3.3

licaon-kter commented 7 months ago

@HumanG33k note that ejabberd does not have any special modules (like Tigase or Prosody) that handle groups.

1:1 might work.

HumanG33k commented 6 months ago

even in 1:1 if i understand well it's not working.

MedicMomcilo commented 5 months ago

I found the issue in my specific setup - it is related to outdated luaossl dependency for mod_cloud_notify_encrypted. Specifically, my OS (CentOS Stream 9) does not have the latest package that has the bug fixed (details here[1]). I was seeing the same errors in my Prosody logs, as mentioned in the link.

Workaround for me was to remove the OS package and install it via luarocks install luaossl.

P.S. my comment regarding "no re-authenticating" is actually expected behavior as client works differently from what I was used to.

[1] https://issues.prosody.im/1778#comment-4