Offline Push (iOS)

Last updated: 2021-10-15 16:42:58

    [](id: configuring push)

    Configuring Offline Push

    If you want to receive APNs offline message notifications, follow these steps:

    1. Apply for an APNs certificate.
    2. Upload the certificate to the console.
    3. The app requests deviceToken from Apple every time it logs in.
    4. Call setAPNS to report the token to the IM backend.

    When the app configured with APNs switches to the background or is killed by the user, the Tencent Cloud backend pushes offline messages to the device through Apple’s APNs. For more information, see Apple Push Notification Service.


    Users who have logged out normally or have been forced offline will not receive any message notifications.

    Step 1: apply for an APNs certificate

    For more information on how to apply for an APNs certificate, see Applying for an Apple Push Certificate.

    Step 2: upload the certificate to the console

    1. Log in to the IM console.
    2. Click the target app card to go to its basic configuration page.
    3. Click Add Certificate on the right side of iOS Platform Push Settings.
    4. Choose the certificate type, upload an iOS certificate (p.12), set the certificate password, and click OK.

      • We recommend that the name of the certificate to be uploaded should be in all English letters (it must not contain special characters such as brackets).
      • You need to set a password for the uploaded certificate. Without a password, push messages cannot be received.
      • Certificates to be published on App Store need to be set to the Release environment. Otherwise, push cannot be received.
      • The uploaded p12 certificate must be an authentic valid certificate that you have personally applied for.
    5. After the push certificate information is generated, record the certificate ID.

    Step 3: request DeviceToken from the Apple backend

    To request DeviceToken from Apple's backend server, add the following code to your app.

    // Request DeviceToken from the Apple backend
    - (void)registNotification
      if ([[[UIDevice currentDevice] systemVersion] floatValue] >= 8.0)
          [[UIApplication sharedApplication] registerUserNotificationSettings:
                  [UIUserNotificationSettings settingsForTypes:
                  (UIUserNotificationTypeSound | UIUserNotificationTypeAlert | UIUserNotificationTypeBadge)
          [[UIApplication sharedApplication] registerForRemoteNotifications];
          [[UIApplication sharedApplication] registerForRemoteNotificationTypes:
                  (UIUserNotificationTypeBadge | UIUserNotificationTypeSound | UIUserNotificationTypeAlert)];
    //The callback of AppDelegate returns deviceToken, which needs to be reported to the Tencent Cloud backend after login.
    -(void)application:(UIApplication *)app didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken
      // Note the deviceToken returned by Apple.
      _deviceToken = deviceToken;

    Step 4: upload the token to Tencent Cloud after IM SDK login

    After logging in to the IM SDK, call setAPNS to upload the DeviceToken obtained in step 3 to the Tencent Cloud backend:

    V2TIMAPNSConfig *confg = [[V2TIMAPNSConfig alloc] init];
    // Push certificate ID, generated after the push certificate (p.12) is uploaded to the IM console backend
    confg.businessID = businessID;
    // The deviceToken requested by Apple’s backend
    confg.token = deviceToken;
    [[V2TIMManager sharedInstance] setAPNS:confg succ:^{
       NSLog(@"-----> APNS set successfully");;
    } fail:^(int code, NSString *msg) {
       NSLog(@"-----> Failed to set APNS");

    businessID must be consistent with the certificate ID assigned by the console.

    General push rules

    For one-to-one messages, the APNs push rules are as follows. Note that the nickname is the sender's nickname. If the nickname is not set, only the content is displayed.


    For group messages, the APNs push rules are as follows. The priority order for displaying the name is: message sender's group name card > group nickname. If neither is available, no name is displayed.

    Name (Group Name):content

    Push rules for different types of messages

    The APNs push content consists of the content of each Elem in the message body. The display of different Elem in offline messages is shown in the following table.

    Parameter Description
    Text Elem Directly display the content
    Audio Elem Display [audio]
    File Elem Display [file]
    Image Elem Display [image]
    Custom Elem Display the desc field set when message is sent. If desc is not set, it will not be pushed.

    Communication among multiple apps

    If you set SDKAppID to the same value for multiple apps, these apps communicate with each other. Different apps need to use different push certificates, and you need to apply for an APNs certificate for each app and complete [offline push configuration](#configuring push).

    Setting Custom iOS Push Alert Sound

    Set the iOSSound field of offlinePushInfo when calling sendMessage to send messages. iOSSound passes the name (with the extension) of the audio file which must be linked to the Xcode project.

    Setting Custom Display for Offline Push

    Set the title and desc fields of offlinePushInfo when calling sendMessage to send messages. Once set, the title content will be added to the default push content and desc will be displayed as the push content.

    Setting Custom Click-to-Redirect Logic

    Set the ext field of offlinePushInfo when calling sendMessage to send messages. When the user receives offline push and starts the app, the ext field can be obtained from the AppDelegate -> didReceiveRemoteNotification system callback, and the user is redirected to the UI as specified by ext.

    The following example assumes that Denny sends a message to Vinson.

    • Sender: Denny needs to set ext before sending a message.
    // Denny sets `offlinePushInfo` and specifies `ext` before sending a message
    V2TIMMessage *msg = [[V2TIMManager sharedInstance] createTextMessage:@"Text message"];
    V2TIMOfflinePushInfo *info = [[V2TIMOfflinePushInfo alloc] init];
    info.ext = @"jump to denny";
    [[V2TIMManager sharedInstance] sendMessage:msg receiver:@"vinson" groupID:nil priority:V2TIM_PRIORITY_DEFAULT
    onlineUserOnly:NO offlinePushInfo:info progress:^(uint32_t progress) {
    } succ:^{
    } fail:^(int code, NSString *msg) {
    • Recipient: although Vinson's app is not online, it can still receive an APNs offline message notification. When Vinson clicks this notification, the app is started.
    // Vinson receives the following callback when the app is started.
    - (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo 
    fetchCompletionHandler:(void (^)(UIBackgroundFetchResult result))completionHandler {
      // Resolve the extension field `desc`.
      if ([userInfo[@"ext"] isEqualToString:@"jump to denny"]) {
          // Go to the chat window with Denny.


    Why doesn't offline push work for common messages?

    First, verify that the app and the certificate have the same runtime environment. Otherwise, offline pushes will not be received.
    Then, verify that the app and the certificate run in the development environment. If that is the case, requesting deviceToken from Apple might fail. Please switch to the production environment to solve the problem.

    Why doesn't offline push work for custom messages?

    The offline push for custom messages is different from common messages. Since we are not able to resolve the content of custom messages and determine what to push, we simply do not push custom messages by default. If you want to enable offline push for custom messages, set the desc field of offlinePushInfo when calling sendMessage, then the content of desc will be used for display by offline push.