AEP Mobile SDK privacy service deletes all data when set to OPT_OUT, however this is also used to collect consent for push permissions for ACS thereby creating a situation where you have a targetable application in ACS with no means to update consent via the app directly to ACS via collectPii etc. According to our tests, it's currently impossible to update consent in ACS to be false using collectPii prior to setting Privacy = OPT_OUT. Placing these requests in sequence still results in the later...

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

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.

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.

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 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?

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

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

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 ...