With the upcoming release of Apple iOS13 system, a push launched ahead DeviceToken adaptation programs to ensure the normal use of the new version is compatible with APP push service. An important change iOS13 that "[deviceToken description]" will be affected by different operating systems and environments and change, if it is not fit to work in a timely manner will result SDK to bind to the wrong DeviceToken, thus affecting the APN push. Will developers make the appropriate updates and optimization based on the current operating environment, to ensure users have a better experience on iOS13 system.
In Xcode11, iOS13 runtime "[ deviceToken Description ]", the case as shown below:
In Xcode11, iOS12 or Xcode10 and the following run-time version of "[ deviceToken
description] ", the case as shown below:
For developers registered DeviceToken different scenarios, and a push put forward the corresponding iOS push SDK adaptation scheme .
To register DeviceToken, a method as shown below: The use of "[GeTui Sdk registerDeviceTokenData]":
Adaptation scheme (recommended): Due to old version SDK to send a push, not fit Xcode11, iOS13 change, you can choose to upgrade to a push SDK version "2.4.1.0" ( docs.getui.com/getui/mobil... ). The code for this program is the most easy to handle.
To register DeviceToken, a method as shown below: The use of "[GeTuiSdk registerDeviceToken]":
Adaptation scheme : by acquiring DeviceToken string process is the NSData converted hexstring , in "[ deviceToken Description After]" issued changes will require the developer to modify the conversion program, with reference to the code as shown below:
DeviceToken adaptation of the iOS SDK integration is crucial push. Please select the appropriate adaptation scheme as soon as possible, in order to better compatibility with Apple's new version. If you have any questions, you can leave a message to us.
3 thumbs up