Search Issue Tracker
Fixed in 2017.3.0f3
Votes
13
Found in
5.4.0b15
Issue ID
790835
Regression
No
[iOS] Push Notifications not Enabled in Xcode Project when NotificationServices are used
To Reproduce:
1. Build the attached project.
2. Open it in Xcode.
3. Observe that the "Remote Notifications" tab is not enabled in Capabilities
(Notifaction.cs does use NotificationServices)
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
- Lists auto expand when scrolling down in the Inspector Window
- Graphics.CopyTexture does not work with Texture2DArray when "Texture Quality" is not "Full Res"
- Unity Download Assistant uses the last install path
- Keycodes Less and Greater are not being registered when using GetKeyDown
- GameObjects in the Scene are not selectable when using "w" after painting with Tile Pallete
lostplesed
Aug 27, 2019 07:17
unity3d 2018.4.1 still has this problem!
playforia-unity3
Sep 23, 2016 07:31
For those who are struggling with this problem, Omar_Unity offers the following workaround.
http://forum.unity3d.com/threads/regarding-unity_uses_remote_notifications-and-missing-callbacks-for-push-registration.429536/#post-2785700
adamt
Sep 08, 2016 16:57
This is absolutely a regression, by the way. In 5.3, iOS push notifications worked. In 5.4, they do not, with no way outside of changing an esoteric C++ macro in an Xcode project file -- with no documentation, release notes, etc. to that effect. This is a total headache for CI-based builds because we need to do a find-and-replace in a post-process script to make the change, which is brittle. The only (seemingly) relevant blurb in the 5.4 release notes is this:
[525606] iOS: Fix to use remote notifications API only if they are used. This fixes a warning when submitting to iTunes Connect.
which is not a publicly viewable bug report, and does not go into detail as to how the Unity can be told that the API is "used" (presumably, that would be by calling UnityEngine.iOS.NotificationServices.RegisterForNotifications and passing "true" as the second argument, but that does not work).