Problem on server side.

%andrzej.wojcik fixed it, but he have to upgrade server.

Andrzej, please assign to me when push component is functional so I can test. If you are not upgrading server, assign to Eric.

Daniel, I've updated a push component on tigase.org and did some testing with %bmalkow. From what we found out, push notifications are working fine if the application is not killed on the device. We have found a few reports on the internet like the one at https://stackoverflow.com/questions/43293467/firebase-messaging-service-does-not-receive-messages-when-the-screen-is-off

When you wrote:

messages are not being delivered to the device when signed off or inactive.

what do you mean? as "signed off" or "inactive"?

You will get messages thru push if:

• your mobile client is registered for push notifications and is disconnected

• there is no other resource connected to this account

• application is not manually killed on the device (and OS did not kill it for some unknown reason)

It is also possible that you will not get a notification if your account is disabled on your device. As if I remember correctly Tigase Android Messenger uses push only as a trigger to reconnect and receive messages from offline message storage, but it would be good if Bartosz would confirm this.

I confirm it.

Remember that if you set application to "offline" status, then it will not reconnect.

Push functionality now works as described. Closing issue.