setPushIdentifier not working on app launch Adobe Campaign Standard

Avatar

Avatar
Level 1
Rev_J
Level 1

Likes

0 likes

Total Posts

11 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
Rev_J
Level 1

Likes

0 likes

Total Posts

11 posts

Correct reply

0 solutions
View profile
Rev_J
Level 1

16-12-2020

We're experiencing the same issue on both iOS and Android, namely that on app launch we use the exact code documented here to register push token: https://experienceleague.adobe.com/docs/campaign-standard/using/administrating/configuring-mobile/su...

The issue is that we can see the token is available in the app through debugging, and we can even use collectPII to send that token to a test field in ACS and this works fine, however the setPushIdentifier function doesn't populate the field in the Registration Token in Adobe Campaign Standard.

If we kill the application and relaunch it then the registration token is correctly sent.

It appears that there is some delay in the SDK registering the token and making available for all SDK functions.

View Entire Topic

Avatar

Avatar
Boost 5
Employee
Ryan_Morales
Employee

Likes

7 likes

Total Posts

24 posts

Correct reply

8 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile

Avatar
Boost 5
Employee
Ryan_Morales
Employee

Likes

7 likes

Total Posts

24 posts

Correct reply

8 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Affirm 5
Affirm 3
View profile
Ryan_Morales
Employee

16-12-2020

Hi @Rev_J ,

 

Invoking the setPushIdentifier API will send the push token to the Adobe Visitor ID service which then forwards the token to your ACS instance. It is possible that there is an issue in the backend which is why sending the push token with collectPii is able to populate the app subscriber table while the setPushIdentifier call isn't able to. We do have some troubleshooting steps available at https://aep-sdks.gitbook.io/docs/resources/troubleshooting-guides/push_notification_troubleshooting. Could you take look and see if it helps resolve your issue? If that doesn't help, I think the next step to take would be to open a customer care ticket so the appropriate team could investigate the issue.

 

Thanks,

Ryan Morales

Mobile Engineer
Adobe Experience Cloud

 
Rev_J

Thanks Ryan.

We have different app development team working on multiple apps and they are all experiencing the same issues across iOS and Android. Thanks for confirming the intended behaviour. I will post a link to that guide to them. I've already contact customer care.

One other question - customer care asked us to confirm the ACS server URL in the app code, I think that this is inherited from the Launch property, right? Is there something that need to be coded in the app to state the ACS server? I can't see anything in the documentation.

Rev_J

Is there any way our app developers can get onto Project Griffon without a 48 hour delay? That pretty much wipes out the rest of this week.

Rev_J
Can you confirm how the Adobe Visitor ID service understands the instance of ACS to forward the registration to? We're currently working in the stage instance.
Ryan_Morales
I will check and see if there is a way to get onto Project Griffon / Assurance without the delay. I had another question regarding your ACS instance. Do you see app subscribers being added to the app subscriber table? Or are those missing as well?
Ryan_Morales
The Visitor ID Service (now known as Experience Cloud ID Service) has a pipeline that sends the Org Id, Experience Cloud ID (ECID), and push token from the setPushIdentifier call to your ACS instance. Your ACS instance should be setup to ingest any push token associated with the instance Org Id.
Ryan_Morales
Could you email me your Org ID? My email is rymorale@adobe.com. Thanks!