API Documentation

Last updated: 2021-08-16 11:20:03

    Description

    The account feature and tag deletion feature in this document are available for SDK v1.2.3.0 and later. For versions earlier than v1.2.3.0, see Accounts and Tags.

    The package name path prefix of all APIs is com.tencent.android.tpush. The following table lists important classes that provide APIs for external use.

    Class Description
    XGPushManager Push service
    XGPushConfig Push service configuration item API
    XGPushBaseReceiver Receiver to receive messages and result feedback, which needs to be statically registered by yourself in AndroidManifest.xml

    Launch and Registration

    • The application can only use the SDK push service after successfully registering for and launching the TPNS. Please ensure that AccessId and AccessKey have already been configured.
    • The new version of SDK has integrated TPNS launch and application registration into the registration API, which means you can simply call the registration API to complete the launch and registration by default.
    • After a successful registration, the device token will be returned. The token uniquely identifies the device and is also the unique ID for TPNS to stay connected with the backend. For more information on how to get tokens, please see Getting a device token.

    The registration API usually provides a compact version and a version with callback. Please choose an appropriate version according to your business needs.

    Registering a device

    The following are device registration API methods. For more information on the timing and principle of calls, see Device registration flow.

    API description

    Standard registration only registers the current device, and the backend can send different push messages based on device tokens. There are two versions of the API method:

    public static void registerPush(Context context)
    

    Parameter description

    context: context object of the current application, which cannot be null

    Sample code

    XGPushManager.registerPush(getApplicationContext());
    

    API description

    To allow you to know if the registration is successful, a version with callback is provided.

    public static void registerPush(Context context,final XGIOperateCallback callback)
    

    Parameter description

    • context: context object of the current application, which cannot be null
    • callback: callback functions, including success and failure callbacks and cannot be null

    Sample code

    XGPushManager.registerPush(this, new XGIOperateCallback() {
    @Override
    public void onSuccess(Object data, int flag) {
    Log.d("TPush", "Registration succeeded. Device token: " + data);
    }
    @Override
    public void onFail(Object data, int errCode, String msg) {
    Log.d("TPush", "Registration failed. Error code: " + errCode + ", error message: " + msg);
    }
    })
    

    Getting the registration result

    There are two ways to check if the registration is successful.

    Using the Callback version of the registration API
    The XGIOperateCallback class provides an API to process registration success or failure. Please see the sample in the registration API.

    Sample code

    /**
    * Operation callback API
    */
    public interface XGIOperateCallback {
    /**
    * Callback when the operation is successful
    * @param data //Business data of a successful operation, such as the token information when registration is successful
    * @param flag //Flag tag
    */
    public void onSuccess(Object data, int flag);
    /**
    * Callback when the operation fails
    * @param data //Business data of a failed operation
    * @param errCode //Error code
    * @param msg //Error message
    */
    public void onFail(Object data, int errCode, String msg);
    }
    

    Reloading XGPushBaseReceiver
    The registration result can be obtained by reloading the onRegisterResult method of XGPushBaseReceiver.

    Note:

    The reloaded XGPushBaseReceiver needs to be configured in AndroidManifest.xml. For more information, please see Message configuration below.

    Sample code

    /**
    *
    * @param context //Current context
    * @param errorCode //0 indicates success, while other values are error codes
    * @param message //Returned registration result
    */
    @Override
    public void onRegisterResult(Context context, int errorCode, XGPushRegisterResult message) {
        if (context == null || message == null) {
            return;
        }
        String text = "";
        if (errorCode == XGPushBaseReceiver.SUCCESS) {       // Registration succeeded
            // Get the token here
            String token = message.getToken();
            text = "Registration succeeded. Token:" + token;
        } else {
            text = message + "Registration failed. Error code:" + errorCode;
        }
        Log.d(LogTag, text);
    }
    

    Class method list

    Method Returned Value Default Value Description
    getToken() String None Device token, i.e., unique device ID
    getAccessId() long 0 Gets AccessId for registration
    getAccount String None Gets the account bound for registration
    getTicket() String None Login state ticket
    getTicketType() short 0 Ticket type

    Unregistration

    The following are unregistration API methods. For more information on the timing and principle of calls, please see Device unregistration flow.

    Note:

    After calling the unregistration API, you need to call the registration API again before you can receive pushed messages.

    API description

    When a user has logged out or the application is closed and it is no longer necessary to receive push messages, the device can be unregistered from the application. (Once the device is unregistered, push messages will no longer be received unless the device is successfully registered again).

    public static void unregisterPush(Context context)
    

    Parameter description

    context: context object of the application

    Sample code

    XGPushManager.unregisterPush(getApplicationContext(), new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int i) {
          Log.d("TPush", "Unregistration succeeded");
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          Log.d("TPush", "Unregistration failed. Error code: " + errCode + ", error message: " + msg);
      }
    });
    

    Getting the unregistration result

    The unregistration result can be obtained by reloading the onUnregisterResult method of XGPushBaseReceiver.

    Note:

    • Frequent unregistration is not recommended because it may cause delay in backend sync.
    • Switching accounts does not require unregistration. With multiple registrations, the last registration will automatically take effect.

    Sample code

    /**
    * Unregistration result
    * @param context //Current context
    * @param errorCode //0 indicates success, while other values are error codes
    */
    @Override
    public void onUnregisterResult(Context context, int errorCode) {
    if (context == null) {
             return;
    }
    String text = "";
    if (errorCode == XGPushBaseReceiver.SUCCESS) {
     text = "Unregistration succeeded";
    } else {
     text = "Unregistration failed" + errorCode;
    }
    Log.d(LogTag, text);
    }
    

    Push Notification (Displayed on the Notification Bar)

    Push notifications are content displayed on the notification bar of devices. All operations are performed by the TPNS SDK. Applications can listen for clicks on notifications. In other words, push notifications delivered on the frontend do not need to be processed by applications and will be displayed on the notification bar by default.

    Note:

    • After the TPNS service is successfully registered, notifications can be delivered without any configuration.
    • In general, combined with custom notification styles, standard notifications can meet most business needs. If you need more flexible pushes, consider using messages.

    Getting notifications

    API description

    The TPNS SDK provides a callback API for developers to get the content of arrived notifications. Notifications can be obtained by reloading the onNotificationShowedResult(Context, XGPushShowedResult) method of XGPushBaseReceiver. Here, the XGPushShowedResult object provides an API for reading notification content.

    Note:

    Due to the callback capability limitations of vendor channel SDKs, the notification arrival callback API onNotificationShowedResult currently does not support listening for the arrival of notifications delivered through vendor channels. It supports listening for the arrival of notifications delivered through the TPNS channel only.

    public abstract void onNotificationShowedResult(Context context,XGPushShowedResult notifiShowedRlt); 
    

    Parameter description

    • context: context of current application
    • notifiShowedRlt: arrived notification object

    Getting notification click results

    Notification callback listening and custom parameter interpretation

    The TPNS SDK collects statistics on notification/message arrivals and notification clicks and clearances by default. The SDK provides a callback API for developers to listen for notification click events. Notification click events can be obtained by reloading the onNotificationClickedResult(Context, XGPushClickedResult) method of XGPushBaseReceiver.

    Note:

    • Starting from v1.2.0.1, the TPNS SDK supports listening for the click events of notifications delivered through the TPNS channel and various vendor channels.
    • If you want to deliver and get custom push parameters, the Intent mode is recommended. For more information, see Notification-Click Redirection.

    API description

    public abstract void onNotificationClickedResult(Context context, XGPushClickedResult notifiClickedRlt); 
    

    Sample code

    // If `actionType` of the notification click callback is `0`, the message was clicked; if it is `2`, the message was cleared
    @Override
    public void onNotificationClickedResult(Context context, XGPushClickedResult message) {
      if (context == null || message == null) {
          return;
      }
      String text = "";
      if (message.getActionType() == NotificationAction.clicked.getType()) {
          // The notification is clicked on the notification bar
          // The application handles actions related to the click
          text = "notification opened:" + message;
      } else if (message.getActionType() == NotificationAction.delete.getType()) {
          // Notification is cleared
          // The application handles related actions after the notification is cleared
          text = "notification cleared:" + message;
      }
    
      // Handling process of the application
    
      Log.d(LogTag, "broadcast that the notification is received:" + text);
    }
    

    Parameter description

    • context: context of current application
    • XGPushClickedResult: opened object of the notification

    Methods of XGPushClickedResult class are as follows:

    Method Returned Value Default Value Description
    getMsgId() long 0 Message ID
    getTitle() String None Notification title
    getContent() String None Notification body content
    getActionType() String None 0: the notification is clicked; 2: the notification is cleared
    getPushChannel() String 100 ID of the channel through which the clicked notification is delivered
  • 100: TPNS channel
  • 101: FCM channel
  • 102: Huawei channel
  • 103: Mi channel
  • 104: vivo channel
  • 105: OPPO channel
  • 106: Meizu channel
  • Clearing all notifications

    API description

    This API is used to clear all notifications of the current application on the notification bar.

    public static void cancelAllNotifaction(Context context) 
    

    Parameter description

    • context: Context object

    Sample code

    XGPushManager.cancelAllNotifaction(context);
    

    Creating a notification channel

    API description

    This API is used to create a notification channel.

    public static void createNotificationChannel(Context context, String channelId, String channelName, boolean enableVibration, boolean enableLights, boolean enableSound, Uri soundUri)
    
    Note:

    This API is applicable to v1.1.5.4 and above.

    Parameter description

    • context: context of current application
    • channelId: notification channel ID
    • channelName: notification channel name
    • enableVibration: whether to enable vibration
    • enableLights: whether to enable LED indicator
    • enableSound: whether to enable sound
    • soundUri: ringtone resource URI, which is valid if enableSound is true. To use the system-default ringtone, set this parameter to null.

    Sample code

    XGPushManager.createNotificationChannel(this.getApplicationContext(),"default_message", "Default notification",true, true, true, null);
    

    Push Message (Not Displayed on the Notification Bar)

    Push messages are content delivered to an application by TPNS. The application needs to inherit the XGPushBaseReceiver API to implement and handle all the operations on its own. In other words, delivered messages are not displayed on the notification bar by default, and TPNS is responsible only for delivering messages from the TPNS server to the application, but not processing the messages. The messages need to be processed by the application.

    • Message refers to the text message delivered by you through frontend or backend scripts. TPNS is only responsible for delivering the message to the application, while the application is fully responsible for handling the message body on its own.
    • Because the message is flexible and highly customizable, it is suitable for applications to handle custom business needs on their own, such as delivering application configuration information and customizing message retention and display.

    Message configuration

    Inherit XGPushBaseReceiver and configure the following in the configuration file:

    Sample code

    <receiver android:name="com.tencent.android.xg.cloud.demo.MessageReceiver">
    <intent-filter>
    <!-- Receive in-app messages -->
    <action android:name="com.tencent.android.xg.vip.action.PUSH_MESSAGE" />
    <!-- Listen for results of registration, unregistration, tag setting/deletion, and notification clicks -->
    <action android:name="com.tencent.android.xg.vip.action.FEEDBACK" />
    </intent-filter>
    </receiver>
    

    Getting in-app messages

    A message delivered by you in the console can be received by the application if it inherits XGPushBaseReceiver and reloads the onTextMessage method. After successfully receiving the message, the application can handle it based on specific business scenarios.

    Note:

    Please make sure that the receiver has been registered in AndroidManifest.xml, i.e., YOUR_PACKAGE.XGPushBaseReceiver is set.

    public void onTextMessage(Context context,XGPushTextMessage message)
    

    Parameter description

    • context: current context of the application
    • message: received message structure

    Class method list

    Method Returned Value Default Value Description
    getContent() String None Message body content, and generally it is sufficient to deliver only this field
    getCustomContent() String None Customer key-value of message
    getTitle() String None Message title (the description of the in-app message delivered from the console is not a title)

    Local Notification

    Adding local notifications

    Local notifications are customized by users and saved locally. When an application is open, the TPNS service will determine whether there is a notification once every five minutes based on the network heartbeat. Local notifications will pop up only if the service is enabled, and there may be a delay of about five minutes. A notification will pop up when the time set is earlier than the current device time.

    Sample code

    // Create a local notification
    XGLocalMessage local_msg = new XGLocalMessage();
    // Set the local message type; 1: notification, 2: message
    local_msg.setType(1);
    // Set the message title
    local_msg.setTitle("qq");
    // Set the message content
    local_msg.setContent("ww");
    // Set the message date in the format of 20140502
    local_msg.setDate("20140930");
    // Set the hour when the message is triggered (in 24-hour clock system); for example: 22 indicates 10 p.m.
    local_msg.setHour("19");
    // Set the minute when the message is triggered, for example: 05 indicates the 5th minute in the hour
    local_msg.setMin("31");
    // Set the message style. The default value is 0 or not set
    local_msg.setBuilderId(0);
    // Set the action type: 1 - open the activity or the app itself; 2 - open the browser; 3 - open the Intent; 4 - open the application by the package name
    local_msg.setAction_type(1);
    // Set the app-pulling page
    local_msg.setActivity("com.qq.xgdemo.SettingActivity");
    // Set the URL
    local_msg.setUrl("http://www.baidu.com");
    // Set the Intent
    local_msg.setIntent("intent:10086#Intent;scheme=tel;action=android.intent.action.DIAL;S.key=value;end");
    //Whether to overwrite the save settings of the original build_id. 1: Yes; 0: No.
    local_msg.setStyle_id(1);
    // Set the audio resource
    local_msg.setRing_raw("mm");
    // Set the key and value
    HashMap<String, Object> map = new HashMap<String, Object>();
    map.put("key", "v1");
    map.put("key2", "v2");
    local_msg.setCustomContent(map);
    // Add the notification to the local system     
    XGPushManager.addLocalNotification(context,local_msg);
    

    Clearing local notifications

    API description

    This API is used to clear local notifications that are created by the application but have not popped up.

    public static void clearLocalNotifications(Context context) 
    

    Parameter description

    • context: Context object

    Sample code

    XGPushManager.clearLocalNotifications(context);
    

    Account Management

    The following are account management API methods. For more information on the timing and principle of calls, please see Account flow.

    Adding an account

    API description

    This API is used to add or update an account. If there is no account of this type, it will add a new one; otherwise, it will overwrite the existing one.

    public static void upsertAccounts(Context context, List<AccountInfo> accountInfoList, XGIOperateCallback callback)
    

    Parameter description

    • context: Context object
    • accountInfoList: account list, containing account types and account names
    • callback: callback of account binding operation

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int flag) {
          Log.i("TPush", "onSuccess, data:" + data + ", flag:" + flag);
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          Log.w("TPush", "onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
      }
    };
    List<XGPushManager.AccountInfo> accountInfoList = new ArrayList<>();
    accountInfoList.add(new XGPushManager.AccountInfo(XGPushManager.AccountType.UNKNOWN.getValue(), "account-test"));
    XGPushManager.upsertAccounts(context, accountInfoList, xgiOperateCallback);
    
    Note:

    • Each account can be bound to up to 100 tokens.
    • The account can be email, QQ account number, mobile number, username, etc. For valid values, please see Account Type Value Table.
    • The TPNS console supports push to account IDs of the 0 account type. For other types, call the Push API to push.
    • If multiple devices are bound to the same account, the backend will push the message to the last bound device by default. If you want to push to all the bound devices, you can view the account_push_type parameter settings in Push API.

    Adding a mobile number

    API description

    This API is used to add or update a mobile number. If you have bound any mobile number before, it will overwrite the original number; if you haven’t, it will be bound (SDK 1.2.5.0+).

    Note:

    The mobile number format is +[country or area code][mobile number], for example +8613711112222 (there is a + sign in the front; 86 is the country code; 13711112222 is the mobile number). If the entered mobile number does not contain a country or area code, TPNS will automatically add +86 as the prefix when sending SMS messages. If the mobile number contains a country or area code, it will be bound as is. To delete the bound mobile number, call the delAccountsByKeys API and set accountTypeSet to 1002.

    public static void upsertPhoneNumber(Context context, String phoneNumber, XGIOperateCallback callback) 
    

    Parameter description

    • context: Context object
    • phoneNumber: an E.164 mobile number in the format of [+][country code or area code][mobile number], for example, +8613711112222
    • callback: callback of mobile number binding operation

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
    @Override
    public void onSuccess(Object data, int flag) {
        Log.i("TPush", "onSuccess, data:" + data + ", flag:" + flag);
    }
     @Override
    public void onFail(Object data, int errCode, String msg) {
        Log.w("TPush", "onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
    }
    };
    XGPushManager.upsertPhoneNumber(context, phoneNumber, xgiOperateCallback);
    

    Unbinding an account

    API description

    This API is used to unbind a bound account.

    // Unbind the specified account (with registration callback)
    void delAccount(Context context, final String account, XGIOperateCallback callback)    
    // Unbind the specified account (without registration callback)
    void delAccount(Context context, final String account )
    
    Note:

    Account unbinding just removes the association between the token and the application account. If full/tag/token push is used, notifications/messages can still be received.

    Parameter description

    • context: context object of the current application, which cannot be null
    • account: account

    Sample code

    XGPushManager.delAccount(getApplicationContext(),"test");
    

    Unbinding by account type

    API description

    This API is used to unbind accounts of one or multiple types. (SDK v1.2.3.0+)

    public static void delAccounts(Context context, final Set<Integer> accountTypeSet, XGIOperateCallback callback)
    

    Parameter description

    • context: Context object
    • accountTypeSet: type of the account to be unbound
    • callback: callback of account unbinding operation

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int flag) {
          Log.i("TPush", "onSuccess, data:" + data + ", flag:" + flag);
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          Log.w("TPush", "onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
      }
    };
    
    Set<Integer> accountTypeSet = new HashSet<>();
    accountTypeSet.add(XGPushManager.AccountType.CUSTOM.getValue());
    accountTypeSet.add(XGPushManager.AccountType.IMEI.getValue());
    XGPushManager.delAccounts(context, accountTypeSet, xgiOperateCallback);
    

    Clearing all accounts

    Note:

    The delAllAccount API is disused in SDK v1.2.2.0. The clearAccounts API is recommended.

    API description

    This API is used to unbind all bound accounts.

    // Unbind all accounts (with registration callback)
    void clearAccounts(Context context, XGIOperateCallback callback)
    // Unbind all accounts (without registration callback)
    void clearAccounts(Context context)
    
    Note:

    Account unbinding just removes the association between the token and the application account. If full/tag/token push is used, notifications/messages can still be received.

    Parameter description

    context: context object of the current application, which cannot be null

    Sample code

    XGPushManager.clearAccounts(getApplicationContext());
    

    Tag Management

    The following are tag management API methods. For more information on the timing and principle of calls, please see Tag flow.

    Preset tags

    Currently, TPNS preset tags include application version, system version, province, active information, system language, SDK version, country/region, phone brand, and phone model tags. Preset tags are automatically reported in the SDK.

    Overwriting multiple tags

    API description

    Setting multiple tags at a time will overwrite tags previously set for this device.
    You can set tags for different users and then send mass notifications based on tag names. An application can have up to 10,000 tags, and each token can have up to 100 tags in one application. If you want to increase the limits, please submit a ticket for assistance. Each custom tag can be bound to an unlimited number of device tokens, and no spaces are allowed in the tag.

    public static void clearAndAppendTags(Context context, String operateName, Set<String> tags) 
    

    Parameter description

    • context: Context object
    • operateName: user-defined operation name. The callback result will return it as-is, which is used to identify the operation to which the callback belongs.
    • tags: a collection of tag names, and each tag is a string. Restrictions: each tag cannot exceed 50 bytes (otherwise, the tag will be discarded) nor contain spaces (all spaces will be deleted). Up to 100 tags can be set, and excessive ones will be discarded.

    Processing result

    The result can be obtained by reloading the onSetTagResult method of XGPushBaseReceiver.

    Sample code

    String[] tags = "tag1 tag2".split(" ");
    Set<String> tagsSet = new HashSet<>(Arrays.asList(tags));
    XGPushManager.clearAndAppendTags(getApplicationContext(), "clearAndAppendTags :" + System.currentTimeMillis(), tagsSet); 
    

    Adding multiple tags

    Note:

    The addTags API is disused in SDK v1.2.2.0. The appendTags API is recommended.

    API description

    • If all tags to be added contain a colon (:), for example, test:2, level:2, all test:* and level:* tags bound with the device will be deleted before the test:2 and level:2 tags are added.
    • If certain tags to be added do not contain a colon (:), for example, test:2 level, all historical tags of the device will be deleted before the test:2 and level tags are added.
      Note:

      In newly added tags, a colon (:) is the backend keyword. Use it according to your business scenarios.

    • This API should be called at a certain interval (an interval longer than 5 seconds is recommended); otherwise, update may fail.
      public static void appendTags(Context context, String operateName, Set<String> tags) 
      

    Parameter description

    • context: Context object
    • operateName: user-defined operation name. The callback result will return it as-is, which is used to identify the operation to which the callback belongs.
    • tags: a collection of tag names, and each tag is a string. Restrictions: each tag cannot exceed 50 bytes (otherwise, the tag will be discarded) nor contain spaces (all spaces will be deleted). Up to 100 tags can be set, and excessive ones will be discarded.

    Processing result

    The result can be obtained by reloading the onSetTagResult method of XGPushBaseReceiver.

    Sample code

    String[] tags = "tag1 tag2".split(" ");
    Set<String> tagsSet = new HashSet<>(Arrays.asList(tags));
    XGPushManager.appendTags(getApplicationContext(), "appendTags:" + System.currentTimeMillis(), tagsSet);
    

    Deleting multiple tags

    Note:

    The deleteTags API is disused in SDK v1.2.2.0. The delTags API is recommended.

    API description

    This API is used to delete multiple tags at a time.

    public static void delTags(Context context, String operateName, Set<String> tags, XGIOperateCallback callback) 
    

    Parameter description

    • context: Context object
    • operateName: user-defined operation name. The callback result will return it as-is, which is used to identify the operation to which the callback belongs.
    • tags: a collection of tag names, and each tag is a string. Restrictions: each tag cannot exceed 50 bytes (otherwise, the tag will be discarded) nor contain spaces (all spaces will be deleted). Up to 100 tags can be set, and excessive ones will be discarded.
    • callback: callback of tag deletion operation

    Processing result

    The result can be obtained by reloading the onSetTagResult method of XGPushBaseReceiver.

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int flag) {
          Log.i("TPush", "onSuccess, data:" + data + ", flag:" + flag);
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          Log.w("TPush", "onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
      }
    };
    
    Set<String> tagSet = new HashSet<>();
    tagSet.add("tag1");
    tagSet.add("tag2");
    XGPushManager.delTags(context, "delTags", tagSet, xgiOperateCallback);
    

    Clearing all tags

    Note:

    The cleanTags API is disused in SDK v1.2.2.0 and later versions. You are advised to use the clearTags API.

    API description

    This API is used to clear all tags of a device.

    public static void clearTags(Context context, String operateName, XGIOperateCallback callback)
    

    Parameter description

    • context: Context object
    • operateName: user-defined operation name. The callback result will return it as-is, which is used to identify the operation to which the callback belongs.
    • callback: callback of tag clearing operation

    Processing result

    The result can be obtained by reloading the onSetTagResult method of XGPushBaseReceiver.

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int flag) {
          Log.i("TPush", "onSuccess, data:" + data + ", flag:" + flag);
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          Log.w("TPush", "onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
      }
    };
    
    XGPushManager.clearTags(context, "clearTags", xgiOperateCallback);
    

    Querying tags

    Note:

    This API is used to get the tags bound to a device and available only for v1.2.5.0 and later.

    API description

    Get the tags bound to the device.

      public static void queryTags(final Context context, final String operateName, final int offset, final int limit, final XGIOperateCallback callback)
    

    Parameter description

    • context: Context object.
    • operateName: operation name defined by the user. The callback result will be returned as-is for users to distinguish the operation.
    • offset: the starting point
    • limit: number of tags to get; maximum value: 100
    • callback: callback of tag getting operation

    Processing result

    The result can be obtained by reloading the onQueryTagsResult method of XGPushBaseReceiver.

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int flag) {
          Log.i("TPush", "onSuccess, data:" + data + ", flag:" + flag);
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          Log.w("TPush", "onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
      }
    };
    XGPushManager.queryTags(context, 0, 100, xgiOperateCallback);
    

    User Attribute Management

    You can set attributes for different users and then perform personalized push in TPNS. The following are user attribute API methods. For more information on the timing and principle of calls, please see User attribute flow.

    Adding user attributes

    API description

    This API is used to add an attribute (with callback). If there is no attribute, it will add one; otherwise, it will overwrite the existing one.

    public static void upsertAttributes(Context context, String operateName, Map<String, String> attributes, XGIOperateCallback callback)
    

    Parameter description

    • context: Context object
    • operateName: operation name defined by the user. The callback result will be returned as-is for users to distinguish the operation.
    • attributes: attribute set, where each attribute is identified by key-value
    • callback: callback of attribute adding operation
    Note:

    1. Attributes are transferred through key-value pairs, and only non-empty strings can be accepted.
    2. There can be up to 50 attributes.
    3. Both the key and value of an attribute can contain up to 50 characters.

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int flag) {
          log("action - onSuccess, data:" + data + ", flag:" + flag);
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          log("action - onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
      }
    };
    
    Map<String,String> attr = new HashMap<>();
    attr.put("name", "coding-test");
    attr.put("gender", "male");
    attr.put("age", "100");
    XGPushManager.upsertAttributes(context, "addAttributes-test", attr, xgiOperateCallback);
    

    Deleting a user attribute

    API description

    This API is used to delete a specified attribute.

    public static void delAttributes(Context context, String operateName, Set<String> attributes, XGIOperateCallback callback)
    

    Parameter description

    • context: Context object
    • operateName: operation name defined by the user. The callback result will be returned as-is for users to distinguish the operation.
    • attributes: attribute set, where each attribute is identified by key-value
    • callback: callback of attribute deleting operation
    Note:

    1. Attributes are transferred through key-value pairs, and only non-empty strings can be accepted.
    2. There can be up to 50 attributes.
    3. Both the key and value of an attribute can contain up to 50 characters.

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int flag) {
          log("action - onSuccess, data:" + data + ", flag:" + flag);
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          log("action - onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
      }
    };
    Set<String> stringSet = new HashSet<>();
    stringSet.add("name");
    stringSet.add("gender");
    
    XGPushManager.delAttributes(context, "delAttributes-test", stringSet, xgiOperateCallback);
    

    Clearing all user attributes

    API description

    This API is used to delete all configured attributes.

    public static void clearAttributes(Context context, String operateName, XGIOperateCallback callback)
    

    Parameter description

    • context: Context object
    • operateName: operation name defined by the user. The callback result will be returned as-is for users to distinguish the operation.
    • callback: callback of attribute clearing operation

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int flag) {
          log("action - onSuccess, data:" + data + ", flag:" + flag);
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          log("action - onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
      }
    };
    
    XGPushManager.clearAttributes(context, "cleanAttributes-test", xgiOperateCallback);
    

    Updating user attributes

    API description

    This API is used to set an attribute (with callback). It will overwrite all the attributes previously set for this device (i.e., clearing and setting).

    Note:

    1. Attributes are transferred through key-value pairs, and only non-empty strings can be accepted.
    2. There can be up to 50 attributes.
    3. Both the key and value of an attribute can contain up to 50 characters.
    public static void clearAndAppendAttributes(Context context, String operateName, Map<String, String> attributes, XGIOperateCallback callback)
    

    Parameter description

    • context: Context object
    • operateName: operation name defined by the user. The callback result will be returned as-is for users to distinguish the operation.
    • attributes: attribute set, where each attribute is identified by key-value
    • callback: callback of attribute setting operation

    Sample code

    XGIOperateCallback xgiOperateCallback = new XGIOperateCallback() {
      @Override
      public void onSuccess(Object data, int flag) {
          log("action - onSuccess, data:" + data + ", flag:" + flag);
      }
       @Override
      public void onFail(Object data, int errCode, String msg) {
          log("action - onFail, data:" + data + ", code:" + errCode + ", msg:" + msg);
      }
    };
    
    Map<String,String> attr = new HashMap<>();
    attr.put("name", "coding-test");
    attr.put("gender", "male");
    attr.put("age", "100");
    XGPushManager.clearAndAppendAttributes(context, "setAttributes-test", attr, xgiOperateCallback);
    

    Configuration APIs

    All configuration APIs are in the XGPushConfig class. For configurations to take effect in time, you need to ensure that configuration APIs are called before launching or registering TPNS.

    Disabling session keep-alive (1.1.6.1+)

    TPNS enables the session keep-alive feature by default. To disable it, please call the following API in onCreate of Application or LauncherActivity during application initialization and pass in false:

    XGPushConfig.enablePullUpOtherApp(Context context, boolean pullUp);
    

    Parameter description

    • context: application context
    • pullUp: true (enable session keep-alive); false (disable session keep-alive)
    Note:

    If the following log is printed, the session keep-alive feature has been disabled: I/TPNS: [ServiceUtil] disable pull up other app.

    Sample code

    XGPushConfig.enablePullUpOtherApp(context, false); // Default value: true (enable keep-alive)
    

    Debug mode

    API description

    To ensure data security, make sure the debug mode is turned off when publishing.

    public static void enableDebug(Context context, boolean debugMode)
    

    Parameter description

    • context: context object of the application
    • debugMode: the default value is false. To enable debug logging, set it to true.

    Sample code

    XGPushConfig.enableDebug(context, true); // Default value: false (do not enable)
    

    Getting a device token

    API description

    A token is the unique ID for TPNS to stay connected with the backend and the unique ID for an application to receive messages. A device token can be obtained only after the device is successfully registered. The obtaining methods are described as follows. (The TPNS token may change if the application is uninstalled and reinstalled.)

    Through the registration API with callback

    In the onSuccess(Object data, int flag) method of the registration API with XGIOperateCallback, the data parameter is the token. For more information, please see the relevant sample of the registration API.

    By reloading XGPushBaseReceiver

    Reload the onRegisterResult (Context context, int errorCode,XGPushRegisterResult registerMessage) method of XGPushBaseReceiver and get the token through the getToken API provided by the registerMessage parameter. For more information, please see Getting registration results.

    Through the XGPushConfig.getToken(context) API

    Once the device is successfully registered, the token will be stored locally and then can be obtained through the XGPushConfig.getToken(context) API.

    Token is the identity ID of a device. It is randomly generated by the server based on the device attributes and delivered to the local system. The token of the same application varies by device.

    public static String getToken(Context context)
    
    Note:

    A token is generated during the first application registration and will be stored in the mobile phone. The token always exists no matter whether unregistration is performed subsequently. After the application is uninstalled and reinstalled, the token will change. The token varies by application.

    Parameter description

    context: context object of the application

    Sample code

    XGPushConfig.getToken(context);
    

    Returned values

    A standard token will be returned upon success, and null or 0 upon failure.

    Getting a third-party vendor token

    API description

    A third-party token is the identity ID of a vendor device. It is delivered to the local system by the vendor. The token of the same application varies by device.

    public static String getOtherPushToken(Context context) 
    
    Note:

    This API can be called only after successful registration; otherwise, null will be returned.

    Parameter description

    context: context object of the application

    Sample code

    XGPushConfig.getOtherPushToken(context);
    

    Returned values

    A standard token will be returned upon success, and null or 0 upon failure.

    Setting the accessId

    API description

    If the accessKey is already set in AndroidManifest.xml, you do not need to call this API again; if you still call this API, the accessKey set through this API will prevail.

    public static boolean setAccessId(Context context, long accessId)
    

    Parameter description

    • Context: object
    • accessId: accessId obtained through registration in the console

    Sample code

    long accessId = 0L; // `accessId` of the current application
    XGPushConfig.setAccessId(context, accessId);
    

    Returned values

    • true: success.
    • false: failure.
    Note:

    The accessId set through this API will also be stored in the AndroidManifest.xml file.

    Setting the accessKey

    API description

    If the accessKey is already set in AndroidManifest.xml, you do not need to call this API again; if you still call this API, the accessKey set through this API will prevail.

    public static boolean setAccessKey(Context context, String accessKey) 
    

    Parameter description

    • Context: object
    • accessKey: accessKey obtained through registration in the console

    Sample code

    String accessKey = ""; // `accessKey` of your application
    XGPushConfig.setAccessKey(context, accessKey);
    

    Returned values

    • true: success.
    • false: failure.
    Note:

    The access key set through this API will also be stored in the AndroidManifest.xml file.

    Reporting logs

    API description

    If you find exceptions with TPush, you can call this API to trigger reporting of local push logs. To report the problem, submit a ticket with the file address provided to facilitate troubleshooting.

    public static void uploadLogFile(Context context, HttpRequestCallback httpRequestCallback)
    

    Parameter description

    • context: Context object, which cannot be null
    • httpRequestCallback: log reporting result callback, which include callbacks for success and failure and cannot be null

    Sample code

    XGPushManager.uploadLogFile(context, new HttpRequestCallback() {
    @Override
    public void onSuccess(String result) {
         Log.d("TPush", "Upload succeeded. File address:" + result);
    }
    @Override
    public void onFailure(int errCode, String errMsg) {
         Log.d("TPush", "Upload failed. Error code:" + errCode + ", error message:" + errMsg);
    }
    });
    
    Note:

    You need to enable XGPushConfig.enableDebug(this, true); first.