What should I do when Xcode 13 for iOS 9 reports an error during compilation saying that it is unable to load UserNotifications.framework or start the archive package.
Error message:
Dyld Error Message:
Dyld Message: Library not loaded: /System/Library/Frameworks/UserNotifications.framework/UserNotifications
Solution: go to Targets > Build Phases > Link Binary With Libraries and set UserNotifications.framework to Optional or use an earlier version for packaging.
Why is a development environment token considered as a production environment token in iOS? How do I deal with the issue?
If an application is installed in the Xcode development environment, and development environment messages are pushed through Tencent Push Notification Service, the following error messages are reported:
Error message reported when you query the token using the push troubleshooting tool in the Tencent Push Notification Service console
Error log recorded when you debug the Tencent Push Notification Service SDK in Xcode
Missing Provisioning Profile - iOS Apps must contain a provisioning profile named embedded.mobileprovision.
The provisioning profile is missing. iOS apps must contain a provisioning profile named `embedded.mobileprovision`.
Error cause: the application package does not contain the embedded.mobileprovision configuration file, making the token environment unknown.
Solution:
1. In the Xcode menu bar, choose File > Project Settings.
2. Set Build System to Legacy Build System and click Done.
3. Build the application again, and uninstall and reinstall it.
4. After successful registration, push messages to test the token.
Why can't pushes be received in an iOS build production environment?
1. Check whether the production environment meets the following testing conditions: the application is the ad-hoc/App Store build (with the release certificate "Production"), and the release certificate is uploaded and successfully verified.
2. Check whether the bundle id configured in the Xcode project matches the configured Provision Profile file and whether the Provision Profile file corresponding to the application has been configured with the message push capability.
3. Check whether the environment specified by the aps-environment field in the embedded.mobileprovision file is correct.
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 Tencent Push Notification Service 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).
5. Check whether the certificate environment and corresponding Bundle ID match the application as shown below:
Why doesn't clicking a notification trigger a callback for the notification clicking event when the application is cold started?
1. Check the version of the Tencent Push Notification Service SDK. If it is v1.2.5.3 or earlier, you are recommended to upgrade it to v1.2.5.4 or later.
2. Check the timing for calling the Tencent Push Notification Service SDK initialization method. Currently, the Tencent Push Notification Service SDK initialization method needs to be called as soon as possible in the main thread of the application startup method to ensure that the Tencent Push Notification Service SDK is set as the proxy of the notification center in the first time.
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 Tencent Push Notification Service supports .p8 certificates?
A .p8 certificate has security risks. Although its validity is longer than that of a .p12 certificate, it has a wider push permission and scope. If leaked, it may cause more severe consequences. Tencent Push Notification Service recommends you use .p12 certificates to manage the push services of your applications separately. If you insist on using .p8 certificates, follow the steps below for application:
1. Go to the certificate page of the Developer center, select Keys, and click + to create a .p8 certificate.
2. Enter the certificate name (Key Name) and select the corresponding capability (APNs).
3. Download the certificate (a .p8 certificate can be downloaded only once after creation).
Why can't push messages be received?
Message push involves various associated modules, and exception in any steps can lead to message delivery failure. If message delivery failures occur, you are recommended to use the Toolbox for troubleshooting. Below are the most common issues:
Client troubleshooting
Check the notification settings of the device
Go to Notifications > App name to check whether your app has enabled message push.
Check the network settings 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, Tencent Push Notification Service 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 Tencent Push Notification Service backend, and the Tencent Push Notification Service 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 Tencent Push Notification Service server sends a message to an iOS device via APNs. If APNs fails, the Tencent Push Notification Service server will fail to request APNs to deliver the message to the device.
Tencent Push Notification Service server problem
The Tencent Push Notification Service 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 Tencent Push Notification Service 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.
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 Tencent Push Notification Service 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?
Yes. If notifications are delivered when devices are offline (the persistent connection is interrupted due to a shutdown, airplane mode, or network exception):
For the vendor channel (APNs), only the last notification delivered is retained, for less than 24 hours.
For the Tencent Push Notification Service channel, the last three notifications delivered are retained, for 72 hours.
Why is arrival data unavailable for iOS?
iOS 9.x and earlier versions do not provide an API to listen to the arrival of messages at the device. Therefore, arrival data can be collected.
iOS 10.0 and later versions provide the Service Extension API, which can be called by the client to listen to the arrival of messages. For more information, please see Notification Service Extension.
How do I create silent push with the Tencent Push Notification Service 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 application. 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.
Sample:
{
"platform":"ios",
"audience_type":"token",
"environment":"dev",
"token_list":[
"05a8ea6924590dd3a94480fa1c9fc8448b4e"],
"message_type":"notify",
"message":{
"ios":{
"aps":{
"badge_type":-2
}
}
}
}
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 Tencent Push Notification Service SDK for iOS (1.2.7.2–1.2.5.4), uses the Recall feature of Tencent Push Notification Service, and implements the following system callback:
Then you may encounter this error. You can use the override feature to process sent messages.
What should I do if Error Domain=NSCocoaErrorDomain Code=1001. APNs' request for a token failed is reported during Xcode debugging?
Problem description:
The following error is reported during Xcode debugging: "Error Domain=NSCocoaErrorDomain Code=1001. APNs' request for a token failed during Xcode debugging. -> Please resolve the problem as follows: use 4G network and restart the phone. If the problem persists after the phone is restarted for multiple times, you are recommended to use another phone for testing." However, the problem persists after I fixed the problem as instructed.
Troubleshooting process:
1. Use a relevant method in the Tencent Push Notification Service SDK to avoid running at the same time as other methods for registering remote notifications.
2. Change Xcode's build system to the legacy build system to see if there is any repeated class definition caused by repeated import of the static library. The procedure is as follows:
2.1 In the Xcode menu bar, choose File > Project Settings.
2.2 Set Build System to Legacy Build System and click Done.
2.3 Compile again. If a compilation error occurs, make modifications accordingly.
Why no message arrival data is reported after a message is delivered successfully?
Troubleshooting process:Message delivered via the APNs channel:
1. Check whether the notification service extension plugin is configured (details). If the plugin is not configured, arrival data cannot be reported.
2. It could be that the arrival event failed to be collected but the message has actually been sent to the mobile phone (the actual push effect is not affected). Check whether the mobile phone network is normal or whether APNs delivery was delayed.
Message delivered via the Tencent Push Notification Service channel:
Possible case 1: The Tencent Push Notification Service backend delivered the message via the Tencent Push Notification Service channel when the link between the Tencent Push Notification Service SDK and the backend was actually disconnected. As a result, the message failed to reach the device.
Possible case 2: No arrival data was reported but the message actually reached the device (the actual push effect is not affected).
Yes
No
Was this page helpful?