۶Ƶ

Documentation

Android push deliveries are stuck in “Sent to the service provider” status

Last update: Thu Nov 07 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

This article addresses the issue in ۶Ƶ Campaign Classic v7 where Android push deliveries get stuck in Sent to the service provider status, preventing push notifications from being received on the mobile application.

Description description

Environment

۶Ƶ Campaign Classic v7

Issue/Symptoms

Android push deliveries have the broad log stuck in Sent to the service provider status, preventing push notifications from being received on the mobile application.

For example:

16/09/2024 13:23:19 Sent to the service provider Not defined Message to '*' pushed to the connector.

Steps to reproduce:

  1. Send an Android push notification delivery.
  2. Check the status of the broad log > push notifications are stuck in Sent to the service provider status and you are not getting any Android push notification on the mobile application that you selected.
  3. In the text field, you can see Message to ‘*’ pushed to the connector.

Resolution resolution

This type of situation may arise if you have not fully migrated to FCM HTTPv1.

Three conditions must be met for an Android push notification delivery to be sent:

  1. The ۶Ƶ Campaign marketing instance’s Android mobile application must use API version HTTP v1 and have the correct details added for the Android application.
    You can use the below documentation to ensure that your Android mobile application is using HTTP v1 correctly:
    Push Notification Channel changes

  2. The latest androidPushConnectorV2.js (nms) Javascript connector in the Android Routing external account is used to send the delivery.

    NOTE: In case, you are using a custom Android push connector, ensure that you merge your changes with the latest OOTB androidPushConnectorV2.js (nms) Javascript connector.

  3. The Android delivery template that you are using in your Android push notification delivery has the correct androidCheckParamsas below:

    code language-none 
    <androidCheckParams>
      <source><!--[ CDATA[ <% if( appSubscription.mobileApp.label!='' &&
     appSubscription.mobileApp.img!='' &&
     appSubscription.mobileApp.fcmProtocol!='' &&((
     appSubscription.mobileApp.senderId!='' &&
     appSubscription.mobileApp.password!='' ) || (
     appSubscription.mobileApp.fcmProjectId!='' &&
     appSubscription.mobileApp.fcmPrivateKey!='' &&
     appSubscription.mobileApp.fcmClientEmail!='' ) ) &&
     String(message.delivery.idTracking)!='' &&
     String(message.delivery.idMarketing)!='' ) { %--> 'OK' <% } else { %> 'Error' <% } %>] ] ></source>
</androidCheckParams>

In order to confirm that the push notifications are sent using HTTPv1, make sure that the text in the broad log is the following:

HTTPv1 SUCCESS 200: message to '*' has been transmitted to FCM

For a more detailed explanation, please follow the below link:

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f