@tencent-rtc/mcp 1.4.7 → 1.6.0

package/resource/knowledge/push/integration/uni-app.md

@@ -0,0 +1,208 @@
+### Effect Showcase
+| Xiaomi 11 Pro (Integrated with <a href="https://ext.dcloud.net.cn/plugin?id=9035">CallKit</a>) | iPhone 13 | Samsung Galaxy A23 Overseas Version (Google FCM Push) |
+| --- | --- | --- |
+
+### Integrate TencentCloud-Push
+
+HBuilderX 4.29 has a bug. Please use HBuilderX 4.36 or higher and upgrade [uni-app Tencent Cloud Push Service (Push)](https://ext.dcloud.net.cn/plugin) to version 1.1.0 or higher.
+
+### Step 1: Downloading the plugin and importing it into **HBuilderX**
+1. Open [uni-app Tencent Cloud Push Service (Push)](https://ext.dcloud.net.cn/plugin), click **Download the plugin and import it into HBuilderX**, and import the plugin into the HBuilderX project.
+
+2. Select the project you want to integrate and click **OK**.
+
+3. The effect after integration is shown below:
+
+### Step 2. Offline push configuration
+
+> **Note:**
+>
+> 1. HBuilderX 4.36 has released non-backward compatible updates. If you are using HBuilderX 4.36 or higher and need vendor push for vivo/Honor, please upgrade the push version to 1.1.0 or higher and refer to the documentation to correctly configure `manifestPlaceholders.json` and `mcs-services.json`.
+> 2. You need to configure push notifications in the `nativeResources` directory. If this folder is not yet created in the project root directory, please create a new folder named `nativeResources`.
+> 3. Ensure that the `nativeResources` directory exists in the project opened with HBuilderX and is at the same level as the `uni_modules` directory.
+
+【Android】
+1. Create the directory `nativeResources/android/assets`.
+
+2. Configure `timpush-configs.json` (download from [Push Service > Access Settings > One-click Quick Configuration](https://console.trtc.io/chat/push-plugin-push-identifier)) to the `nativeResources/android/assets/` directory. As shown in the figure:
+
+3. Huawei, HONOR, vivo, FCM.
+
+【FCM】
+1. Configure `com.google.gms.google-services` to `uni_modules/TencentCloud-Push/utssdk/app-android/config.json` in `project.plugins`, as shown below:
+
+``` json
+"project": {
+  	"plugins": [
+        ...
+  		"com.google.gms.google-services"
+  	],
+  	"dependencies": [
+  		"com.huawei.agconnect:agcp:1.9.1.301",
+		"com.google.gms:google-services:4.3.15",
+		"com.hihonor.mcs:asplugin:2.0.1.300"
+  	]
+}
+```
+
+2. Configure the `google-services.json` file to the `nativeResources/android/` directory (Note! Do not configure it to the `nativeResources/android/assets` directory). As shown in the figure:
+
+【Huawei】
+
+【HONOR】
+3. Edit `uni_modules/TencentCloud-Push/utssdk/app-android/config.json` in `dependencies`, add `"com.tencent.timpush:honor:8.3.6498"`.
+
+``` bash
+{
+     ...
+     "dependencies": [
+         ...
+         "com.tencent.timpush:honor:8.3.6498"
+     ]
+}
+```
+4. Configure the `mcs-services.json` file to the `nativeResources/android` directory (for details on obtaining this file, see Vendor Configuration > uniapp > Honor > Step 3.2: Enter Application Details, Bind Application Package Name, Download mcs-services.json File).
+
+5. Configure `appID` to `nativeResources/android/manifestPlaceholders.json` in `"HONOR_APPID"`.
+
+``` bash
+{
+     "HONOR_APPID": ""
+}
+```
+
+【vivo】
+6. Edit `uni_modules/TencentCloud-Push/utssdk/app-android/config.json` in `dependencies`, add `"com.tencent.timpush:vivo:8.3.6498"`.
+
+``` bash
+{
+     ...
+     "dependencies": [
+         ...
+         "com.tencent.timpush:vivo:8.3.6498"
+     ]
+}
+```
+7. Configure `appID` and `appKey` to `nativeResources/android/manifestPlaceholders.json` in `VIVO_APPKEY` and `VIVO_APPID`.
+
+``` bash
+{
+     "VIVO_APPKEY": "",
+     "VIVO_APPID": "",
+}
+```
+
+【iOS】
+1. Create the directory `nativeResources/ios/Resources`.
+
+2. Create a `timpush-configs.json` file in `nativeResources/ios/Resources`.
+
+3. Add the certificate ID obtained from [Chat Console > Push Service > Access Settings](https://console.trtc.io/chat/push-plugin-push-identifier) to the `timpush-configs.json` file. As shown below:
+
+``` json
+{
+    "businessID":"xxx"
+}
+```
+
+### Step 3. Introduce and register Tencent Cloud Push Service (Push)
+
+Replace `SDKAppID` and `appKey` with the application information obtained from [Chat Console - Push Service - Access Settings page](https://console.trtc.io/chat/push-plugin-push-identifier). As shown in the figure:
+
+``` javascript
+// Integration of TencentCloud-Push
+import * as Push from '@/uni_modules/TencentCloud-Push';
+const SDKAppID = 0; // Your SDKAppID
+const appKey = ''; // Client Key
+
+// If you need to connect with the Chat login userID (i.e., push messages to this userID), please use the setRegistrationID API
+// Push.setRegistrationID(userID, () => {
+    // console.log('setRegistrationID ok', userID);
+// });
+
+Push.registerPush(SDKAppID, appKey, (data) => {
+        console.log('registerPush ok', data);
+        Push.getRegistrationID((registrationID) => {
+            console.log('getRegistrationID ok', registrationID);
+        });
+    }, (errCode, errMsg) => {
+        console.error('registerPush failed', errCode, errMsg);
+    }
+);
+
+// Listen for notification bar click events to get push extension information
+Push.addPushListener(Push.EVENT.NOTIFICATION_CLICKED, (res) => {
+    // res is the push extension information
+    console.log('notification clicked', res);
+});
+
+// Listen for online push
+Push.addPushListener(Push.EVENT.MESSAGE_RECEIVED, (res) => {
+    // res is the message content
+    console.log('message received', res);
+});
+
+// Listen for online push recall
+Push.addPushListener(Push.EVENT.MESSAGE_REVOKED, (res) => {
+    // res is the ID of the recalled message
+    console.log('message revoked', res);
+});
+```
+
+### Step 4. Use cloud certificates to generate custom base
+
+Click **Run** > **Run to mobile device or emulator** > **Create custom debugging base** in HBuilderX to use cloud certificates to create Android or iOS custom debugging base.
+
+### Step 5. Experience your first push
+
+Before testing the push, please make sure to turn on notifications and the status bar. Go to [Push Service Push > Access Test](https://console.trtc.io/chat/push-plugin-push-check) to send your first push.
+
+## Push Result Callback
+
+After enabling the push service, the push results can be forwarded to the App backend by configuring basic callbacks. For details, see:
+- [Normal push result callback](https://www.tencentcloud.com/document/product/1047/67553)
+
+- [All-member push result callback](https://www.tencentcloud.com/document/product/1047/60561)
+
+## Device Notification Bar Settings
+
+The intuitive representation of push is the notification bar reminder, so it is affected by the device notification settings just like other notifications. Taking Huawei as an example:
+- "Settings > Notifications > Lock screen notifications > Hide or not show notifications", will affect the display of push notifications when the screen is locked.
+
+- "Settings > Notifications > More notification settings > Show notification icons in the status bar", will affect the display of push notification icons in the status bar.
+
+- "Settings > Notifications > App notification management > Allow notifications", turning it on or off will directly affect the display of push notifications.
+
+- "Settings > Notifications > App notification management > Notification sounds" and "Settings > Notifications > App notification management > Silent notifications", will affect the sound effects of push notifications.
+
+## Vendor's push restrictions
+1. All vendors in China have adopted message classification mechanisms, and different push policies are assigned for different types of messages. To make the push timely and reliable, you need to set the push message type of your app as the system message or important message with a high priority based on the vendor's rules. Otherwise, push messages are affected by the vendor's message classification and may vary from your expectations.
+
+2. In addition, some vendors set limits on the daily volumes of app push messages. You can check such limits in the vendor's console. If push messages are not pushed timely or cannot be received occasionally, consider the following:
+
+【Huawei】
+
+Push messages are classified into service and communication messages and information marketing messages with different push effects and policies. In addition, the message classification is also related to the self-help message classification permission:
+- If there is no self-help message classification permission, the vendor will perform secondary intelligent message classification on push messages.
+
+- If you have applied for the self-help message classification permission, push messages will be classified based on the custom classification and then pushed. For more information, see [Vendor Description](https://developer.huawei.com/consumer/cn/doc/development/HMSCore-Guides/message-classification-0000001149358835).
+
+【vivo】
+
+Push messages are classified into system messages and operational messages with different push effects and policies. The system messages are further subject to the vendor's intelligent classification for correction. A message that cannot be intelligently identified as a system message will be automatically corrected as an operational message. If the judgment is incorrect, you can provide feedback by email. In addition, the total number of push messages is subject to a daily limit determined based on the app subscription statistics by the vendor. For more information, see [Vendor Description 1](https://dev.vivo.com.cn/documentCenter/doc/359) or [Vendor Description 2](https://dev.vivo.com.cn/documentCenter/doc/156).
+
+【OPPO】
+
+Push messages are categorized into private messages and public messages, each having different effects and strategies. Private messages target users with a certain level of attention who wish to receive information promptly, and access to the private messaging channel requires an application via email. The public messaging channel has a limited push volume. For more details, see [Vendor Description 1](https://open.oppomobile.com/wiki/doc#id=11227) or [Vendor Description 2](https://open.oppomobile.com/wiki/doc#id=11210).
+
+【Mi】
+
+Push messages are divided into urgent messages and regular messages, with different effects and strategies. The urgent message category is limited to instant communication messages, personal attention updates, personal reminders, changes in personal order status, personal financial alerts, personal status updates, personal resource changes, and personal device alerts, which can be requested on the vendor dashboard. The regular message category has a limited push volume. For more details, see [Vendor Description 1](https://dev.mi.com/console/doc/detail) or [Vendor Description 2](https://dev.mi.com/console/doc/detail).
+
+【Meizu】
+
+There is a limit to the number of messages that can be pushed. For more details, see [Vendor Description](http://open.res.flyme.cn/fileserver/upload/file/202201/85079f02ac0841da859c1da0ef351970.pdf).
+
+【FCM】
+
+There is a frequency limit for pushing upstream messages. For more details, see [Vendor Description](https://firebase.google.com/docs/cloud-messaging/scale-fcm#handling-retries).

package/resource/knowledge/push/integration/unity.md

@@ -0,0 +1,389 @@
+## Operation Steps
+
+### Step 1: Integrating the Message Push Plugin
+
+Adjust the `Packages/manifest.json` file and add relevant dependencies:
+``` json
+{
+  "dependencies": {
+    ...
+    "com.tencent.timpush.unity": "https://github.com/TencentCloud/TIMSDK.git#push_unity"
+  }
+}
+```
+
+### Step 2: Push Parameter Configuration
+
+【iOS】
+
+Upload the iOS APNs Push Certificate obtained from the manufacturer configuration process to the Chat console.
+
+The Chat console will allocate a certificate ID for you, as shown below:
+
+You need to create file `UnityIMPush.mm` under the directory `Assets/Plugins/iOS` (if the directory does not exist, create it manually), and implement the `- businessID` protocol method in the file to return the certificate ID. See the implementation as follows:
+``` objectivec
+#import "TPush/TPush.h"
+#import "UnityAppController.h"
+
+@interface UnityAppController (ThirdPartyExtension) <TIMPushDelegate>
+- (int)businessID;
+
+- (NSString *)applicationGroupID;
+@end
+
+@implementation UnityAppController (ThirdPartyExtension)
+
+#pragma mark - TIMPush
+- (int)businessID {
+    //Certificate ID from the previous step console, such as 1234567
+    int  kBusinessID = 1234567;
+    return kBusinessID;
+}
+
+- (NSString *)applicationGroupID {
+    //AppGroup ID
+    return kTIMPushAppGroupKey;
+}
+
+- (BOOL)onRemoteNotificationReceived:(NSString *)notice {
+    // custom navigate
+    return NO;
+}
+@end
+```
+
+【Android】
+
+After completing the console manufacturer push information, download and add the configuration file to the project. Add the downloaded `timpush-configs.json` file to the `Assets/Plugins/Android` directory of the project. If the directory does not exist, create it manually.
+
+### Step 3: Client Vendor Configuration
+
+【iOS】
+
+No need to perform this step on iOS.
+
+【Android】
+
+`File` > `Build Settings` > `Player Settings`, then go to `Publishing Settings` > `Build` in the Android platform settings and check the following three configurations:
+
+Find the `Assets/Plugins/Android/launcherTemplate.gradle` file, add the `dependencies` configuration at the end of the file, and as needed, introduce all or part of the manufacturer's push packages. Only by introducing the corresponding manufacturer's push package can you enable its native push capability.
+``` java
+dependencies {
+     // Version number "VERSION" please visit  to get configuration.
+     // Integration of the push main package is mandatory
+     implementation 'com.tencent.timpush:tpush:VERSION'
+     // other need packages
+     implementation 'androidx.appcompat:appcompat:1.3.0'
+     implementation 'com.google.code.gson:gson:2.10.1'
+     // Integrate FCM push package
+     implementation 'com.tencent.timpush:fcm:VERSION'
+     // If only the FCM channel is needed, the following packages do not need to be integrated; if you want to prioritize the FCM channel, call the API forceUseFCMPushChannel
+     implementation 'com.tencent.timpush:huawei:VERSION'
+     implementation 'com.tencent.timpush:xiaomi:VERSION'
+     implementation 'com.tencent.timpush:oppo:VERSION'
+     implementation 'com.tencent.timpush:vivo:VERSION'
+     implementation 'com.tencent.timpush:honor:VERSION'
+     implementation 'com.tencent.timpush:meizu:VERSION'
+}
+```
+- **Vivo and Honor adaptation**
+
+- According to the vivo and Honor vendor access guide, `APPID` and `APPKEY` need to be added to the manifest file, which can be done by modifying the `Assets/Plugins/Android/launcherTemplate.gradle` file.
+
+``` java
+// Assets/Plugins/Android/launcherTemplate.gradle
+
+android {
+    ...
+    defaultConfig {
+        ...
+        manifestPlaceholders = [
+            "VIVO_APPKEY" : "The cert APPKEY assigned to your app",
+            "VIVO_APPID" : "The cert APPID assigned to your app",
+            "HONOR_APPID" : "The cert APPID assigned to your app"
+        ]
+    }
+}
+```
+- **Huawei, Honor, and Google FCM adaptation**
+
+Integrate the plugin and json configuration file by vendor method.
+
+> **Note:**
+>
+
+> The following Honor adaptation requires configuration for version 7.7.5283 and above.
+>
+
+  1. Download the configuration file and add it to the project root directory `Assets/Plugins/Android/JsonConfigs`. `Create the directory manually if it does not exist`.
+
+【Huawei】
+
+【Honor】
+
+【Google FCM】
+
+【Operation Path】
+
+  2. In the `Assets/Plugins/Android/baseProjectTemplate.gradle` file, add the following configurations under `buildscript` -> `dependencies` (if it is necessary to add a new `buildscript`, place it at the top of the file):
+
+【Gradle 7.1 and above Versions】
+
+In the `Assets/Plugins/Android/baseProjectTemplate.gradle` file, add the following configurations under `buildscript` -> `dependencies`:
+``` java
+buildscript {
+    dependencies {
+        ...
+        classpath 'com.huawei.agconnect:agcp:1.6.0.300'
+        classpath 'com.hihonor.mcs:asplugin:2.0.1.300'
+        classpath 'com.google.gms:google-services:4.3.15'
+    }
+}
+```
+
+ In the `Assets/Plugins/Android/settingsTemplate.gradle` file, add the following repository configurations under buildscript -> repositories and allprojects -> repositories:
+``` java
+pluginManagement {
+    repositories {
+        gradlePluginPortal()
+        mavenCentral()
+        maven { url "https://mirrors.tencent.com/nexus/repository/maven-public/" }
+        // Configure the Maven repository address for HMS Core SDK.
+        maven {url 'https://developer.huawei.com/repo/'}
+        maven {url 'https://developer.hihonor.com/repo'}
+    }
+}
+dependencyResolutionManagement {
+    ...
+    repositories {
+        mavenCentral()
+        maven { url "https://mirrors.tencent.com/nexus/repository/maven-public/" }
+        // Configure the Maven repository address for HMS Core SDK.
+        maven {url 'https://developer.huawei.com/repo/'}
+        maven {url 'https://developer.hihonor.com/repo'}
+    }
+    }
+}
+```
+
+【Gradle 7.0 Version】
+
+In the `Assets/Plugins/Android/baseProjectTemplate.gradle` file, add the following configurations under `buildscript`:
+``` java
+buildscript {
+    repositories {
+        mavenCentral()
+        maven { url "https://mirrors.tencent.com/nexus/repository/maven-public/" }
+        // Configure the Maven repository address for HMS Core SDK.
+        maven {url 'https://developer.huawei.com/repo/'}
+        maven {url 'https://developer.hihonor.com/repo'}
+    }
+    dependencies {
+        ...
+        classpath 'com.google.gms:google-services:4.2.0'
+        classpath 'com.huawei.agconnect:agcp:1.4.1.300'
+        classpath 'com.hihonor.mcs:asplugin:2.0.1.300'
+    }
+}
+```
+
+ In the `Assets/Plugins/Android/settingsTemplate.gradle` file, add the following repository configurations under `allprojects` -> `repositories`:
+``` plaintext
+allprojects {
+    ...
+    repositories {
+        mavenCentral()
+        maven { url "https://mirrors.tencent.com/nexus/repository/maven-public/" }
+        // Configure the Maven repository address for HMS Core SDK.
+        maven {url 'https://developer.huawei.com/repo/'}
+        maven {url 'https://developer.hihonor.com/repo'}
+    }
+}
+```
+
+【Gradle 7.0 and below Versions】
+
+In the project level build.gradle file, add the following configurations under `buildscript` and `allprojects`:
+``` java
+buildscript {
+    repositories {
+        mavenCentral()
+        maven { url "https://mirrors.tencent.com/nexus/repository/maven-public/" }
+        // Configure the Maven repository address for HMS Core SDK.
+        maven {url 'https://developer.huawei.com/repo/'}
+        maven {url 'https://developer.hihonor.com/repo'}
+    }
+    dependencies {
+        ...
+        classpath 'com.google.gms:google-services:4.2.0'
+        classpath 'com.huawei.agconnect:agcp:1.4.1.300'
+        classpath 'com.hihonor.mcs:asplugin:2.0.1.300'
+    }
+}
+
+allprojects {
+    repositories {
+        mavenCentral()
+        maven { url "https://mirrors.tencent.com/nexus/repository/maven-public/" }
+        // Configure the Maven repository address for HMS Core SDK.
+        maven {url 'https://developer.huawei.com/repo/'}
+        maven {url 'https://developer.hihonor.com/repo'}
+    }
+}
+```
+
+  3. In the `Assets/Plugins/Android/launcherTemplate.gradle` file, add the following configurations:
+
+``` java
+apply plugin: 'com.google.gms.google-services'
+apply plugin: 'com.huawei.agconnect'
+apply plugin: 'com.hihonor.mcs.asplugin'
+```
+
+### Step 5: Handling Message Click Callback and Parsing Parameters
+
+If you need to customize the parsing of received remote push, you can implement it by the following method.
+
+> **Note:**
+>
+> 1. Register the callback timing in the program entry function.
+> 2. Configure the console to click subsequent actions with the following configuration, select **open specified in-app page,** do not modify and use default values.
+
+``` csharp
+PushListener listener = new PushListener(onRecvPushMessage: (message) => {
+  Debug.Log($"Received push message: Title:{message.title}, Content:{message.desc}, Passthrough content:{message.ext}, Message ID:{message.messageID}");
+}, onRevokePushMessage: (messageID) => {
+  Debug.Log($"Revoke push message ID: {messageID}");
+}, onNotificationClicked: (ext) => {
+  Debug.Log($"Click to push message: {ext}");
+});
+
+PushManager.AddPushListener(listener);
+```
+
+### Step 6: Registering the Push Plugin
+
+Upon success of calling the `PushManager.RegisterPush` method, you can receive offline push notifications.
+
+> **Note:**
+>
+
+> Note: If you have already integrated the Chat product and call this API after successful log-in, set the appKey parameter to null. Otherwise, the Chat account will be taken offline.
+>
+
+``` java
+PushManager.RegisterPush(sdkAppId: your sdkAppId, appKey: "client key", new PushCallback(onSuccess: (data) => {
+  Debug.Log($"Push registration successful: {data}");
+}, onError: (errCode, errMsg, data) => {
+  Debug.Log($"Push registration failed: error code:{errCode}, error info:{errMsg}");
+}));
+```
+
+### Step 7: Message Push Delivery Statistics
+
+If you need statistics for reach data, complete the configuration as follows:
+
+【Huawei】
+
+Receipt Address:
+
+Singapore : https://apisgp.im.qcloud.com/v3/offline_push_report/huawei
+
+Korea: https://apikr.im.qcloud.com/v3/offline_push_report/huawei
+
+USA: https://apiusa.im.qcloud.com/v3/offline_push_report/huawei
+
+Germany: https://apiger.im.qcloud.com/v3/offline_push_report/huawei
+
+Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/huawei
+
+China: https://api.im.qcloud.com/v3/offline_push_report/huawei
+
+> **Note:**
+>
+
+> Note: Huawei Push certificate ID <= 11344 uses Huawei Push v2 version interface with no support for reachability and Receipt Click. Please regenerate the certificate ID.
+>
+
+【Honor】
+
+Receipt Address:
+
+Singapore : https://apisgp.im.qcloud.com/v3/offline_push_report/honor
+
+Korea: https://apikr.im.qcloud.com/v3/offline_push_report/honor
+
+USA: https://apiusa.im.qcloud.com/v3/offline_push_report/honor
+
+Germany: https://apiger.im.qcloud.com/v3/offline_push_report/honor
+
+Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/honor
+
+China: https://api.im.qcloud.com/v3/offline_push_report/honor
+
+【vivo】
+| Callback Address Configuration | Receipt ID Configuration Chat Console |
+| --- | --- |
+| Receipt Address:<br>Singapore :https://apisgp.im.qcloud.com/v3/offline_push_report/vivo<br>Korea:<br>https://apikr.im.qcloud.com/v3/offline_push_report/vivo<br>USA: https://apiusa.im.qcloud.com/v3/offline_push_report/vivo<br>Germany: https://apiger.im.qcloud.com/v3/offline_push_report/vivo<br>Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/vivo<br>China:<br>https://api.im.qcloud.com/v3/offline_push_report/vivo |  |
+
+【Meizu】
+| Enable Receipt Switch | Configure Receipt Address |
+| --- | --- |
+|  |  |
+
+Receipt Address:
+
+Singapore : https://apisgp.im.qcloud.com/v3/offline_push_report/meizu
+
+Korea: https://apikr.im.qcloud.com/v3/offline_push_report/meizu
+
+USA: https://apiusa.im.qcloud.com/v3/offline_push_report/meizu
+
+Germany: https://apiger.im.qcloud.com/v3/offline_push_report/meizu
+
+Indonesia: https://apiidn.im.qcloud.com/v3/offline_push_report/meizu
+
+China: https://api.im.qcloud.com/v3/offline_push_report/meizu
+
+> **Note:**
+>
+
+> Note: After enabling the receipt switch, please ensure the receipt address is configured correctly. Without configuring or with an incorrect address, it will impact the push notification feature.
+>
+
+【iOS】
+
+iOS Push Notification Reach Statistics Configuration, see:
+  - If you need to track push notification reach and click data, you need to implement the `- applicationGroupID` method in the AppDelegate.m file. For reference, see the Push Parameter Configuration section, which returns the App Group ID (for generation method, see Manufacturer Configuration - Generate App GroupID).
+
+  - Call the push arrival rate statistics function in the [Notification Service Extension](https://github.com/TencentCloud/TIMSDK/blob/master/iOS/Demo/pushservice/NotificationService.m)'s `-didReceiveNotificationRequest:withContentHandler:` method.
+
+``` java
+@implementation NotificationService
+
+- (void)didReceiveNotificationRequest:(UNNotificationRequest *)request withContentHandler:(void (^)(UNNotificationContent * _Nonnull))contentHandler {
+    //appGroup indicates the App Group shared between the main APP and Extension. The App Groups capability needs to be configured in the main APP's Capability.
+    //format is group + [main bundleID] + key
+    //for example group.com.tencent.im.pushkey
+    NSString * appGroupID = kTIMPushAppGroupKey;
+    __weak typeof(self) weakSelf = self;
+    [TIMPushManager handleNotificationServiceRequest:request appGroupID:appGroupID callback:^(UNNotificationContent *content) {
+        weakSelf.bestAttemptContent = [content mutableCopy];
+        // Modify the notification content here...
+        // self.bestAttemptContent.title = [NSString stringWithFormat:@"%@ [modified]", self.bestAttemptContent.title];
+        weakSelf.contentHandler(weakSelf.bestAttemptContent);
+    }];
+}
+
+@end
+```
+
+> **Note:**
+>
+> 1. Report push reach data. The mutable-content switch requires enabling to support the iOS 10 Extension function.
+
+> 2. Data details can be viewed on the push data page. The push data page is only available after [purchasing the push plugin](https://console.cloud.tencent.com/im/plugin/TIMPush).
+
+The rest support manufacturers with no need to configure. FCM does not currently support the push notification statistics feature.
+
+Congratulations on completing the access of the push plugin. Please note: **After the trial or purchase expiry of the push plugin, it will automatically stop providing push service (including regular message offline push, all users/tag push, etc.)**. To avoid affecting your normal business operation, please advise in advance to [purchase](https://www.tencentcloud.com/account/login)/[renew](https://www.tencentcloud.com/account/login).