Closed jazzace closed 5 months ago
Thanks @jazzace, @paul-cossey brought this to my attention earlier and I'll be looking into this more tonight/tomorrow.
Updates to follow.
@jazzace should be done.. just needed to add 24.1 to the json - https://github.com/autopkg/dataJAR-recipes/commit/06ee1c4d9c5989b83703cf8c96443c883c484350
Test and let me know.
And, FWIW.. the OptionXML.xml has this defined as 24.1.. despite being 24.0.x
<Medias>
<Media>
<TargetFolderName>APRO24.1</TargetFolderName>
<InstallerLocation></InstallerLocation>
<isCompressed>false</isCompressed>
<mediaLEID>V7{}AcrobatCont-12-Mac-GM</mediaLEID>
<SAPCode>APRO</SAPCode>
<prodVersion>24.1</prodVersion>
This works. Thanks for the quick fix (and working around Adobe being Adobe).
The file
AdobeAutoPkgApplicationData.json
, which assists theAdobeAdminConsolePackagesPkgInfoCreator
processor when determining the package version of an Adobe Admin Console Package, was updated today to support Acrobat DC version 24. Running theAdobeAdminConsolePackagesPkgInfoCreator
processor on an Admin Console package of Acrobat DC 24.001.20604 calculates theaacp_application_major_version
to be 24.1 (rather than 24.0), so any recipe with that combination fails. For example, when running an override of the recipeAdobeAdminConsole.pkg.recipe
from thejazzace-recipes
repo that specifies the Acrobat package path:(In order for my recipe to find the JSON file, I need to symlink to it in the RecipeOverrides folder. This should not be the cause of the problem, since it works with all other Adobe applications including Acrobat v.23.)
The expected run result is that the processor determines that the major version is 24.0 (which is included in the updated JSON file) rather than 24.1.