I want to test if the .ccx file is installed in the PS software. When I double-click the .ccx file, it doesn’t install. I have created a new listing for this project. Can you help me pass the review?
After double-clicking the .ccx file, only the cmd window flickered and then nothing happened; the plugin was not installed.
Are you on Windows? This is a major bug on some Windows computers. I’ve brought it up in the monthly UXP Developers Office Hours, but no one at Adobe seems to know about it or how to solve it. I’ve had several customers experience this problem. They are all on Windows computers. I think it might be related to admin privileges as it does not happen on all Windows computers. Fortunately only a rather low percentage experience this, but it definitely happens consistently. There are two solutions:
-
Use a third-party installer like Anastasiy, ZXP Installer, or Aescripts+aeplugins. If one third-party installer doesn’t work, try another one. Almost everyone finds one that works.
I don’t think this problem will affect the Adobe review of your plugin as it is likely a problem related to your computer (not the plugin), and Adobe has not acknowledged that this problem even exists as far as I know.
However, if you are a developer and are experiencing the command-window flash when trying to install a plugin via .ccx files, you should get some logs and/or contact Adobe as getting this problem solved would be much appreciated.
Log collector tool is here: Allow offline development - #14 by Erin_Finnegan
I apologize if I have pulled your post in the wrong direction, but the command-window flash has been diagnostic for this very frustrating problem with all my customers who have experienced it. If you find a solution, please post it.
3 Likes
Hey I’m someone at Adobe who knows about it!
I could swear we came up with some solution or another with @gregbenz about this.
Sometimes running the host app as an admin first and installing the CCX can be helpful, if I recall correctly. (I know that’s not always an option for all users.)
1 Like
I haven’t found a silver bullet, more a mix of solutions. AnthonyK’s suggestion for the command line is good, as it at least shows an error code when things go wrong. The flashing black window just leaves you scratching your head. I’ve also heard several people tell me that Anastasiy’s installer worked when the official Adobe installer failed.
Is there some way UPIA could stay on screen or pop a message when there is an error? Just closing during a fault makes things very challenging for the average user to even know where to search for help.
@Erin_Finnegan Separately, I run into some users who install the PS beta only (without production PS). When they do, CCD may say that there is no valid host application. The logic does not seem to consider the beta as a potential target, so they end up having to install production PS. It’s an edge case, but would be helpful to address as it helps to support PS beta testing.
I’ve had people try that without success but will be interested to know if it works for @HAO-RANGE .
Also, not being disrespectful of you or Adobe. I know that not being able to emulate a problem makes solving it difficult.
Thank you all! I tried downloading some free plugins from Creative Cloud, and they work properly, so for now, I can only try to upload the plugin to Creative Cloud.
I can also confirm this problem. So far 99% with this problem were able to install the plugin with the third party installer from aescripts..
However, a solution from Adobe is urgently needed as the installation fails silently. As Greg has already mentioned, in case of an error, the error text should be displayed and a link to a help page should be provided.
1 Like
Trouble is, if Adobe does not fix this, you’re going to be stuck using ZXPInstaller forever. And, I’m not sure if ZXPInstaller overwrites previous versions like the CC app does when CC app installs a new version of your plugin. I’ve had customers tell me that with third-party installers, they need to first go into the CC app and uninstall the corresponding plugin in the “Plugin management” section before they can install the new version. Very inconvenient, this.
I am also developing a UXP plugin, and I can say that in my case, on Windows, the plugin usually doesn’t install by CCX. The screen flickers, and nothing happens. On Mac works ok.
I wonder what could be the deciding factor. I’ve been using my own CCX for years since UXP was available on Ps. Started on Windows 10 64bit with manifest v4 API v1. Then API v2. Then upgraded PC to Win11 with a new hardware (except HDDs). Then updated plugin to manifest v5. During these years I’ve been installing my CCX from Desktop and from other locations on different drives 
So far didn’t have such issue 
@vimalvarshney This keeps popping up. It’s a permissions problem with Windows that seems very hard to reproduce.
@HAO-RANGE seems to be able to consistently reproduce the problem. Maybe Adobe could work with this developer to pin down the problem and find a solution. Seems like a good opportunity to finally figure it out.
@HAO-RANGE if you can reproduce the problem, generate some logs following the steps below. (Please note that the two steps of log collection are a pretty heavy lift for end users.)
First install the Log Collector app).
Next, create and rename these empty files:
- Create an empty file named ExManCoreLibLog.YES (with .YES extension, not .txt extension) in the following location:
- Win: C:\Users\AppData\Roaming\Adobe\UPI\Log\
- Mac: /Users//Library/Application Support/Adobe/UPI/Log/
- Create an empty file named asu.trace (with .trace extension, not .txt extension) in the following location.
- Win: C:\Users***\AppData\Local\Temp
- Mac: /Users/***/Library/Logs
After that re-install the extension, reproducing the problem.
Finally, send the following information in an email:
- If the plugin is from Adobe’s marketplace, provide a link to the listing. If it’s not from Adobe’s marketplace, engineering will need a copy of the plugin installer from the developer (or the user if you’ve got the installer).
- The log file(s) you collected. The log collector outputs a ZXP.
2a. It’s very helpful to include the file name of the ZXP in the body of your email. - The time you noted from your computer when the plugins went missing.
Email and share the above to ccintrev@adobe.com and CC vvarshne @ adobe . com and cc me finnegan @ adobe.com
Note that ZXP files sometimes get lost in the spam filter. If you’ve sent everything and it’s been a few days with no response, email again with no attachments.