ios14 "Notifications are not allowed" ERR

Hello. After the ios14 update, there was a problem that the application I distributed did not request notification permission.
In ios 13.7 version, notification permission is normally requested, but the device that has updated ios 14 does not request notification permission.

When requestAuthorization outputs the error details to completionHandler, the following error is displayed.

===========================================
Error Domain=UNErrorDomain Code=1 "Notifications are not allowed for this application" UserInfo={NSLocalizedDescription=Notifications are not allowed for this application}
===========================================

If you know how to fix it, please let me know.

Have a nice day.
Up vote post of NIKM Down vote post of NIKM
10k views
Posted by
NIKM
Reply
Add a Comment

Replies

I resolve this problem
Posted by
NIKM
Post not yet marked as solved Up vote reply of NIKM Down vote reply of NIKM
Add a Comment

I have the same problem. How did you solve it?
Posted by
wingplus
Up vote reply of wingplus Down vote reply of wingplus
Add a Comment
Do you have any solution? Can you share it?
Posted by
ngdangduy13
Up vote reply of ngdangduy13 Down vote reply of ngdangduy13
Add a Comment
Can you share the solution please? Thanks.
Posted by
mferia
Up vote reply of mferia Down vote reply of mferia
Add a Comment
In my case, Build Settings - Packaging - Product Name was not English. Changed to English and worked.
It was okay to set the name in other languages in iOS 13 though.
Posted by
chungchung1315
Post not yet marked as solved Up vote reply of chungchung1315 Down vote reply of chungchung1315

  • Packaging- Product Name is already set in English, but the permission request still does not show, have to solve any other else, please?

    —
    AyechanMaung
Add a Comment

In my case, Build Settings - Packaging - Product Name was not English. Changed to English and worked.
It was okay to set the name in other languages in iOS 13 though.

I solved this problem with this solution!
Thanks!
Posted by
dirablue
Post not yet marked as solved Up vote reply of dirablue Down vote reply of dirablue
Add a Comment
Apple sometimes is really strange... I tried to find a solution 2 or 3 days, and missed out this thread. Product name is the answer. Use english in product name, problem will solved. Thanks to chungchung1315.
Posted by
onr99
Up vote reply of onr99 Down vote reply of onr99
Add a Comment
@NIKM How did you solve it? I have the same problem
Posted by
jdiestram
Up vote reply of jdiestram Down vote reply of jdiestram
Add a Comment
Forgive me for being late.
IOS14 solved the problem by changing 'Build Settings-Packaging-Product Name' to English.

If you want to keep the existing name as it is, add the existing name to the Bundle display name in 'info.plist' and it will work as before.

I refer to the site below.

https://github.com/invertase/react-native-firebase/issues/4093
Posted by
NIKM
Post not yet marked as solved Up vote reply of NIKM Down vote reply of NIKM

  • I am running into the same problem as described in this thread. I have tried using the "English" as the "Product Name". This did not work. Does anyone know if Apple actually has a smart and proper way to get this to work ?

    —
    Art

  • This solved it for me. I'm surprised this did not show up on StackOverflow.

    Btw, to keep your non-English app name the same on the Home Screen, go to the Info tab on the project settings, click the small + button on the Custom iOS Target Properties key-value list and paste CFBundleDisplayName. Tap Return and the key name will be replaced by the nicer one from Apple. Then just paste your localized app name on the value part of this key.

    —
    commander.swift
Add a Comment

Big Thanks. Package name was not in English lol

Posted by
AIYUBBB
Up vote reply of AIYUBBB Down vote reply of AIYUBBB
Add a Comment

In my case I simply just had previously denied notifications. Just check the notification settings first.

UNUserNotificationCenter.current().getNotificationSettings(completionHandler:)

Posted by
Heestand
Up vote reply of Heestand Down vote reply of Heestand

  • The result tips: <UNNotificationSettings: 0x600000d2b020; authorizationStatus: NotDetermined, notificationCenterSetting: NotSupported, soundSetting: NotSupported, badgeSetting: NotSupported, lockScreenSetting: NotSupported, carPlaySetting: NotSupported, announcementSetting: NotSupported, criticalAlertSetting: NotSupported, alertSetting: NotSupported, alertStyle: None, groupingSetting: Default providesAppNotificationSettings: No>

    —
    ruige
Add a Comment