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.

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.