Send Test Push from Assurance not delivering Push on Android

[MA9541]

We are implementing AJO on mobile app. While testing the push functionality via Assurance we are not seeing push getting delivered on Android. Works fine on iOS. There are no errors and the Test Results panel is all green.

Any pointers why this is happening? 

[ranjithd]

If push notifications are not getting delivered on Android while testing with Assurance, but they are working fine on iOS, there could be a few different reasons for this. Here are a few possible causes and solutions:

1. Check your Android device settings: Ensure that your Android device has push notifications enabled and that the app is allowed to receive notifications. Also, check if the device is connected to the internet and has a strong network signal.

2. Check your push notification settings: Double-check that the push notification settings for Android are configured correctly in your AJO implementation. Specifically, make sure that the Android-specific settings such as the Firebase Server Key and Firebase Sender ID are properly configured.

3. Check your Assurance (Griffon) configuration: Ensure that your Assurance (Griffon) configuration is set up properly for Android devices. Double-check that the correct device tokens and other relevant details are being sent in the push notification request.

4. Check for any errors or warnings: Review the logs and console output in the Assurance (Griffon) tool for any errors or warnings that may be related to the Android push notifications.

5. Check for any issues with the mobile app: It's possible that there may be issues with the mobile app that are preventing the Android push notifications from being delivered. Check for any issues with the app's network connection, device compatibility, or other factors that may be affecting push notifications.

If none of the above solutions resolve the issue, you may want to reach out to Adobe's technical support for further assistance.

[MA9541 · Accepted solution]

Thanks @ranjithd for your inputs. We figured out that Assurance uses Data key instead of Notification key in the message payload and this needs some changes in the SDK to parse and display the notification. We were able to set a breakpoint and capture the incoming message. So push functionality seems to be working fine.

Pasting the firebase link which might be useful for others.

https://firebase.google.com/docs/cloud-messaging/concept-options

[MRIniesta]

Hi Ranjithd, 

What do you mean with ''make sure that the Android-specific settings such as the Firebase Server Key and Firebase Sender ID are properly configured.'' ? The JSON that has to be uploaded to App surfaces or something specific to Firebase?

We have an erorr displayed in Assurance, specifically in the step: send to push provider

The json that we upload to App Surfaces has the next variables, its correct? 

{

  "type": "service_account",

  "project_id": "xx",

  "private_key_id": "xx",

  "private_key": "-----BEGIN PRIVATE KEY----------END PRIVATE KEY-----\n",

  "client_email": xx,

  "client_id": "xx",

  "auth_uri": https://accounts.google.com/o/oauth2/auth,

  "token_uri": https://oauth2.googleapis.com/token,

  "auth_provider_x509_cert_url": https://www.googleapis.com/oauth2/v1/certs,

  "client_x509_cert_url": xx,

}

xx = personal/enterprise information

Thanks