I have an issue with my Extension with Windows 8 and Photoshop CC. When I try to call the extension, the extensions panel pops up but keeps blank, then shortly after a dialog box shows "Cannot complete command because the extension could not be loaded".
By chance I discovered that the registry entry
"PlayerDebugMode"="1" in [HKEY_CURRENT_USER\Software\Adobe\CSXS.4]
helps the extension to load! Since that registry entry is claimed to "run unsigned extensions during development" (see EB docs), I wonder whether the loading error is an code signing issue showing up only with Photoshop CC (and Windows 8?).
Additionally, in the "csxs4-PHXS.log" I found the line
2013-08-22 14:09:38 : INFO Return value of PlugPlugLoadExtension call : PlugPlugErrorCode_invalidSignature
which seems to approve my assumption.
Does this mean, that I need a valid (trusted, non self made) code certificate to deploy my extension for Photoshop CC (and later)?
Any help is very appreciated!
I had the same problem. The manifest editor created an invalid path to the swf.
I edited the xml to change the swf path from "./" to "../" and the screen is no longer blank.
Hope this helps.
Thank you for your advice, but for me, this didn't work. With the manifest.xml edited that way, my extension doesn't even show up in the extension menu. So there must be other reasons.
If you create an mxi file you can convert it to a zxp or just use the cert that Adobe Exchange Packager creates. To download Adobe Exchange Packager sign in with your Adobe ID here:
Then go to Resources. Packager might be able to help...