If you are sending multiple notifications to the same device within a short period of time, the push service will send only the last one. https://developer.apple.com/library/content/technotes/tn2265/_index.html#//apple_ref/doc/uid/DTS40010376-CH1-TNTAG23 Look “Some Notifications Received, but Not All” in that documentation.
You can implement application:didReceiveRemoteNotification: Here is a possible sample code: – (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo { NSString *message = nil; id alert = [userInfo objectForKey:@”alert”]; if ([alert isKindOfClass:[NSString class]]) { message = alert; } else if ([alert isKindOfClass:[NSDictionary class]]) { message = [alert objectForKey:@”body”]; } if (alert) { UIAlertView *alertView = [[UIAlertView alloc] initWithTitle:@”Title” message:@”AThe … Read more
I was experiencing the same issue, but after countless hours trying to debug, I realized that I was calling registerUserNotificationSettings(settings) twice in didFinishLaunchingWithOptions:. Verify that you’re not doing the same
Here’s how Apple say you can do it: Resetting the Push Notifications Permissions Alert on iOS The first time a push-enabled app registers for push notifications, iOS asks the user if they wish to receive notifications for that app. Once the user has responded to this alert it is not presented again unless the device … Read more
For iOS 10 local notifications your out of luck. For iOS 10 remote notifications —regardless of user interaction you can receive callbacks using application(_:didReceiveRemoteNotification:fetchCompletionHandler:). (It’s kind of confusing that they deprecated most notification related methods but not this one) Callback for when app is in foreground and you’re about to show the notification: func userNotificationCenter(_ … Read more
When you send a push notification, there are several problems: If there is a problem, Apple will disconnect you but you don’t know about it. When you use basic notifications there is no way to know if they were all sent or not. SOLUTION: This is the whole point of using an enhanced notification and … Read more
application:didReceiveRemoteNotification:fetchCompletionHandler: gets called even if the app is suspended, not running at all, backgrounded, or active. Also worth noting that the method is iOS 7 only. Here is the apple documentation. HOWEVER if the app was forcibly closed (i.e. by killing with the app switcher), the app will not be launched. (see SO answer) EDIT: … Read more
I am a new iOS developer and I had the same issue before. I finally found that the problem was due to the p12 certificate. We should not use the private key p12 file, instead we should generate a p12 from your private key and the cert download from Apple. Please execute the following OpenSSL … Read more
I figured out the problem. I revoked and regenerated the certificate again, and this time I only exported the private key (without the certificate). In Keychain access, I exported as .p12 and used the new file and it worked. For some reason, PushSharp wasn’t play well with .p12 when both certificate and private key are … Read more
Ok I figured it out. The method is actually called twice (once when it receives the push, and once when the user interacts with the icon or the notification). – (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler { if(application.applicationState == UIApplicationStateInactive) { NSLog(@”Inactive”); //Show the view with the content of the push completionHandler(UIBackgroundFetchResultNewData); } else if … Read more