Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0b4
Issue ID
1037675
Regression
Yes
[iOS] Using Local Notification services creates Push notification Entitlement Key and enables Push notification capability
Steps to reproduce:
1. Open attached project
2. Build 'SampleScene' to iOS
3. Open generated Xcode project
Actual behaviour: 'Push Notifications' capability has been enabled even though push notifications aren't used
Expected behaviour: 'Push Notifications' cabality should remain disbaled and entitlement key for it should not be created
Note:
This happens even if the script referencing NotificationServices isn't used in the built scene.
Reproduced with: 2018.2.0a3, 2018.2.0b4
Not reproduced with: 2018.1.1f1
-
DrizzleGames
Jan 23, 2019 23:06
Did anyone figure out how to deal with this?
-
DrizzleGames
Jan 23, 2019 23:04
Did anyone figure out how to deal with this?
-
Devil_Inside
Jan 08, 2019 15:57
So how am I supposed to fix this if I don't use or need push notifications?
-
Litovets
Aug 10, 2018 14:04
I found this problem in 2018.2.2f1. If I'm not mistaken this problem is appearing because of automatic generating '.entitlements' file and adding it to xCode build. I don't have entitlements file in my project but it is always there.
In the same time this file is not present in xCode build on new clean project.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2019.1.X):
There is no nice way to solve this, because with the current API we can't know if the user will use remote notifications in build time. And the whole API is going to be deprecated anyway.