Onesignal-ios-sdk: Possible issue - "Provisioning Profile Missing Push" status when background modes are disabled
The device can sometimes be reported as (Provisioning Profile Missing Push Permission)" on the first start of the app when "background modes" are disabled in Xcode. It might be related to when the user accepts the notification permission but the SDK isn't waiting for an attempt to get the APNs pushToken to return. The case where this was found on the device it did not have an identifier set but had notification_types set to 15. The next time the app was opened a pushToken was set correctly.
jkasten2
All 2 comments
I've never been able to reproduce this issue - I think it must be quite rare. Closing - if anyone else ever encounters this problem please feel free to reply
Nightsd01
on 2 Aug 2018
I just had the case where my first app start, permissions prompt accepted, resulted in "Provisioning Profile Missing Push".
I double checked our entitlements and capabilities in our provisioning profile and Xcode says everythings all right. Found this Post, simply restarted the App and now my Test device is properly subscribed.
iPhone SE @ iOS 12.1.2
OneSignal Unity-SDK 2.7.7 for iOS (I'm assuming it uses the OneSignal iOS SDK)
bjustice-sympatient
on 8 Jan 2019
Related issues
reza-khalafi
路
5Comments
Tavernari
路
4Comments
huahengling
路
5Comments
KishanVyas
路
6Comments
konkontos
路
3Comments
Most helpful comment
I just had the case where my first app start, permissions prompt accepted, resulted in "Provisioning Profile Missing Push".
I double checked our entitlements and capabilities in our provisioning profile and Xcode says everythings all right. Found this Post, simply restarted the App and now my Test device is properly subscribed.
iPhone SE @ iOS 12.1.2
OneSignal Unity-SDK 2.7.7 for iOS (I'm assuming it uses the OneSignal iOS SDK)