Yes, the testing has been a Broadcast In-App on Application Launch. I've also seen that the message won't get displayed if you don't have an action button, so have made sure that's being configured in the In-App payload. I can't see that anything else needs to be configured according to the documentation.

Looking at the main "code" documentation, it even states (post Mobile Core implementation which includes Lifecycle): "No additional setup is needed for iOS in-app messaging and local notifications.". Android states "If you are developing an Android application, to correctly display fullscreen in-app messages, add the Campaign Standard extension's FullscreenMessageActivity to your AndroidManifest.xml file", ref: https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-campaign-standard#init...

HI Shaun, the app is registering and push are being displayed correctly.The In-App message is broadcasting fine, but nothing is being displayed on the app.In-App tracking has been enabled in the Launch property, but I'm not seeing any tracking there.

No responses here and no responses on the Adobe Support ticket.

I've raised a support ticket

Even though the sequence is sending to ACS first, THEN setting privacy status? I'm expecting that we can do something prior to switching everything off.

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. When we don't respond to user permissions (such as don't contact me in preferences outside of control panel), or if other collected data are used to personalize or target messages, then there could be i...

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

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(getApplication()); MobileCore.lifecycleStart(null);}@Overridepublic void onPause() { super.onPause(); MobileCore.lifecyclePause();}When lifecycle start was included the device was registered correctly. 2 - Back end is...

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.

Quick update, it was a provisioning/tech ops issue with the staging environment.

Thank you Ryan. I see the documentation has been updated too.