Thanks for the clarification. We can definitely leave this question open to see if anyone from the community has a better answer, but my answer would still apply. This isn't something within Adobe's control so I don't have a concrete answer. I'll move this over to the Experience Cloud section where mobile experts are more likely to see it.

Hi Jonathon,The App icon that appears on the device screen once installed require republishing in order to change because it is part of the app file and can't be altered without building and uploading an new version.Thanks,

Jonathan - yes that is correct when you are talking about campaign variables. You can use SAINT to change it to Direct if that makes it easier for your stakeholders to understand

If you build an AEM Mobile app using On-Demand Services, you can publish an app in iOS, Android, and Windows:Build AEM Mobile apps for iOS devicesBuild Android apps for AEM Mobile Build AEM Mobile apps for Windows Store

Updates to production apps aren't immediate (up to 5 minutes). I suspect the update just didn't reach the device until later.In preflight it's a much shorter time, it's almost immediate.

I would take a look at the DPS Learn example Colin references in this document. While it's referencing DPS, recall that the InDesign overlays do apply as well to Experience Manager Mobile.https://helpx.adobe.com/digital-publishing-suite/help/nesting-interactive-overlays.htmlFor additional examples of embedded overlays, including nesting slideshows within slideshows, see "Advanced Overlays" in the DPS Learn app.

Weird, I'm not sure I've actually seen this combination before. Have you tried using a video overlay instead of the image sequence? Does that show the problem?I'm wondering too if some different options on the image sequence would address this. For example, if you turn off any swipe or tap options for the image sequence.

Sorry I misunderstood you question. Glad you find you way to that tick box.

I'm not sure why you can't use the AEM Signing Tool to sign the app. Are you specifying the correct mobileprovision file and password? You might want to contact Adobe support for troubleshooting help.