AEP SDK: How to change PushPlatform default value GCM ? | Community
Skip to main content
robayzma
robayzma
Level 3
December 19, 2019
Solved

AEP SDK: How to change PushPlatform default value GCM ?

  • December 19, 2019
  • 1 reply
  • 4365 views

I am using the AEP SDK and noticing that the payload on startup is set to GCM.

The log entry in Android Studio looks like this:

D/AdobeExperienceSDK: CampaignExtension - processRequest - Campaign Request Queued with url (https://*******-sandbox.adobe.com/rest/head/mobileAppV5/@YbyiVrJB5VoiREkHe_JyohyYvxOREuJjngnWTaKlelvapqcTcnlbk4POgDOUoTLnzkRMQ4Sm6uFh_EIEcdSylkc7eKZXJdHS5jce6WULYr7U6lCyWDfis50xtplhd6mq5mhWbA/subscriptions/84468840125982782508671000597616434081) and body ({"marketingCloudId":"84468840125982782508671000597616434081","pushPlatform":"gcm"})

 

Can it be changed to another variant like iOS or FCM? And how to do that?

 

Cheers

Robert

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 Swarna_S-Adobe

@robayzma The payload containing the push platform information is currently sent from within the SDK as part of Campaign registration call based on the platform (android - `gcm` or `fcm` and iOS - `apns`). You should be able to update the value using a launch postback rule but we do not recommend it. What exactly is your use case for trying to update the push platform value later?

1 reply

S
Adobe Employee
Swarna_S-AdobeAdobe EmployeeAccepted solution
Adobe Employee
December 19, 2019

@robayzma The payload containing the push platform information is currently sent from within the SDK as part of Campaign registration call based on the platform (android - `gcm` or `fcm` and iOS - `apns`). You should be able to update the value using a launch postback rule but we do not recommend it. What exactly is your use case for trying to update the push platform value later?

    robayzma
    robayzmaAuthor
    Level 3
    January 3, 2020
    @swarna_s-adobe Yes I assumed as much that 'gcm' was there because of a legacy reason and that is why it should be an optional setting or configurable parameter that could be set in the SDK, especially since we can confirm it is obsolete as per the statement from Google. I will write to Customer Care or in this case Neolane Support and create a ticket for the behaviour I see in Campaign. Thanks for confirming.
    Terms & ConditionsAccessibility statement

    Loading footer...