All Products
Search
Document Center

Mobile Platform as a Service:OPPO push notification failures

Last Updated:Jan 29, 2026

If OPPO push notifications fail, follow these steps to troubleshoot the issue:

  1. Ensure that you have successfully integrated OPPO Push by following the instructions in Integrate OPPO Push. The integration involves these steps:

    1. Download and import the OPPO Push SDK library.

    2. Add the Push - OPPO component.

    3. Configure the AndroidManifest.xml file.

    4. Integrate MpaaSNcActivity.

      Note
  2. Verify that the SDK version for the imported mcssdk-2.xx.jar file is correct.

    • If the mPaaS baseline is 10.1.68.29 or later, OPPO Push SDK V2.1.0 (mcssdk-2.1.0.jar) is supported.

    • If the mPaaS baseline is earlier than 10.1.68.29, only OPPO Push SDK V2.0.2 (mcssdk-2.0.2.jar) is supported.

  3. Verify that the service is configured correctly in the AndroidManifest.xml configuration file. Different SDK versions require different service classes.

    • For OPPO Push SDK V2.0.2 (mPaaS baseline earlier than 10.1.68.29), the required service classes are com.heytap.mcssdk.PushService and com.heytap.mcssdk.AppPushService. The configuration is as follows:

      <uses-permission android:name="com.coloros.mcs.permission.RECIEVE_MCS_MESSAGE" />
      <uses-permission android:name="com.heytap.mcs.permission.RECIEVE_MCS_MESSAGE"/>
      <application>
      <!-- Add Service for V2.0.2 START-->
      <service
         android:name="com.heytap.mcssdk.PushService"
         android:permission="com.coloros.mcs.permission.SEND_MCS_MESSAGE"
         android:process=":push">
         <intent-filter>
             <action android:name="com.coloros.mcs.action.RECEIVE_MCS_MESSAGE"/>
         </intent-filter>
      </service>
      <service
         android:name="com.heytap.mcssdk.AppPushService"
         android:permission="com.heytap.mcs.permission.SEND_MCS_MESSAGE"
         android:process=":push">
         <intent-filter>
             <action android:name="com.heytap.mcs.action.RECEIVE_MCS_MESSAGE"/>
         </intent-filter>
      </service>
      <!-- Add Service for V2.0.2 END-->
      <meta-data
         android:name="com.oppo.push.app_key"
         android:value="Get from OPPO Open Platform"
         />
      <meta-data
         android:name="com.oppo.push.app_secret"
         android:value="Get from OPPO Open Platform"
         />
      </application>
    • For OPPO Push SDK V2.1.0 (mPaaS baseline 10.1.68.29 or later), the required service classes are com.heytap.msp.push.service.CompatibleDataMessageCallbackService and com.heytap.msp.push.service.DataMessageCallbackService. The configuration is as follows:

      <uses-permission android:name="com.coloros.mcs.permission.RECIEVE_MCS_MESSAGE" />
      <uses-permission android:name="com.heytap.mcs.permission.RECIEVE_MCS_MESSAGE"/>
      <application>
      <!-- Add Service for V2.1.0 START-->
      <service
         android:name="com.heytap.msp.push.service.CompatibleDataMessageCallbackService"
         android:permission="com.coloros.mcs.permission.SEND_MCS_MESSAGE"
         android:process=":push">
         <intent-filter>
             <action android:name="com.coloros.mcs.action.RECEIVE_MCS_MESSAGE"/>
         </intent-filter>
      </service>
      <service
         android:name="com.heytap.msp.push.service.DataMessageCallbackService"
         android:permission="com.heytap.mcs.permission.SEND_PUSH_MESSAGE"
         android:process=":push">
         <intent-filter>
             <action android:name="com.heytap.mcs.action.RECEIVE_MCS_MESSAGE"/>
             <action android:name="com.heytap.msp.push.RECEIVE_MCS_MESSAGE"/>
         </intent-filter>
      </service>
      <!-- Add Service for V2.1.0 END-->
      <meta-data
         android:name="com.oppo.push.app_key"
         android:value="Get from OPPO Open Platform"
         />
      <meta-data
         android:name="com.oppo.push.app_secret"
         android:value="Get from OPPO Open Platform"
         />
      </application>