since ‎20-11-2020
Jan 15, 2021
Rev_J
Level 1
Re: setPushIdentifier not working on app launch Adobe Cam...
Avatar

Rev_J

Rev_J
- Adobe Experience Platform SDKs
UPDATE - we've been working through this with Adobe support but it still isn't resolved.

Views

20

Likes

0

Replies

0
IAB TCF 2.0 Vendor? AEP Mobile SDK as well as AEP Web SDK?
Avatar

Rev_J

Rev_J
- Adobe Experience Platform
Adobe Experience Platform Web SDK supports the Interactive Advertising Bureau Transparency & Consent Framework, version 2.0 (IAB TCF 2.0) as described here: https://experienceleague.adobe.com/docs/experience-platform/edge/consent/iab-tcf/with-launch.html?lang=en#consentHowever, it's unclear if the AEP Mobile SDK is also covered?We're working to integrate our mobile app with SourcePoint who have Adobe as a listed vender under 565 Adobe Audience Manager (Adobe Experience Platform) and it’s unclear...

Views

59

Likes

0

Replies

0
Re: setPushIdentifier not working on app launch Adobe Cam...
Avatar

Rev_J

Rev_J
- Adobe Experience Platform SDKs
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.

Views

78

Likes

0

Replies

0
Re: setPushIdentifier not working on app launch Adobe Cam...
Avatar

Rev_J

Rev_J
- Adobe Experience Platform SDKs
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.

Views

82

Likes

0

Replies

0
Re: setPushIdentifier not working on app launch Adobe Cam...
Avatar

Rev_J

Rev_J
- Adobe Experience Platform SDKs
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?...

Views

86

Likes

0

Replies

0
Re: setPushIdentifier not working on app launch Adobe Cam...
Avatar

Rev_J

Rev_J
- Adobe Experience Platform SDKs
I will test some more, but I wonder if actually this function doesn't work properly, and it's simply the way that Launch is configured to trigger posts to ACS using Actions or collectPII that is naturally posting during the use of the application?

Views

102

Likes

0

Replies

0
Re: setPushIdentifier not working on app launch Adobe Cam...
Avatar

Rev_J

Rev_J
- Adobe Experience Platform SDKs
It would help if you can confirm that setPushIdentifier is supposed to be automatically posting to the Adobe Campaign server?

Views

104

Likes

0

Replies

0
Re: setPushIdentifier not working on app launch Adobe Cam...
Avatar

Rev_J

Rev_J
- Adobe Experience Platform SDKs
Thanks Ivan, they don't appear to be showing at all unless we kill and relaunch the app and incorporate a collectPII function

Views

105

Likes

0

Replies

0
Re: setPushIdentifier not working on app launch Adobe Cam...
Avatar

Rev_J

Rev_J
- Adobe Experience Platform SDKs
After more investigation it appears that the setPushIdentifier function is simply setting the SDK pushIdentifier string rather than pushing this to Adobe Campaign. For that an Mobile Core > Action or collectPII is required, correct?There seems to be some delay in this setPushIdentifier function setting the string, so when we call collectPII immediately after it isn't available for Launch to send to Adobe Campaign, despite being available generally.How are other developers mitigating this? Or is ...

Views

125

Likes

0

Replies

5
setPushIdentifier not working on app launch Adobe Campaign Standard
Avatar

Rev_J

Rev_J
- Adobe Experience Platform SDKs
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/supported-mobile-use-cases.html?lang=en#send-push-tokenThe 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 setPushIdent...

Views

174

Likes

0

Replies

14
Likes given to