FCM Channel Integration

Discontinuing Push Notification Service TPNS

Announcements

Features

SDK for Android

SDK for iOS

SDK for macOS

Release Notes

Overview

Strengths

Use Cases

Global Deployment

Product Introduction

Billing Overview

Purchase Directions

Billing Modes

Free Trial

Payment Overdue

Purchase Guide

Creating Products and Applications

Quick Integration with Android

Quick Integration with iOS

Creating a Push Task

Querying Push Records

Guidelines for Push Testing Methods

Product Restrictions

Getting Started

Troubleshooting Tool

Conversion Funnel

Push Plan

Push Settings

Message Recall

Push Management

Multi-Package Name Push

Notification Tap-to-Redirect

Custom Push Speed

Channel Policies

Message Collapse

Rich Media Notification

Custom Notification

Push to Accounts

Advanced Push Features

Operation Guide 

iOS Badge Feature Practice

Practical Tutorial

API Overview

Signature Authentication (Recommended)

Basic Auth Authentication

Request Structure

Call Method

Push API

Creating a Push Plan

Account Package Upload API

Token Package Upload API

Push APIs

Tag Binding and Unbinding

Deleting All Devices Under Tag

Tag APIs

Account Binding and Unbinding

Account and Device Binding Query

Account APIs

Querying Daily Aggregated Push Statistics

Querying Device Statistics

Querying All Push Information in Specific Period

Querying Push Information for One Task

Querying Push Statistics for a Single Task

Querying Aggregated Statistics for Multiple Tasks

Querying All Push Tasks on the Day by Token

Statistics APIs

User Attribute APIs

Server-Side Error Codes

Server SDKs

API (Java)

API Documentation

SDK Integration

Vendor Channel Integration Guide

Vendor Channels

Android SDK FAQs

Compatibility with Android P

Error Codes

Android Integration Guide

Acquisition of Push Certificate

Push Environment Selection Description

Extension Feature

iOS SDK FAQs

iOS Integration Guide

Client Integration Plugin

Push Certificate Description

macOS Integration Guide

SDK Documentation

Quick Configuration

Advanced Custom Configuration

Resource Tag

Users and Permissions

Service Level Agreement

Service Agreement

Android

Flutter

Others

FAQs

Privacy Policy

Data Processing and Security Agreement

Developer Agreement

Tencent Push Notification Service Policy

Contact Us

Glossary

Tencent Push Notification Service

The FCM channel is a system-level push channel provided by Google. On mobile phones with the Google service framework, as the background processes are managed loosely, push notifications can be received if application processes are not force stopped. This channel is not supported for clusters in the Chinese mainland.

FCM PUSH supports the following two methods of key configuration. You just need to choose one of them, but the new proposal method using the server private key is recommended.

Server private key (recommended)
Register the application at the 

https://firebase.google.com/?hl=zh-cn

 to get the json file containing the Firebase server private key. Then, go to the 

Tencent Push Notification Service console

https://console.tencentcloud.com/tpns

, select Server Private Key (Recommended), and click 

 to upload the above-mentioned json file.


Legacy server key
Register the application at the 

 of the FCM app push, and enter the key in the 

Configure gradle to integrate the Google service.

Add the following code to the dependencies node in the project-level 

classpath 'com.google.gms:google-services:4.2.0'

FCM Register error! java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.qq.xg4all. Make sure to call FirebaseApp.initializeApp(Context) first.

appears for a version earlier than 4.2.0, add 

        implementation 'com.tencent.tpns:fcm:[VERSION]-release' // For FCM PUSH, [VERSION] is the version number of the current SDK and can be obtained from "SDK for Android".

 implementation  'com.google.firebase:firebase-messaging:17.6.0'

// In the app-level gradle file, add the following to the last line of the code and put google-services.json under the root directory of your app model

apply plugin: 'com.google.gms.google-services'

For FCM PUSH, [VERSION] is the version number of the current SDK and can be obtained from the 

Configure google-play-services for Google (v17.0.0+ or later recommended; an earlier version may cause FCM registration failure).

Add the following code before calling the Tencent Push Notification Service registration code 

XGPushConfig.enableOtherPush(this, true);

The log of successful FCM registration is as follows:

V/TPush: [XGPushConfig] isUsedOtherPush:true

I/TPush: [OtherPush] checkDevice pushClassNamecom.tencent.android.tpush.otherpush.fcm.impl.OtherPushImpl

I/TPush: [XGPushManager] other push token is : dSJA5n4fSZ27YeDf2rFg1A:APA91bGiqSPCMZTuyup**********f1fBIahZKYkth2OoDpixDPQmEZkQ11fX06mw_1kEaW5-jFmT4YwlER4qfX66h_BIoUxOyj_tKqZSUg7oHigIKaOrDWmMQfMAqGoT8qSfg  other push type: fcm

 Obfuscation rules must be stored in the 

Why can't messages pushed through the FCM channel be received?

On mobile phones with the Google service framework outside the Chinese mainland, as the background processes are managed loosely, messages pushed through the FCM channel can be received if application processes are not force stopped.

The background process management policies of phone brands in the Chinese mainland are generally strict, which also restrict the Google services on the background. On such phones, messages pushed through the FCM channel cannot be sent or received. To receive them, keep the app running on the foreground.

How do I force stop an application process?

 on the phone, select a specific application, and click 

, or a similar button to stop the application. For most Chinese phones, closing the application process on the multitasking page can also be considered as force stopping the application process (this is not the case for phones outside the Chinese mainland).

tencent cloud