4

From my understanding, when app is running or in the foreground and a push notification is received, the app should NOT show any alert but the app delegate will call the didReceiveRemoteNotification delegate method and I should handle the push notification in that callback.

The push notification should ONLY display alerts/banners when the app is in the background.

However, our app gets push notification alert with an OK button when the app is running or in the foreground sometime, not all of the time. I'm wondering if it is something new in iOS 7 (I have never heard of this) or is it because I'm using UrbanAirship for push notification for our iOS app using alias of the user. The app will display the push alert when running and run the callback in didReceiveRemoteNotification.

Scratching my head over this. Does anyone know why?

imObjCSwifting
  • 743
  • 1
  • 12
  • 34
  • If you don't have code to display a UIAlertView when a push notification is received, it sounds like it's likely Urban Airship that's doing it. – Mike Aug 27 '14 at 16:16

3 Answers3

8

When the App is in foreground, it should not display anything.

If you see alertView, it means you provided code for it.

Something along the following lines:

-(void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo
{
    UIApplicationState state = [application applicationState];

    if (state == UIApplicationStateActive) {
        //app is in foreground
        //the push is in your control
    } else {
        //app is in background:
        //iOS is responsible for displaying push alerts, banner etc..
    }
}

If you have implemented pushNotificationDelegate

[UAPush shared].pushNotificationDelegate = self;

then override, and leave it blank

- (void)displayNotificationAlert:(NSString *)alertMessage
{
  //do nothing
}
meda
  • 45,103
  • 14
  • 92
  • 122
  • That's exactly my question. I'm getting 2 alert views. One from my code (same as your code) and one from nowhere. I'm thinking if urban airship is responsible for the second alert – imObjCSwifting Aug 27 '14 at 16:24
  • yes UA is the culprit. overriding UA handling of push notification works. Thanks – imObjCSwifting Aug 27 '14 at 16:57
2

You are most likely seeing the additional push notification because of the way Urban Airship is configured in your code. From Urban Airship's docs:

The sample UI includes an implementation of UAPushNotificationDelegate that handles alerts, sounds, and badges. However, if you wish to customize this behavior, you can provide your own implementation:

[UAPush shared].pushNotificationDelegate = customPushDelegate;

There is more information on the proper way to handle push notifications with Urban Airship in their support articles. Since you are using UA, I would recommend that you use their delegates etc. to handle incoming push notifications while in the foreground rather than implementing your own code in the didReceiveRemoteNotification app delegate method.

Hopefully that helps...if not, please post your code so that we can decipher what is going on. This would be very odd behavior indeed!

BFar
  • 2,447
  • 22
  • 23
  • This one should be correct. You can also just remove the UI code, or just comment out the UIAlertView here: https://github.com/urbanairship/ios-library/blob/master/Airship/UI/Default/Push/Classes/Shared/UAPushNotificationHandler.m#L33 – Donato Perconti Aug 28 '14 at 17:41
  • Both links are dead! – Amir Hajiha Feb 09 '23 at 17:17
0

This answer is for swift users looking for the same thing

let state = application.applicationState

        if (state == .active) {
            //app is in foreground
            //the push is in your control
        } else {
            //app is in background:
            //iOS is responsible for displaying push alerts, banner etc..
        }

Please refer to the checked answer if you guys have any more doubts. Apple Documentation on handling Notifications

John Xavier
  • 73
  • 1
  • 12