If you see the "Your provisioning profile does not have APS entry." error message, make sure your provisioning profile is push compatible and has the
aps-environmentstring in it with the
developmentvalue. The easiest way to check is to open the mobile provisioning profile in any text editor and look for the
aps-environmentstring. It should be there.
If it is, and you keep receiving the error, it means that XCode still picks a "non push-compatible" profile. Please make sure you sign with the right one - sometimes if you have two profiles for the same App ID XCode messes things up and signs with the old one.
The recommended steps are:
iOS device push tokens are strings with 64 hexadecimal symbols. Push token example:
03df25c845d460bcdad7802d2vf6fc1dfde97283bf75cc993eb6dca835ea2e2fMake sure that iOS push tokens you use when targeting specific devices in your API requests are in lower case.
Pushwoosh uses IDFV as the device HWID. Note that it may change in case user re-installs all apps from a specific vendor.
By default our latest iOS SDK displays the notification banner when the app is running in the foreground. You can control this behavior by changing the following flags in the Info.plist:
Pushwoosh_ALERT_TYPE– string type, values are:
BANNER– default value, displays banner in-app alert
ALERT– alert notification
NONE– do not show notifications when the app is in the foreground
To get your iOS device push token,
- 1.Open Xcode => Devices & Simulators;
- 2.Connect the test device to your computer;
- 3.Select your connected device in the list of devices on the left;
- 4.Click the Open Console button.
Launch the application for which you need the device push token, and locate your 64 hexadecimal characters device push token in the “Registered for push notifications” line:
It is an expected behavior - badges are handled by iOS itself and its values are stored in application preferences, which are not instantly removed when you uninstall your app. A badge value remains there for some time in case of immediate re-installation, resulting in the same badges shown after an app is re-installed.
Your feedback helps us create a better experience, so we would love to hear from you if you have any issues during the SDK integration process. If you face any difficulties, please do not hesitate to share your thoughts with us via this form.