Pushing messages to iOS devices involves client application (Client App), APNs (Apple Push Notification service), and Tencent Push Notification Service server (Tencent Push Notification Service Provider). They need to collaborate throughout the entire process to successfully push messages to the client. An exception from any of them can lead to a push message delivery failure.
XGPushPrivate.h (header files where the SDK provides APIs)
libXG-SDK-Cloud.a (main SDK file)
XGExtension.h ("arrival and rich media" extension library and API header file)
XGMTACloud.framework ("click report" component)
XGInAppMessage.framework (in-app messages)
Supports iOS 8.0 and later
For iOS 10.0 and later
You need to introduce
We recommend you use Xcode 8.0 and later
If you use Xcode 7 or an earlier version , you need to configure the SDK for iOS on your own to support the compilation of the
The SDK for iOS provided by Tencent Push Notification Service contains APIs for clients to implement message pushing. It is mainly used to:
Get and register device tokens automatically to facilitate integration.
Bind accounts, tags, and devices, so you can push messages to specific user groups and have more push methods.
Report the number of clicks, i.e., how many times a message is clicked by users.
Message delivery channels used by Tencent Push Notification Service:
Tencent Push Notification Service channel: the channel built by Tencent Push Notification Service. It can deliver messages only when the Tencent Push Notification Service is online (maintaining a persistent connection with the Tencent Push Notification Service backend server). It requires the SDK 220.127.116.11 or later.
APNs channel: Apple's official message push service. For more information, please see APNs.
Device registration flow
The device registration flow is as shown below. For specific API methods, see the API documentation.
Device unregistration flow
The device unregistration flow is as shown below. For specific API methods, see the API documentation.
The account flow is as shown below. For specific API methods, see the API documentation.
The tag flow is as shown below. For specific API methods, see the API documentation.
User attribute flow
The user attribute flow is as shown below. For specific API methods, see the API documentation.