How to get back "Allow Push Notifications" dialog after it was dismissed once?

Question

I am building an app that is heavily relies on APN. Upon the very first start of my app, iOS asks if this app is allowed to use APN (as a result of registerForRemoteNotificationTypes: call). However once dismissed, this dialog is never popping up back. I have to manually go to Settings->Notifications->MyApp to enable/disable things there. So is there a way to avoid this hustle and actually experience what user will experience upon the very first start every time I start my app in debug mode?

Luxuriant

check this link #10191506 – Stoned

You should mark this as answered, since the below method does work (for ios 7.0+). – Monastery

@Luxuriant Eran's answer covers what you asked. Currently the only way to set up a "first time" start is following the below steps. I reproduced them and it worked. Documentation provided by Apple: developer.apple.com/library/ios/technotes/tn2265/_index.html#//… – Monastery

Why is there a bounty here? Isn't the accepted answer enough? – Hypolimnion

Answer 1

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 is restored or the app has been uninstalled for at least a day.

If you want to simulate a first-time run of your app, you can leave the app uninstalled for a day. You can achieve the latter without actually waiting a day by following these steps:

1. Delete your app from the device.

2. Turn the device off completely and turn it back on.

3. Go to Settings > General > Date & Time and set the date ahead a day or more.

4. Turn the device off completely again and turn it back on.

Tade

Wow... Good work Apple :) But thank you! Still better than nothing. I'll give it a shot. – Luxuriant

Side effect: If you do this on an iDevice that have iMessages enabled, moving the clock one day into the future will disable iMessage. So after you have completed the above and reset the clock, remember to enable iMessages again or you will not be able to send or receive – Pasturage

Something I've just found: After you reset the permissions, whenever the prompt shows again, you can turn off/on the phone instead of answering the prompt, and that'll make it prompt again on the next app run. Useful for changing code trying to figure out if/when certain code-paths would cause the prompt. – Ammadas

@ThomasWatson: would turning on airplane mode avoid iMessages to be turned off? – Solarize

@Solarize I think it would have the same effect, as turning iMessage on/off isn't related to your online status - but give it a try... I haven't tested it – Pasturage

Sorry to bother. Can you please take a look here and see if you can answer it? @eran – Chaussure

Answer 2

Since time is money and the other methods take FOREVER—just change your bundle ID over and over while debugging, each time notifications will get queried fresh. Once you are satisfied with code return to original bundle ID.

---

Key Notes from comments below:

• Temporarily turn off all other Capabilities (like IAP) to get around needing to change the provisioning profile.

Gerger

I think this is definitely best, fastest and safest way to get app back to it's initial state. – Compo

But wouldn't you need to change the provisioning profile all the time? – Ullman

@VanDuTran I don't have to, push still worked for me. But even if you had to, it would be so much faster than the current marked solution. Haha! – Gerger

@AlbertRenshaw Oh my, the current solution doesn't even work for me... I set it to two days forward.. – Ullman

Temporarily turn off all other Capabilities (like IAP) to get around needing to change the provisioning profile. – Tempt

Answer 3

On iOS 9.x, you can get the prompt every time you delete the app and reinstall it. This is true for both AppStore production downloads and adhoc mode. The device token will be unique each time.

@chengsam verified this is true in iOS 10 as well. @WongWray verified this is true in iOS 11 as well.

Groats

I'm not seeing the re-prompt bare out in my testing with the ad hoc version of my app distributed through HockeyApp to an iPad Mini (Model A1489 a.k.a. ME276LL/A) on iOS 9.2 (13C75). Can others please weigh in? – Chaqueta

I wasn't seeing the reprompt either :( – Logotype

Thank you! It works well on my iOS 10. I've just run the app from xCode to the iPhone and uninstall the app before next run. Simplest answer here. – Benefice

I have tested on my iOS 10 and it worked well. This should be the correct answer since 2017. – Florencia

Tested for iOS 11.x as well. Works in both production and development – Deyoung

Tested for iOS 15.x too. Works in TestFlight too. – Gavelkind

Answer 4

On IOS10 i can now get the prompt again by just deleting the app.

Valdis

this was back in the day for iOS 8 – Hendrickson

Answer 5

Currently their is no programmatic way to prompt a user to re-accept Push Notificaitons after they have already decided to say no.

You should simply check if you have been granted access, and if not display a view reminding the user to manually give permission in the privacy settings in order to enable push notification features of your application.

Reminiscent

I am not even looking for a way to ask the same thing. All I need is basically bring the system to the initial state. But I got your point. That's really what I am doing later by calling [[UIApplication sharedApplication] enabledRemoteNotificationTypes]. The problem is that I wanted to act differently upon app startup. I can try to use the same approach I suppose. – Luxuriant

I understand what you're trying to do, but unfortunately it's not possible (unless there are some undocumented private APIs to do so). – Reminiscent

Answer 6

If you're just testing that the Push Notifications prompt appears correctly, use the simulator. All you need to do is uninstall the app and reinstall, and the prompt will appear again when you try to register for push notifications.

Logotype

This is definitely better that doing the whole change-date-reset dance. Although it only works on iOS 12 and not 13 :/ – Geometrize

Answer 7

My problem was not registering for UserNotificationSettings. This allowed the APN to work but not the background sound or badge.

      [[UIApplication sharedApplication] registerUserNotificationSettings:[UIUserNotificationSettings settingsForTypes:UIUserNotificationTypeAlert|UIUserNotificationTypeBadge|UIUserNotificationTypeSound categories:nil]];

Disentail

Answer 8

From iOS 13 and above you need to do the whole changing-date-reset thing, as pointed out by Eran.

From iOS 12 and below, uninstalling the app is enough. This also works on simulator, you wont get token though since simulator does not support push notifications.

Geometrize