![]() | iPhone 13 ![]() | Samsung Galaxy A23 Overseas Version (Google FCM Push) ![]() |



manifestPlaceholders.json and mcs-services.json.nativeResources directory. If this folder is not yet created in the project root directory, please create a new folder named nativeResources.nativeResources directory exists in the project opened with HBuilderX and is at the same level as the uni_modules directory.nativeResources/android/assets.timpush-configs.json (download from Push Service > Access Settings > One-click Quick Configuration) to the nativeResources/android/assets/ directory. As shown in the figure:

com.google.gms.google-services to uni_modules/TencentCloud-Push/utssdk/app-android/config.json in project.plugins, as shown below:"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"]}

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:
agconnect-services.json (for details on obtaining this file, see Vendor Configuration > uniapp > Huawei > Step 4: Obtain Application Information) to the nativeResources/android/assets/ directory. As shown in the figure:
uni_modules/TencentCloud-Push/utssdk/app-android/config.json in dependencies, add "com.tencent.timpush:honor:8.3.6498".{..."dependencies": [..."com.tencent.timpush:honor:8.3.6498"]}
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).
appID to nativeResources/android/manifestPlaceholders.json in "HONOR_APPID".
{"HONOR_APPID": ""}
uni_modules/TencentCloud-Push/utssdk/app-android/config.json in dependencies, add "com.tencent.timpush:vivo:8.3.6498".{..."dependencies": [..."com.tencent.timpush:vivo:8.3.6498"]}
appID and appKey to nativeResources/android/manifestPlaceholders.json in VIVO_APPKEY and VIVO_APPID.
{"VIVO_APPKEY": "","VIVO_APPID": "",}
nativeResources/ios/Resources.timpush-configs.json file in nativeResources/ios/Resources.timpush-configs.json file. As shown below:{"businessID":"xxx"}

SDKAppID and appKey with the application information obtained from Chat Console - Push Service - Access Settings page. As shown in the figure:
// Integration of TencentCloud-Pushimport * as Push from '@/uni_modules/TencentCloud-Push';const SDKAppID = 0; // Your SDKAppIDconst 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 informationPush.addPushListener(Push.EVENT.NOTIFICATION_CLICKED, (res) => {// res is the push extension informationconsole.log('notification clicked', res);});// Listen for online pushPush.addPushListener(Push.EVENT.MESSAGE_RECEIVED, (res) => {// res is the message contentconsole.log('message received', res);});// Listen for online push recallPush.addPushListener(Push.EVENT.MESSAGE_REVOKED, (res) => {// res is the ID of the recalled messageconsole.log('message revoked', res);});





masukan