Table of Contents generated with DocToc
- Submission Checklist
- Top 3 Rejection Reasons
- Adobe Branding Guidelines
- Benefits & Best Practices
- FAQs
- How can I generate coupon code(s)?
- How can I submit a patch?
- How can I edit my metadata?
- Can I reply to a review left by a user?
- How can I change the bundled ID for a CEP extension?
- How can I fix the following .DS_Store or macOSX error?
- How can I add a collaborator, colleague, or teammate to the Exchange Portal?
- How can I drop support for a Creative Cloud app while submitting a patch?
- How can I fix a server error encountered on the Exchange portal?
- How can I troubleshoot the following errors on the Exchange portal?
By reviewing every plugin submission, Adobe aims to help developers get ready for primetime and ensure that users have great experiences with the plugins they install.
This document will give you an idea of what we're checking for during the review process. While lengthy, working through the points below will help you make sure you've accounted for all the requirements and avoid having to fix things and resubmit before getting published.
- A plugin name can only include "Adobe Photoshop" if it fits the pattern "\${Plugin Name} for Photoshop". Refer to the [Adobe Branding Guidelines](https://partners.adobe.com/content/dam/tep_assets/public/public_1/documents/Adobe-Creative-Cloud-Developer-Brand-Guide.pdf) for further information. For example:
- OK: "Rectanglator", or "Rectanglator for Adobe Photoshop"
- Not OK: "PS Rectanglator", or "Rectanglator PS". "Rectanglator PS" would be rejected based on the plugin name.
- The plugin description must be both relevant and self*explanatory.
- Regardless of supported languages, an English description must be provided.
- All listing content, including author name, email address, and website must comply with [Adobe Branding Guidelines](https://partners.adobe.com/content/dam/tep_assets/public/public_1/documents/Adobe-Creative-Cloud-Developer-Brand-Guide-062218.pdf).
- Any plugin website must provide an email address or contact form so that the users can contact the plugin developer easily. (We will check your provided website to confirm this information is present.)
- The listing should not link to the websites that are still under development (i.e., "under construction", "coming soon", etc.).
- Plugin icons must not contain Adobe product assets or icons. (Please note that many submissions are rejected because they contain Adobe product icons.)
- Plugin icons must be clear and free of distortion.
- Plugin icons should be clearly visible when the Creative Cloud desktop app is set to dark mode.
- Screenshots in the listing must not contain Adobe product assets or icons without prior permission from Adobe Branding team ([email protected] or [email protected]).
- The videos in the listing must be relevant to the plugin/publisher. They should not contain any Adobe assets or icons without getting permission from the Adobe Branding team ([email protected] or [email protected]).
- Make sure to review and adhere to the Adobe Branding Guidelines (login required).
- Avoid using publisher names, domain names, email addresses, and other such property names that are confusingly similar to existing Adobe brand, product, or service names. Eg: [email protected], [email protected] or XYZforAdobe.com
- Using Adobe assets and icons in your plugin or your plugin marketing material requires explicit permission from Adobe. Note that getting permission to use Adobe branding assets can add to the time it takes to get your plugin reviewed, approved and published.
-
The plugin and associated marketing surfaces must not include any intense violence, blood, gore, sexual content, nudity, or strong language.
-
The plugin must not promote or conduct phishing, spamming, hacking, password trafficking, or spyware, nor contain malware, trojans, or viruses.
-
If your plugin requires paid credentials, when you submit your plugin to Adobe, you must provide test credentials for login, license key, API Key, or anything else that would be required to fully review your plugin.
-
All plugin functionalities must be accessible, either openly or through the credentials that you provide to Adobe, for Adobe's reviewers.
-
If a plugin requires additional steps before it can be used with the Adobe products, the steps need to be present in the "Where to find it" section. For example: After acquiring the plugin from the Creative Cloud desktop application, the user needs to perform more steps like moving or placing some files at desired location and such instructions must be clearly mentioned in the "Where to find it" section.
-
Installation instructions should be present for all the supported point products.
-
Instructions should be clear and precise so that end users can locate the plugin for each supported point product.
-
The ZXP must install successfully.
-
After installation, the plugin should be visible at the desired place as mentioned in "Where to find it" section.
-
After opening the ZIP, if the resulting file is an EXE and/or DMG, ensure that the file plugin matches the supported platform(s) noted in the listing information (for example "Windows only.").
Once the user installs the plugin, we make sure that the newly added plugin is working seamlessly, and customers can use it to enhance their productivity.
-
The plugin must install without error.
-
The plugin should launch successfully in the maximum supported version of the point product.
-
The plugin should launch successfully in the minimum supported version of the point product.
-
Modal dialogs must provide an affordance in the UI for closing the modal (e.g., a cancel/close button).
-
The plugin must never show a completely blank UI.
-
The plugin shouldn't get stuck on any screens with no way to navigate out.
-
The plugin must indicate to the user if an internet connection is not available but is required.
-
The plugin must work as described by the developer.
-
All the external links that are added to the plugin must open a website when clicked.
-
UI elements in the plugin must not overlap or truncate.
-
Plugin content must follow Adobe Branding Guidelines.
-
No content should be clipped.
-
UI content must wrap or adapt as necessary to accommodate the available width of the UI.
-
The plugin UI must scroll when all content is not visible on the screen.
-
The plugin must not degrade the performance of Adobe products.
-
The plugin must load in a timely manner.
-
The plugin must not cause abnormal resource usage (e.g., CPU, RAM, storage).
-
The plugin must not cause crashes, system errors, or any major failures.
-
Share the license code with review team if the end users need to enter them in the plugin so that the plugin can be activated.
-
The team will store the license keys on FastSpring and when the end user buys the plugin from Adobe Marketplace, FastSpring will distribute the license key to the user.
-
Developers can mention details of license keys in the "Notes to approver" section.
During the review process, we check plugins with the aim to make sure users have positive experiences with the plugins they install. Sometimes developers' plugins are rejected during the process, particularly when submitting a plugin for the first time. When that happens, we request certain changes be made before they are re-submitted for review.
During the review process, we check plugins with the aim to make sure users have positive experiences with the plugins they install. Sometimes developers' plugins are rejected during the process, particularly when submitting a plugin for the first time. When that happens, we request certain changes be made before they are re-submitted for review.
Developers often use Adobe brand assets without getting prior permission, (for example, Adobe's "A" icon). This violates the Adobe Branding Guidelines. It is advised that before you start using the Adobe assets, please get permission from the Adobe Branding Team by contacting them at [email protected]. Once the permissions are granted you can start using Adobe assets on your website and in your screenshots.
-
At the time of testing, the review team validates all of the functionality of your plugin. Please make sure before submission that your plugin is functioning as advertised, and all the features are working properly.
-
Silent failures: If the plugin user attempts an unsupported function, the plugin must not fail silently. Plugins must display a dialog that this action/functionality is not supported so that users understand it and avoid repeating the same action.
-
Your plugin is compatible with all of the Adobe products, product versions, and operating systems you listed in the "Product Compatibility Information" section of your listing.
-
Sometimes the installation instructions provided with the submission are not descriptive enough to help a user find the plugin and install it for each of the Adobe applications this product supports. Please note each version of an Adobe application your product supports should have a unique set of instructions listed in the "Where to find it" section of the listing.
-
If the review team cannot find the files mentioned in the "Where to find it" section of your listing, your plugin will be rejected. Please supply the path where users would find this plugin from within the Adobe product.
There is a predefined set of guidelines that are published by Adobe periodically for the use of Adobe assets and product icons. It is expected that developers strictly adhere to these guidelines.
Association with Adobe will increase acceptability within the user community and users are confident that plugins will meet Adobe's quality standards, which developers can leverage by using Adobe assets with their products.
Adobe does not allow any change into product icons. Developers are allowed to use Adobe published assets and logos within their products, as long as they do not alter Adobe icons in any way.
With due diligence, we expect you to thoroughly read the Adobe Branding Guidelines and follow the guidelines exactly. Failure to do so will result in rejection during the review process.
Link: https://partners.adobe.com/exchangeprogram/creativecloud/marketing/dev-brand-guide.html
Note: Make sure that you are logged in on the Exchange Developer Portal, otherwise, you will not be able to access the link.
-
Use same developer AdobeID for both UXP and CEP plugins: You should always use the same developer ID to submit CEP and UXP plugins. This makes it easier to track plugin performance, manage your listings, and respond to user comments.
-
Proper Description: Use the description field to explain what your plugin can do, what are its features and functionality, and what can be achieved using the plugin. It is very beneficial for end users if you provide a video that captures plugin functionality so that new users get a better understanding of how to use your plugin.
-
Update Your Plugin(s) Regularly: Updating your plugin(s) on a regular basis to make it compatible with the latest version of the supported point product. Updating you plugin(s) will provide an awesome and seamless experience for the end user which will reflect on your revenue and ratings.
-
Share Test Credentials: Always share test credentials with the review team via the "Notes to Approver" section. Sharing test credentials while submitting the listing will help us expedite the review process.
-
Share a License: Some plugins require users to enter a license key before use. If the same is to be done for your plugin and FastSpring is used to handle your payments, you should share 100 license keys with the review team via the "Notes to Approver" section and we will store the license keys on FastSpring. FastSpring will distribute the license key to users who have successfully purchased your plugin.
-
Note: Before the current license exhaust, [email protected] will contact you to provide an additional license and they will restore the license on FastSpring so that the user can obtain the license key after purchase.
-
It is up to you how many licenses you want to store on FastSpring. In general, we encourage developers to share at least 100 licenses although you are free to share fewer or more license keys if you wish to do so.
-
-
Provide Proper Installation Instructions: Make sure to provide proper installation instructions under the "Where to find" section, like what files users need to install, or where to place the files. If the plugin supports multiple Adobe products and the instructions are not the same for each product, then the developer must provide the installation instruction for each point product individually. (For example, if the installation instructions are different for Photoshop versus InDesign, please include the instructions for both products.)
-
Follow the Adobe Brand Guidelines: Before you use any Adobe brand asset, (for example, product icons) you are required to read the Adobe Brand Guidelines and adhere to them. Without obtaining proper authorization from Adobe, you should never use an asset in your listing or for any marketing purposes. Use of Adobe assets without prior approval will result in rejection.
-
Provide Support: You must make sure that users can always reach out to you and inform you of problems with your plugin. In many cases, we have seen that users give poor reviews and ratings to plugins due to a lack of communication.
-
Additional Payment: If any kind of additional payment is needed to use your plugin, then you must share all the information about it with the user, and you must write about it in the plugin description.
-
Companion application: If any kind of additional application is required for your plugin to work then information about this must be mentioned in the plugin description and you should specify where the user can download the companion application.
-
Millions of Creative Cloud users will have direct access to your plugin(s) through the Creative Cloud desktop app or the Adobe Exchange webpage.
-
Easy, one click installation; installation is handled by the Creative Cloud desktop app.
-
Plugin acquisition is tied to an AdobeID. Users may easily reinstall your plugin on a new machine or on alternative hardware.
-
Users are automatically notified of plugin updates and installing updates is easy.
-
Developer profiles: Users can easily find all of your plugins on one page.
-
An easy monetization opportunity built in. Adobe uses FastSpring for the handling of payments.
-
Users can trust that plugins listed on the marketplace are both secure and useable, because they have gone through a formal review process.
-
You may use our official "Designed for"-Badges to promote your plugin.
-
Additional Support is available to users for installation issues.
-
Developers receive a free Creative Cloud subscription. (For a free seat please contact us at [email protected]).
Answer: You can ask the Review Team to create a coupon code (or codes) on your behalf. You will need to share the following details with Review Team:
-
Extension name (or listing name)
-
Coupon validity period: You may restrict your discount to a certain date range or request a perpetual coupon.
-
Percent off: Specify the discount you want to give your user(s).
-
Coupon code and code format: Coupon codes are supported in two formats: single coupon code, and multiple random codes.
-
For a single coupon code, please choose a unique coupon code that will be stored on FastSpring. Every time a user enters your coupon code on the payment page, a discount will be applied to the cart value. (For example, “MYCOUPON-FREE".)
-
Multiple Random Codes: If you want, for example, 100 coupon codes, the Review Team will generate the codes. Please supply a five-character prefix that will be added at the beginning of each coupon code.
-
The Review Team will contact you once the coupon creation process is complete. You may then distribute your coupon code(s) to your customers and instruct them to enter the code during the checkout process.
Answer: You may submit a patch when you update functionality for an existing listing. Updating functionality might include new features or bug fixes.
Below are the fields that you may edit when submitting patches:
-
Upload File (Note: For a non-ZXP upload, the file type of the patch needs to be of the same file type as the parent upload file.)
-
Version Number (Note: This applies only to ZIP based extensions. CEP based extensions have version numbers that are automatically generated from the manifest file and cannot be entered manually.)
-
EULA (End User License Agreements)
-
Where to Find It
-
Installation Instructions for Enterprise Users or Creative Cloud Teams users
-
Release Notes
-
Note to the approver
-
Login to the Exchange Developer Portal.
-
Go to the Dashboard.
-
Select the name of your extension or listing (this applies only to listings that have already been published).
-
Click on the “More” dropdown button (upper right) and choose “Create New Patch”.
-
Now click on the Patch Details Tab.
-
For ZIP-based extensions, you may change the version number. ZXP-based extensions acquire version numbers automatically from the manifest file and cannot be updated manually.
-
If you don’t want the patch to be published immediately upon approval, uncheck “Publish this patch immediately upon approval”. In this case, the patch will appear in the “Not Published” section of Dashboard once approved, and you will need to publish it manually for it to appear on the Creative Cloud Exchange Marketplace.
-
Scroll down and click submit.
-
The Exchange Portal will show a message that changes requested are submitted successfully and you will receive an email from [email protected] and [email protected] confirming your submission.
-
If your last patch submission was rejected, you will need to click on the “Not Published” section and open the last rejected version.
-
Click on the “Edit” button and select the “Patch Details” tab.
-
Now replace the previously uploaded file with the new one.
-
For a patch upload, the file type needs to match the parent file type. For example, during the first-time submission, if you uploaded a ZXP file, then during the patch submission, you need to upload another ZXP file.
If you face an issue while creating metadata or patches, contact the Review Team at [email protected]. Also be sure to check the Exchange FAQs (Frequently Asked Questions).
Answer: If you want to change the description, images, link or any of the information listed here, follow the instructions below:
- Purchase Method
- Primary Tags
- Secondary Tags
- Custom Tags
- Language Supported
- Summary
- Detailed Description
- Listing Icon
- Featured Image
- Preview Images and Videos
- Release Notes
- Documents
- How to Sell
- EULA
- Where To Find It
- CCT/Enterprise user
- Note to approver
-
Login to the Exchange Developer Portal and go to the Dashboard.
-
Select the listing you want to change in the ‘Published’ tab to edit it.
-
Select Edit.
-
Make edits to any of the four Tabs (Details, Images, Upload & Docs, Notes & EULA).
-
Scroll down and click “Save & Next” (or back to switch between tabs).
-
Once you’ve made your changes, click on the ‘Save’ button and preview the listing.
-
If all the changes are correct, click on the ‘Submit’ button.
-
The Exchange Portal will show a message that your changes were submitted successfully. You will receive a submission email from [email protected] and [email protected].
Answer: Yes, you may reply to comments directly from the Exchange Portal or using the Creative Cloud Desktop App.
Answer: The bundled ID is a unique identifier. Once an extension is published you can’t change the bundled ID. If you want to use a new bundled ID, you must create a new listing.
- DS_Store or _MACOSX were detected and rejected in upload due to security reasons. Please upload a new package without these files. Please contact [email protected] with questions.
Answer: When uploading a ZXP file, you may encounter the .DS_Store or a macOSX error above. The macOS operating system adds hidden files to directories.
Note: If you’re not signed in as an administrator, you may be asked to enter your name and password to access the Terminal app and use the commands needed to delete DS_Store files.
-
From the desktop, select Go > Utilities > Terminal.
-
Locate the folder containing the DS_Store file and navigate to that directory in the Terminal. For example, if your folder is on the desktop, use the cd desktop command and press Enter.
-
Type find . –name '.DS_Store' –type f –delete to delete all of the .DS_Store files in the current directory and press Enter.
-
Select OK. The .DS_Store files in the folder you selected will be deleted.
Answer: You may provide access to collaborators so that they may update or change your listing.
-
Login to the Exchange Developer Portal.
-
On the top right side click the “Edit Profile” button.
-
Now click on Add/Edit Users and click on “Invite contact”.
-
Fill in your contact’s details (FirstName, LastName, Email) and click on “Invite”.
-
An invitation will be sent to the requested user.
-
Your collaborator must complete the AdobeID registration through the email link.
-
Once the registration is complete, the collaborator has to create an account on Exchange Developer Portal, and after this step, the collaborator will be able to update the listing.
Answer: It is not possible to drop support for Creative Cloud apps (e.g., your listing is compatible with Photoshop, Illustrator, and InDesign, but you wish to remove Photoshop support). The listing must support all point products that are supported by the first published version you submitted.
In some cases where developers can no longer support Creative Cloud apps, they must submit a new listing and withdraw the old listing once the new listing is approved.
Answer: Kindly clear the cache and cookies (at least the adobe.com cookies) before logging into the Exchange Developer Portal. If the issue persists, then please follow these steps:
-
Clear the browser cache and cookies.
-
Log out from the Exchange Portal and log in again.
-
Use the steps below to collect the browser network and console logs as you try to publish your listing.
- How to capture browser network and console logs:
- Open the Chrome browser and reproduce the error.
- Open the Chrome Developer Tools by typing Cmd+Option+I on Mac or F12 on Windows.
- Please keep the Developer Tools open to see the error.
- Select the Network tab. In the Name column and click on the Name for which you are getting server errors.
- Share all the details that appear in the Headers tab (Request URL, Response Header, Request Headers etc.)
- Next, select the Console tab and share the logs if you see any errors there.
- Create a HAR file by following the steps in this article: https://support.zendesk.com/hc/en-us/articles/204410413-Generating-a-HAR-file-for-troubleshooting
- Kindly share both the network logs and the HAR file through Google Drive or Dropbox.
- If possible, record a video and share it as well, via link or in the same Google Drive or Dropbox folder.
- Share the logs described above with us (share the logs in the HAR file along with screenshot of network/console logs with [email protected]. Providing logs (and optionally video) will help the Adobe Engineering team in fixing the problem expeditiously.
- Plugin manifest has an invalid host app min version
- Ensure that the Adobe product minimum version is in valid x.y format.
- Ensure that the Adobe product maximum version is in valid x.y format.
Due to an issue with the Exchange portal, the host.minVersion and host.maxVersion in your UXP plugin manifest must be specified in a.b format. We will soon support the a.b.c format (later in 2023, the date is unconfirmed at this time). For example, if your manifest.json contains:
"host": {
"app": "PS",
"minVersion": "22.5.7"
},
Before submitting to the Marketplace, please edit your manifest.json to an a.b. minVersion format:
"host": {
"app": "PS",
"minVersion": "22.5"
},
Please note that as of December, 2022, the Exchange portal no longer accepts "99.9" as the maximum version number in extension manifests. Previously, you could submit ZXP packages to the exchange with the manifest specifying a maximum product version of 99.9. For example, if your extension supports Illustrator version 25 and up, you may have included the following line in your manifest file:
<HostList>
<Host Name="ILST" Version="[25.0,99.9]"/>
</HostList>
If you want to indicate no maximum version, only include the minimum version in your manifest, for example:
<HostList>
<Host Name="ILST" Version="25.0"/>
</HostList>
Additional manifest documentation is available here. Also please review this chart of product version numbers.