iOS APNS 在后台模式下未收到

发布于 2024-12-15 18:56:06 字数 238 浏览 4 评论 0原文

我试图在后台模式下接收通知。我不希望用户在收到通知中的警报后启动我的应用程序。但iOS似乎没有将通知发送到回调函数didReceiveRemoteNotification：有任何输入吗？

为了在后台模式下接收推送，我需要执行一些特殊的操作吗？

仅供参考：我也尝试使用 voip 后台模式，但仍然没有任何结果！

基本上，我希望我的应用程序能够在不启动应用程序的情况下接收通知，并在应用程序在后台运行时执行某些操作。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

甜心 2024-12-22 18:56:06

但是iOS似乎没有将通知发送到回调函数didReceiveRemoteNotification：

确实如此。如果您的应用程序位于后台，您将不会收到有关传入推送通知的通知，除非用户通过与通知警报交互来实际启动应用程序。

基本上，我希望我的应用程序能够接收通知，而无需用户启动我的应用程序/用户干预并在后台运行时执行某些操作。

那是不可能的。

回复收藏 0 原文

榕城若虚 2024-12-22 18:56:06

可以获取远程通知并被唤醒。但了解当前实现及其如何受应用程序行为影响非常重要。在苹果的领导下，一切都可能发生变化。
在撰写本文时，您需要了解以下内容（大多数人显然都理解前两个）：

首先，也是最重要的一点，您的应用程序必须包含“远程通知”作为必需的后台模式。
您的应用程序必须注册远程通知，如 https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/IPhoneOSClientImp.html
您必须了解其中根据您当前的应用程序状态（前台、后台、挂起等）在您的应用程序（Swift 的 UIApplicationDelegate）中执行回调
- 前台 - 将调用 application:didReceiveRemoteNotification 或更佳地 application:didReceiveRemoteNotification:fetchCompletionHandler
- 后台/挂起 - 仅（可能）调用 application:didReceiveRemoteNotification:fetchCompletionHandler 并且您最好在 30 秒内调用该 fetchCompletionHandler，否则您的应用将终止。如果您没有使用 fetchCompletionHandler 实现该方法，那么您可能只能从系统接收徽章/警报如果您将其放入 APN 消息的内容中。否则，您将什么也看不到。

现在，问题就在这里。当前的 iOS 分析您的应用程序，然后决定是否真正唤醒您的应用程序。如果您花费大量时间测试 APN，它最终会假设您的应用程序是坏公民，并且不会唤醒您的应用程序（除非您至少已接通电源）。它只会等到您的应用程序随后启动（您可以通过 APN 消息中的系统徽章/警报鼓励用户执行此操作），然后将该远程通知放入 UIApplicationLaunchOptionsRemoteNotificationKey 键下的 did/willFinishLaunchingWithOptions launchOptions 中

It is possible to get remote notifications and be woken up. But it is important to understand the current implementation and how it is affected by application behavior. All things are subject to change under Apple.
As of this writing, here is what you need to know (the first 2 most people obviously grok):

First and foremost, your application has to include "Remote notifications" as a Required Background Mode.
Your application has to register for remote notifications as described in https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/IPhoneOSClientImp.html
You MUST be aware of which callback gets executed in your application (UIApplicationDelegate for Swift) based on your current application state (foreground, background, suspended, etc)
- Foreground -- will call application:didReceiveRemoteNotification or more preferably application:didReceiveRemoteNotification:fetchCompletionHandler
- Background/Suspended -- will ONLY (potentially) call application:didReceiveRemoteNotification:fetchCompletionHandler and you better call that fetchCompletionHandler within 30 seconds or your app gets terminated. If you didn't implement the method with the fetchCompletionHandler, then you will probably only be able to receive a badge/alert from the System IF you put those in the content of the APN message. Otherwise, you will see nothing.

Now, here is the catch. The current iOS profiles your application and THEN decides whether or not to actually wake up your app. If you spend a lot of time testing APN, it will eventually assume your app to be a bad citizen and it won't wake up your app (unless you are plugged into power at the very least). It will just wait until your app is subsequently launched (which you can encourage the user to do via the System badge/alert in your APN message), and then put that remote notification into the did/willFinishLaunchingWithOptions launchOptions under a key UIApplicationLaunchOptionsRemoteNotificationKey

回复收藏 0 原文

~没有更多了~