推送注册
-
iOS 8 以下推送注册
UIRemoteNotificationType types = (UIRemoteNotificationType) (UIRemoteNotificationTypeAlert |UIRemoteNotificationTypeSound | UIRemoteNotificationTypeBadge); [[UIApplication sharedApplication] registerForRemoteNotificationTypes:types]; -
iOS 8 、9 推送注册
UIUserNotificationType types = (UIUserNotificationTypeAlert | UIUserNotificationTypeSound | UIUserNotificationTypeBadge); UIUserNotificationSettings *settings = [UIUserNotificationSettings settingsForTypes:types categories:nil]; [[UIApplication sharedApplication] registerUserNotificationSettings:settings]; [[UIApplication sharedApplication] registerForRemoteNotifications]; -
iOS 10 以及以上推送注册
UNUserNotificationCenter *center = [UNUserNotificationCenter currentNotificationCenter]; center.delegate = self; [center requestAuthorizationWithOptions:(UNAuthorizationOptionBadge | UNAuthorizationOptionSound | UNAuthorizationOptionAlert | UNAuthorizationOptionCarPlay) completionHandler:^(BOOL granted, NSError *_Nullable error) { if (!error) { NSLog(@"request authorization succeeded!"); } }]; [[UIApplication sharedApplication] registerForRemoteNotifications];注意：需要导入
Device Token 获取
// 远程通知注册成功
- (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken
{
NSLog(@"%@", deviceToken);
}
// 远程通知注册失败
- (void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error
{
NSLog(@"did Fail To Register For Remote Notifications With Error: %@", error);
}
device token :
APNs uses device tokens to identify each unique app and device combination. It also uses them to authenticate the routing of remote notifications sent to a device.
device token 是 APNs 用于区分识别每个 iOS 设备和设备上不同 app 的一个标识符，还可以用于 APNs 通过它将推送消息路由到指定设备上。
大意就是：device token 是唯一的，我们可以通过 device token，推送到指定设备指定 App 上。
接收通知
iOS 7 之前台接收远程通知，后台点击通知
- (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo
{
}
iOS 7，8，9 前台接收远程通知，后台点击通知。这个回调比上面的多了一个参数completionHandler，上面的回调也可以接收 iOS 7，8，9 的通知，但是当这两个回调一起写的时候，只执行下面这个。
- (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler
{
completionHandler(UIBackgroundFetchResultNewData);
}
iOS 10 推送回调
// iOS 10: App在前台获取到通知
- (void)userNotificationCenter:(UNUserNotificationCenter *)center willPresentNotification:(UNNotification *)notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions))completionHandler
{
if([notification.request.trigger isKindOfClass:[UNPushNotificationTrigger class]])
{
NSLog(@"iOS10 前台收到远程通知:%@", notification.request.content.userInfo);
}
else
{
// 判断为本地通知
NSLog(@"iOS10 前台收到本地通知:%@", notification.request.content.userInfo);
}
completionHandler(UNNotificationPresentationOptionBadge | UNNotificationPresentationOptionSound | UNNotificationPresentationOptionAlert);
}
// iOS 10: 点击通知进入App时触发
- (void)userNotificationCenter:(UNUserNotificationCenter *)center didReceiveNotificationResponse:(UNNotificationResponse *)response withCompletionHandler:(nonnull void (^)(void))completionHandler
{
if([response.notification.request.trigger isKindOfClass:[UNPushNotificationTrigger class]])
{
NSLog(@"iOS10 点击远程通知:%@", response.notification.request.content.userInfo);
}
else
{
// 判断为本地通知
NSLog(@"iOS10 点击本地通知:%@", response.notification.request.content.userInfo);
}
completionHandler();
}
静默推送
Silent Notification
The aps dictionary can also contain the content-available property. The content-available property with a value of 1 lets the remote notification act as a silent notification. When a silent notification arrives, iOS wakes up your app in the background so that you can get new data from your server or do background information processing. Users aren’t told about the new or changed information that results from a silent notification, but they can find out about it the next time they open your app.
For a silent notification, take care to ensure there is no alert, sound, or badge payload in the aps dictionary. If you don’t follow this guidance, the incorrectly-configured notification might be throttled and not delivered to the app in the background, and instead of being silent is displayed to the user.
静默推送：顾名思义，就是安静的推送，用户安全感知不到。
{
"aps": {
"content-available": 1
}
}
静默推送的 content-available 一定要为 1，不然苹果感知不到这是一条静默的推送，苹果的建议是take care to ensure there is no alert, sound, or badge payload in the aps dictionary.，不要将 alert 、sound、badge 放在 payload 中。
举个例子：
{
"aps": {
"content-available": 1,
"alert": "推送",
"badge": 1,
"sound": "default",
}
}
如果你这样设置静默推送的 payload，也没有错，但是这个就跟普通的通知没有区别了，还是会打扰到用户，就违背了苹果设计静默推送的的初衷。
静默推送可以唤醒应用在后台被系统杀死的情况，但是不能唤醒用户手动杀死的情况。
静默推送是在 iOS 7 之后推出的一种推送方式。它与其他推送的区别在于允许应用收到通知后在后台（background）状态下运行一段代码，可用于从服务器获取内容更新。功能使用场景：（多媒体）聊天，Email更新，基于通知的订阅内容同步等功能，提升了终端用户的体验。
静默通知在前台和后台都是调用 application: didReceiveRemoteNotification: fetchCompletionHandler 回调。