21
votes

I have noticed a different behavior of didReceiveRemoteNotification between APNS production and development environment.

In development mode (build using development provisioning profile) this method is being called when user taps on notification. In both background and active state.

but in production mode (build using adhoc provisioning profile) this method is being called when user taps on notification if app is in background or not active but when the app is in active state this method calls immediatily when receive notification.

Can anyone help me to understand this different behavior?

I want my user to redirect to a different screen when he taps on notification (in active state), but due to this behavior he is automatically redirecting to other screen.

1
@JitendraSolanki my question is different, and same issue with your suggested method, calling immediatily when receive notification.Mayank Jain
@MayankJain please refer to my answer. tell me if I'm wrong somewhere.Pratik Jamariya
With background what do you mean, killed or just in the background?Akshay Sunderwani
@AkshaySunderwani just background also same behavior with killed, but different in case of foregroundMayank Jain

1 Answers

-1
votes

Your question make me confuesed and I did a test,"In development mode (build using development provisioning profile) this method is being called when user taps on notification. In both background and active state."The Documentation of WatchKit says:If a remote notification arrives while your app is active, WatchKit calls this method to deliver the notification payload. Use this method to respond to the notification(whithout your tap).I tested it on my iphone,the result is the same,it's run without my tap.And it's deprecated in iOS 10.enter image description here