Notification Not Working For MUC (#477)

Unknown opened 4 years ago

Describe the bug Message to MUC from other client does not generate notification on iOS.

To Reproduce Steps to reproduce the behavior:

Create / join a MUC with participants from various servers (participant using Siskin IM may or may not be on tigase.im)
Send message from / to MUC for all parties to confirm bidirectional communication works for everyone
Start another app (no need to terminate Sisikin IM)
Lock iOS (iPad or iPhone)
Have 3rd party (i.e. user on Conversations) send message to MUC
No notification generated for Sisik IM.
Start Sisikin IM
Siskin IM comes online, MUC message recieved.

**Expected iOS should notify Sisikin IM user that there is a message for MUC momentarily after message is sent from 3rd party participant.

Screenshots N/A

Details (please complete the following information):

Siskin Version: 6.2
iOS version: 14.4
iPhone model: iPhoneX

Additional context Add any other context about the problem here.

Unknown commented 4 years ago

@ged296123: this is most likely a server related issue. If your server is not tigase, then you run into this issue

Unknown commented 4 years ago

@Ged296123: this is most likely a server related issue. If your server is not tigase, then you run into this issue

Hi mwlczk,

In the above instance iOS participant was tried with tigase.im. However, it didn't make a difference. Tried all combinations with conversations.im, tigase.im, yax.im, jabber.hot-chilli.net on Siskin IM and as 3rd party.

Unknown commented 4 years ago

So the user has an account @tigase.im and is using siskin-im-app and he still does not get a notification in a muc on the tigase.im server, thats odd.

But please check in the muc-settings if the user gets notified "always", "when mentioned" or has set the muc to "muted"

Unknown commented 4 years ago

Room details showed notifications "when mentioned". Changed this to "always." Didn't make a difference.

Unknown commented 4 years ago

@Ged296123 just to confirm, you were joined to MUC room on muc.tigase.im using a SiskinIM client connected to the account on tigase.im and no other device was connected to this account?

Unknown commented 4 years ago

@hantu85 hello. 2 different processes tried. In both of them, Siskin IM client was used with tigase.im account and no other device was connected to this account.

The MUC room was created by 3rd part client (on Conversations) with their own account (i.e. on conversation.im) and an invitation to Siskin IM was sent to join. Joining room and initial messaging was successful (as described in steps 1-2 above)
The MUC room was created by Siskin IM and invitations were sent to users on conversations.im, yax.im and jabber.hot-chilli.net. Creating room and initial messaging was successful (as described in steps 1-2 above).

Unknown commented 4 years ago

@Ged296123 but was MUC room on muc.tigase.im or not?

Unknown commented 4 years ago

@hantu85 the MUC room was on conversations.im

Unknown commented 4 years ago

As it was mentioned in issue #405, there is no standardized specification for a notification from MUC rooms when you are not connected, as according to MUC specifications when you are going offline then you are leaving the MUC room. There is a workaround available in Siskin IM which AFAIK works only with Tigase servers.

The only issue which can be fixed here is to not show (or make it possible to set) the "notification" setting for rooms on servers not supporting this workaround.

Also as stated in issue #405, there is already a MIX specification that should supersede MUC specification and which allows being part of the MUC room even when not connected and this specification is supported by SiskinIM.

Unknown commented 4 years ago

It's a shame Apple puts the apps to sleep, notifications are not a problem on Android. I understand not receiving notifications from Public Groups after having left the room, but for Private Groups it shouldn't be so. Maybe MIX or a re-view on the XEP in the near future can happen. IMO, this is a major dealbreaker for most people when deciding between federated XMPP and proprietary messaging. Thanks for your attention and response @hantu85.

	Unknown opened 4 years ago Describe the bug Message to MUC from other client does not generate notification on iOS. To Reproduce Steps to reproduce the behavior: Create / join a MUC with participants from various servers (participant using Siskin IM may or may not be on tigase.im) Send message from / to MUC for all parties to confirm bidirectional communication works for everyone Start another app (no need to terminate Sisikin IM) Lock iOS (iPad or iPhone) Have 3rd party (i.e. user on Conversations) send message to MUC No notification generated for Sisik IM. Start Sisikin IM Siskin IM comes online, MUC message recieved. Expected iOS should notify Sisikin IM user that there is a message for MUC momentarily after message is sent from 3rd party participant. Screenshots N/A Details (please complete the following information): Siskin Version: 6.2 iOS version: 14.4 iPhone model: iPhoneX Additional context** Add any other context about the problem here.
	Unknown commented 4 years ago @ged296123: this is most likely a server related issue. If your server is not tigase, then you run into this issue
	Unknown commented 4 years ago @Ged296123: this is most likely a server related issue. If your server is not tigase, then you run into this issue Hi mwlczk, In the above instance iOS participant was tried with tigase.im. However, it didn't make a difference. Tried all combinations with conversations.im, tigase.im, yax.im, jabber.hot-chilli.net on Siskin IM and as 3rd party.
	Unknown commented 4 years ago So the user has an account @tigase.im and is using siskin-im-app and he still does not get a notification in a muc on the tigase.im server, thats odd. But please check in the muc-settings if the user gets notified "always", "when mentioned" or has set the muc to "muted"
	Unknown commented 4 years ago Room details showed notifications "when mentioned". Changed this to "always." Didn't make a difference.
	Unknown commented 4 years ago @Ged296123 just to confirm, you were joined to MUC room on muc.tigase.im using a SiskinIM client connected to the account on tigase.im and no other device was connected to this account?
	Unknown commented 4 years ago @hantu85 hello. 2 different processes tried. In both of them, Siskin IM client was used with tigase.im account and no other device was connected to this account. The MUC room was created by 3rd part client (on Conversations) with their own account (i.e. on conversation.im) and an invitation to Siskin IM was sent to join. Joining room and initial messaging was successful (as described in steps 1-2 above) The MUC room was created by Siskin IM and invitations were sent to users on conversations.im, yax.im and jabber.hot-chilli.net. Creating room and initial messaging was successful (as described in steps 1-2 above).
	Unknown commented 4 years ago @Ged296123 but was MUC room on muc.tigase.im or not?
	Unknown commented 4 years ago @hantu85 the MUC room was on conversations.im
	Unknown commented 4 years ago As it was mentioned in issue #405, there is no standardized specification for a notification from MUC rooms when you are not connected, as according to MUC specifications when you are going offline then you are leaving the MUC room. There is a workaround available in Siskin IM which AFAIK works only with Tigase servers. The only issue which can be fixed here is to not show (or make it possible to set) the "notification" setting for rooms on servers not supporting this workaround. Also as stated in issue #405, there is already a MIX specification that should supersede MUC specification and which allows being part of the MUC room even when not connected and this specification is supported by SiskinIM.
	Unknown commented 4 years ago It's a shame Apple puts the apps to sleep, notifications are not a problem on Android. I understand not receiving notifications from Public Groups after having left the room, but for Private Groups it shouldn't be so. Maybe MIX or a re-view on the XEP in the near future can happen. IMO, this is a major dealbreaker for most people when deciding between federated XMPP and proprietary messaging. Thanks for your attention and response @hantu85.