用于 iOS 推送通知的 MQTT 服务 [英] MQTT Service for iOS Push Notifications

查看:31
本文介绍了用于 iOS 推送通知的 MQTT 服务的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Android 上 GCM 的低可靠性以至于我已经转移到另一个服务来处理推送消息:Pushy,(https://pushy.me/)

The low reliability of GCM on Android is such that I have moved to another service to handle push messages: Pushy, (https://pushy.me/)

该服务依赖于 MQTT,根据我的经验以及许多其他评论,实时功能集名副其实,很少有消息被丢弃.但是,联系支持人员时,他们指出没有 iOS 集成,仅支持 Android.

The service relies on MQTT, and from my experience as well as many other reviews, the real time feature-set holds up to its name and rarely does a message get dropped. However, contacting support, they noted that there is no iOS integration and only support Android.

我进行了广泛的搜索,但没有找到一个合适的 iOS 替代品,它支持开箱即用的 MQTT.

I have searched widely but have not found a suitable replacement for iOS that supports MQTT out of the box.

是否有这样的服务可以提供更可靠的推送消息?

Is there such a service available to allow for more dependable push messages?

推荐答案

问题是 iOS 对后台服务的限制使得与 MQTT 代理保持连接变得困难.

The problem is iOS's limitations on background services makes staying connected to a MQTT broker difficult.

Apple 有一个允许在后台运行的用例列表,该列表可以在 本文档

Apple have a list of use cases that are allowed to run in the background, the list can be found in this document

如果您的应用不符合此列表,则很可能无法获得 App Store 的批准.

If your app does not conform to this list it is likely to not get approved for the App Store.

这篇关于用于 iOS 推送通知的 MQTT 服务的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆