Push notifications "open" not working - Does not redirect where it should | Community
Skip to main content
CampaignerForLife
New Participant
February 21, 2024
Solved

Push notifications "open" not working - Does not redirect where it should

  • February 21, 2024
  • 1 reply
  • 706 views

Hello, i'm having troubles with the "Open" command in Push Notifications. 

 

When I send the notification, it appears but the "Open" command is not working - It does not redirect to where it should. 

 

What am I missing? How should I format the open parameter for it to work? i'm trying with openOp/url and openURL/url. Any insight?? 

 

@_manoj_kumar_ @parthasarathy @parvesh_parmar @davidkangni

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by _Manoj_Kumar_

Hello @campaignerforlife 

 

Could you please share how the deep link is configured in the APP? Are you using OOTB click action or using application variables for deep-linking?

 

If you are using the application variables for deeplink then the mobile developer will have to capture all those variables by OnMessageReceived function.

 

Here is an example:

 

public void onMessageReceived(RemoteMessage remoteMessage) { Log.d(LOG_TAG, "From: " + remoteMessage.getFrom()); if (AEPMessagingService.handleRemoteMessage(this, remoteMessage)) { // Campaign extension has handled the notification } else { // Handle notification from other sources } }

 

 

In this function, the app can check for click_action (in case of OOTB click action) or any other variable in case of application variables.

 

Mobile App will have to take this action of redirection or opening a URL. AEP Mobile SDK won't do this out of the box.

 

 

1 reply

_Manoj_Kumar_
_Manoj_Kumar_Accepted solution
New Participant
February 22, 2024

Hello @campaignerforlife 

 

Could you please share how the deep link is configured in the APP? Are you using OOTB click action or using application variables for deep-linking?

 

If you are using the application variables for deeplink then the mobile developer will have to capture all those variables by OnMessageReceived function.

 

Here is an example:

 

public void onMessageReceived(RemoteMessage remoteMessage) { Log.d(LOG_TAG, "From: " + remoteMessage.getFrom()); if (AEPMessagingService.handleRemoteMessage(this, remoteMessage)) { // Campaign extension has handled the notification } else { // Handle notification from other sources } }

 

 

In this function, the app can check for click_action (in case of OOTB click action) or any other variable in case of application variables.

 

Mobile App will have to take this action of redirection or opening a URL. AEP Mobile SDK won't do this out of the box.

 

 

     Manoj     Find me on LinkedIn
CampaignerForLife
New Participant
February 22, 2024

How would it be with OOTB click action? 

 

Thank you!!

_Manoj_Kumar_
New Participant
February 23, 2024

Hello @campaignerforlife 

Even for OOTB Click function, it is apps responsibility to redirect the customer to a specific page. AEP Mobile SDK won't do this automatically. 

     Manoj     Find me on LinkedIn