Thanks for the clarification. I don't think the logic for this is correct. Once the ECID is cleared then no further updates can be made to Adobe Campaign, therefore the application is still contactable in Adobe Campaign, but we lose the ability to capture any data about it, including permissions. Wh...

If the Privacy service is set to OPT_OUT after being opted in, it doesn’t invoke anything to Adobe Campaign Standard to remove the registration token. Is this correct behaviour? What is the intended flow here? Use collectPii to force a blank token before invoking OPT_OUT?

This has been accepted as a bug by Adobe. You can duplicate an OOB push template and configure with mobile app etc.When you come to use the template to create a push, the Associate a mobile App to a delivery is not inherited from the push templateWhen you go back to the push template the dropdown ha...

I'm a bit puzzled. I can't find anywhere to link the Mobile App being targeted to a push delivery template. This option doesn't appear in the template advanced configuration anywhere.The result of this is that every time one of my users creates a new push message from any push delivery template, the...

Your last paragraph was the answer I was looking for thank you. It's for beyond standard privacy and into (equally standard) permissions. I was hoping the Profile attributes store available within the Mobile SDK would have encryption. https://aep-sdks.gitbook.io/docs/using-mobile-extensions/profile

I'm working with an app dev team who are capturing a preference flag called OptIn that is being pushing to Adobe Campaign Standard via collectPii.The developers want to be able to retrieve this flag so they can show the current status on a preference screen in app.I believe that they need to store l...

It turned out there were 2 issues causing this same end result. 1 was front end (dev), 1 seems to be an Adobe back end issue. 1 - Front endDeveloper forgot to put the lifecycle start code into their app...@Overridepublic void onResume() { super.onResume(); MobileCore.setApplication(getApplicat...

Ok, it turns out there is one potential Adobe back end problem, and one dev issue which was causing the same end result.

The collectPii workaround has been disabled now that the backend problems have been resolved and the Launch rule disabled passing token via contextData.

I'm working with multiple app dev teams and some of them are reporting that some Android devices being registered target platform Apple. I believe this is something code related because my application registers fine on the same Launch property, but I wondered if anyone with technical knowledge of th...