Last updated: 2021-03-03 15:29:37

    What should I do if the error building for iOS Simulator, but linking in object file built for iOS is reported when the Xcode 12 simulator integrates with the notification extension plugin during the build?

    You need to find the extension plugin target, click Build Settings > Excluded Architectures, and add the arm64 instruction set, as shown in the following figure:

    What should I do if push certificate upload failed in the TPNS console?

    Convert the .p12 file of the push certificate into a .pem file and troubleshoot as follows:

    1. Open the Terminal and go to the .p12 file directory.
    2. Run the following command to generate a certificate (apns-dev-cert is the name of the sample push certificate, which should be replaced with the name of your certificate).
    openssl pkcs12 -clcerts -nokeys -out apns-dev-cert.pem -in apns-dev-cert.p12
    1. Enter the password of the .p12 file.
    2. Run the following command to convert the .pem certificate into text:
    openssl x509 -in apns-dev-cert.pem -inform pem -noout -text
    1. Check whether the certificate environment and corresponding Bundle ID match the application as shown below:

    What should I do if an empty notification cannot pop up on devices on iOS 10 or below?

    The content field cannot be empty if the RESTful API is called for push; otherwise, the notification will not pop up on devices on iOS 10 or below.

    Does TPNS support .p8 certificates?

    A .p8 certificate has security risks. Although it is valid longer than a .p12 certificate, it has a wider push permission and scope. If leaked, it may cause more severe consequences. TPNS recommends you use .p12 certificates to manage the push services of your applications separately.

    What should I do if the simulator for TPNS SDK v1.2.5.4 or below prompts that the XGForFreeVersion symbol cannot be found?

    SDK v1.2.5.4 or below only supports debugging on real devices. If you need to use the simulator for debugging, please upgrade to the latest version.

    Why can't push messages be received?

    Message push involves various associated modules, and exception in any steps can lead to message delivery failure. Below are the most common issues:

    Client troubleshooting

    • Check the notification setting of the device
      Please go to Notifications > App name to check whether your app has enabled message push.
    • Check the network setting of the device
      If there is a network issue, the client may fail to obtain the message-receiving token when registering for APNs. As a result, TPNS cannot be used to push messages to specified devices.

    If the device is not connected to the Internet, it cannot receive the message, even if the client has correctly obtained the token, registered it with the TPNS backend, and the TPNS server has successfully delivered the message. The message might be received if the device reconnects to the Internet within a short time, as APNs will retain the message for some time and deliver it again.

    Check the SDK integration. After the SDK is integrated, please make sure that it can get the device token used to receive messages. For more information, please see iOS SDK Integration Guide.

    Server troubleshooting

    • APNs server problem
      The TPNS server sends a message to an iOS device via APNs. If APNs fails, the TPNS server will fail to request APNs to deliver the message to the device.
    • TPNS push server problem
      The TPNS server achieves message delivery through the collaboration of multiple feature modules. If an exception occurs in any of these modules, message push will fail.

    Push certificate troubleshooting
    When the TPNS server requests APNs to deliver the message, it needs to use two required parameters: the message push certificate and the device token. When pushing the message, please make sure that the message push certificate is valid. For more information on how to configure the message push certificate, please see Acquisition of Push Certificate.

    Why does account/tag binding or unbinding not work?

    When SDK APIs are used to bind or unbind accounts/tags, the TPNS server needs about 10 seconds to sync data.

    What do I do if the error no valid 'aps-environment' entitlement string found for application is reported in terminal?

    Check whether the bundle ID configured in the Xcode project matches the configured provisioning profile, and whether the provisioning profile corresponding to the app has been configured with the message push capability.

    How does the client play the custom push message audio?

    First, on the device development side, put the audio file in the bundle directory.

    • If you use the TPNS console to create a push, enter the audio file name in Advanced Settings (the full path of the audio file is not required).
    • If you use RESTful APIs, set the sound parameter to the name of the audio file (the full path of the audio file is not required).

    Does iOS support offline retention of push messages?

    No. When the TPNS server sends a message to APNs, if APNs finds that the device is not online, it will retain the message for a while. However, the duration of the retention is not clear.

    Why is arrival data unavailable for iOS?

    • OS versions earlier than iOS 9.x do not provide an API to listen to the arrival of messages at the device. Therefore, the arrival data can be collected.
    • OS versions later than iOS 10.0 provide the Service Extension API, which can be called by the client to listen to the arrival of messages.

    How do I create silent push with the TPNS server SDK?

    Set content-available to 1 and do not use alert, badge, or sound.

    What should I do if DeviceToken is not returned occasionally for registration or APNs' request for token fails in the development environment of iOS?

    This problem is caused by instability of APNs. You can fix it in the following ways:

    1. Insert a SIM card into the phone and use the 4G network.
    2. Uninstall and reinstall the application, restart the application, or shut down and restart the phone.
    3. Use a package for the production environment.
    4. Use another iPhone.

    How do I expand the testing scope on iOS if the number of testing devices is limited?

    1. Enterprise signature certificate
      Apply for enterprise signature and push certificates and release your application as follows:
      Use the enterprise signature certificate to build and release your app. Testers can download and install the application through the dedicated enterprise channel.
    2. App Store signature certificate
      Use the current push certificate released on App Store as follows:
      Release the preview version in TestFlight: upload the IPA package to App Store Connect, use TestFlight to create a beta version, and set the list of testers (Apple IDs) for the specified version in TestFlight. Testers can download and install your application through the official TestFlight application on App Store.

    For iOS, how do I configure to change the badge number only without displaying the message?

    When creating a push, you can use the API to specify the notification bar message type, leave the title empty, and only set badge_type. For more information, please see Push API.
    See below as an example:

        "platform": "ios",
        "audience_type": "token",
            "token_list": [
            "aps": {

    What should I do if my application reports the error Crash: you can't call -sendResponse: twice nor after encoding it?

    If your application integrates TPNS SDK for iOS (–, uses the Recall feature of TPNS, and implements the following system callback:

    - (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo  fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler

    Then you may encounter this error. You can use the Override feature to process sent messages.

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback