3 ms·
There's really no good way around this for iOS - it's really a limitation of how push notifications work vs. how XMPP is designed. You'll find that things like
by structural 12y ago
There's really no good way around this for iOS - it's really a limitation of how push notifications work vs. how XMPP is designed. You'll find that things like IRC clients have the exact same problems on iOS (similar problem space, similar protocol that expects constant connections).
If you want to do this for real, what you end up doing is implementing your own server backend that receives XMPP messages and then sends out push notifications to a mobile client. Generally a pain in the rear, but do-able. Getting your own iOS developer key & dealing with app store approval for stuff like this is probably the hardest part (for shops that aren't already doing mobile development). There are 3rd-party services that help bridge this gap: examples are https://pushover.net/ https://pushover.net/ or https://boxcar.io/ https://boxcar.io/
If you're okay with a hosted solution and don't really want to deal with development or deploying a XMPP solution yourself, many of our clients have had good success with Slack (https://slack.com/ https://slack.com/)