Apple OS 10.15 Catalina supports 64-bit apps only. Since CC 2018 or prior apps contain 32-bit components, these apps will fail to launch on machines running macOS 10.15 Catalina.
Feb 19, 2015 Hey all: Created and deployed a Creative Cloud 2014 package to our Apple iMac OS 10.9.5 The package is now out of date and desktops cannot install updates. I have attempted to create an update package with Adobe Creative Cloud Packager but the update package will not install. I am attempting to cr. Download Adobe Creative Cloud Packager. If you are a Creative Cloud for teams customer, download Adobe Creative Cloud Packager from the Team Admin Portal in Adobe Creative Cloud.; If you are a Creative Cloud for enterprise customer, download Adobe Creative Cloud Packager from the Adobe Licensing Website (LWS) or Admin Console.; Note: Adobe recommends that Creative Cloud Packager. Jun 24, 2016 The reason for this is that you do not have the Creative Cloud Packager installed on your machine. In order to install it, you can either download it from the Licensing Website or from your Enterprise Dashboard or the Teams admin console under the deployment option. Thanks, Ankit Singh. Creative Cloud Enterprise Support.
For more details, see Why don't my Adobe apps work in macOS 10.15 Catalina?
For example; if you create a package containing CC 2018 and CC 2019 apps, the package will deploy successfully. The CC 2019 apps will also launch successfully, however, when end users launch a CC 2018 app it will fail with the following error message:
Issue with quarantine bits in downloaded package
Note:
The issue and resolution detailed in this section applies only to packages created prior to October 24, 2019.
Creative Cloud Packager Mac
If you are creating packages after this date, see the Adobe Package Downloader article for details.
![Adobe creative cloud packager for mac download Adobe creative cloud packager for mac download](/uploads/1/2/9/3/129362384/759570794.png)
When you create a package on the Admin Console, a zip archive of the package is downloaded to your computer. In the Admin Console, the zip file is created on-the-fly and then downloaded. Since it is created dynamically, a zip file downloaded on a macOS machine has the com.apple.quarantine bits associated with it.
Adobe Creative Cloud Packager Download
This is the case for zip files downloaded on any macOS machine. However, in the case of a machine that is running macOS 10.15, you will be unable to extract and deploy the associated package that has the com.apple.quarantine bits associated with it.
After the zip file is downloaded, you will first need to remove the quarantine bits, extract the contents, and then deploy the package.
Follow these steps to remove the quarantine bits:
- Open the Terminal and navigate to the folder containing the downloaded zip file.
- Run the following command to check if the downloaded file has the quarantine bits associated with it:xattr <downloaded packaged name>If the output of the above command, contains the following, then the quarantine bits are associated with the file:com.apple.quarantine
- Run the following command to remove the quarantine bits from the file:xattr -d com.apple.quarantine <package name>
- Again, run the following command to check if the downloaded file has the quarantine bits associated with it:xattr <downloaded packaged name>The output of the above command will no longer display the below:com.apple.quarantineThis means that the quarantine bits have been removed.
- Extract the contents of the zip file to get the package.
- Go ahead and deploy the package on your end-user machines.
Due to changes introduced in macOS 10.15 Catalina, Admin Console installer package zip files created prior to September 16, 2019 will fail to decompress properly on machines running macOS 10.15.
If you are installing packages on a 10.15 client machine, then we advise that you should take one of the following steps:
- In the Adobe Admin console, leverage your existing package to create an update package.
- Create a brand new package.
- Extract the existing package on a version of macOS prior to 10.15 and then deploy it to the machine running 10.15.
Note:
If you are using JAMF Casper or MUNKI, then the package you have uploaded to your repository will continue to install successfully on 10.15 and prior versions of macOS, because it has already been extracted.