Flat packages Adobe installation issue (policy / self service)

[RaniPM]

Hello,

I would like to know if you've encountered the following issue with the (Flat) Adobe packages generated via the Adobe Admin Console.

When we generate an Adobe flat package and upload it to the JSS to make it available via self-service, during installation, it shows as "completed" in the self-service, even though it is still being installed.
Therefore, if we create a JSS policy with multiple product packages, preferences, and scripts, including Adobe products, it considers the Adobe application installed and moves on to the next item. This poses a problem because often these are Adobe plugins or preferences that need to be installed after the Adobe product.

We experience the same behavior if we incorporate the flat pkg into a package generated with Composer, along with a post script to install the flat package.

We don't have this issue with non-flat Adobe pkgs, but apparently, it's become mandatory for Sequoia.

Additionally, the installation of Adobe flat packages is much slower compared to non-flat ones...

Thank you for your help.

[czarmark]

Having to keep recreating those Adobe PKGs, re-uploading them to Jamf, testing, etc several times a year to keep the installer reasonably up to date prompted me to switch to using Installomator to install Creative Cloud Desktop and Acrobat Pro. Given how massive those installers are, coupling Swift Dialogue provides a visual cue to the end user about the download and install status. Something to consider.