Since Photoshop version 24.1.0, I have encountered an issue where I am unable to load any plugins using UXP Developer Tools. However, if I downgrade Photoshop to version 24.0.1, I do not experience this problem. Currently, I am using UXP Developer Tools version 126.96.36.199.
I have searched for options in the Creative Cloud app to install previous versions of UXP Developer Tools, similar to how it can be done for Photoshop, but I couldn’t find any.
I have double-checked that the Developer mode is enabled in the Photoshop preferences. Additionally, I have attempted a fresh installation of Photoshop and UXP Developer Tools on a different hard drive with a different OSX (Mac-Ventura), but the issue persists.
I posted this problem on this platform a month ago, but I have not yet received any helpful replies. I would greatly appreciate any assistance in resolving this frustrating issue.
Could this issue possibly be a bug in either Photoshop or UXP Developer Tools?
I have attached a screenshot of the UXP Developer Tools console for reference.
The fact that I cannot load any plugin, not even the most basic one like the “hello-world-panel-js-sample” from Adobe since version 24.1.0, makes it challenging to think that the issue is with the plugins.
No issues with v24.0.1!
Do you know how to go back to an earlier version of the UXP Developer Tool?
I have some good news to share. I was able to resolve the problem!
It turns out that if the plugins are located on a different hard drive than the one where the operating system is installed, the plugins will not be loaded. Unfortunately, all my plugins were stored on a separate hard drive, which is why I couldn’t understand the problem until I early created the new plugins and saved them on my desktop.
I’m not sure if this behaviour is correct, but the important thing is that I can now load my plugins without any issues.
Funnily enough I was going to suggest this as the cause of the issue as I vaguely remembered a post that suggested as such, but when I searched the forum I couldn’t find it and I didn’t want to speak without evidence!
I had this same problem – AGAIN! Because I forgot about this and migrated my dev files to a new bigger external hard drive…
This is a WTF error.
As in, WTF don’t they fix it so you can load from external disks (Apple).
OR, if it is this way for security purposes, WTF don’t they update the error message to tell you the file needs to be on the same drive as the op system .
Sheesh, I lost 2 hours searching the forums for this answer, again.
– Now noted in my dev errors manual.