Signature verification failed on MAC but not on Windows

Report · Feb 23, 2018

Good morning.

I've been developing PPRO extensions since a year ago and self-signing my releases with ZXPSignCMD for 3rd parties usage.

Since the update to CEP8 I have noticed the Signature verification is failing on MAC.

I mean. I am signing and packing my extension on a mac laptop and It is loaded and works properly on Windows machines, but on MAC the extension appears on the extensions list and the logs said first signature verification was ok. Then I click to open the extension and it is never showed and CEP8 logs show Signature verification failed.

The ZXPSignCMD has the verify option and I have also verified it is OK.

I even downloaded the CEP8 samples on the github and gives me the same Signature Verification error, so it is very weird.

Of course with the DebugPlayerMode =1 works, but I only use this for development purposes.

Anyone having the same issue? Any hint of what is happening?

Thanks

moved from Premiere Pro CC to Extensions / Add-ons Development

[Moderator]

Report · Nov 06, 2018

we are having a similar issue with an indesign&photoshop cep plugin - did you ever solve this?

Report · Dec 05, 2018

Did either of you figure this out? If not I'll ask the product team.

Report · Dec 05, 2018

Not really. AFAICT, using a signing key from a recognized CA (certificate authority) seems to work. However, until recently this was not a requirement (and is documented as such). I would appreciate a definitive response from Adobe to this issue and ideally documentation updates, if this is, in fact, the case. Thanks ErinF.

Report · Dec 09, 2018

I dealt with this for most of my day today on Mac High Sierra, with the latest Creative Cloud 2019 update. I hope this helps.

The documentation for this is all over the place. I was even getting "Signature verification failed" when trying to open the official PProPanel, following the steps exactly. Different pages of even the Adobe CEP Github can't even agree on whether "com.adobe.CSXS.9.plist" + CEP logs are stored in the system Library or the user Library folders. For me, both of these exist in the user Library, as in "/Users/<username>/Library/Preferences" and "/Users/<username>/Library/Logs". Curious if anyone has it set up differently.

Anyways, the issue for me was that com.adobe.CSXS.9.plist only had System "Read/Write" privileges, and not User "Read/Write" privileges. I should have thought of this a little sooner, to be fair, as Terminal was requiring me to use "sudo" ahead of the "defaults write com.adobe.CSXS.9 PlayerDebugMode 1" command. Another symptom was the "defaults write com.adobe.CSXS.9 LogLevel 6" command didn't seem to be giving me any extra info in the logs. It was rather confusing, because when I opened com.adobe.CSXS.9.plist, the values were correctly set to "PlayerDebugMode 1" and "LogLevel 6".

It seems that Premiere or any other CS application is unable to read the "com.adobe.CSXS.9.plist" file when it only has System "Read/Write" privileges, and proceeds to silently revert to a "default" of "PlayerDebugMode 0" and "LogLevel 1".

The solution for me was to right click "com.adobe.CSXS.9.plist" and click Get Info, then unlock the permissions with the tiny lock button on the bottom right of the Info panel. Type your password, then make sure that "everyone" has "Read & Write" privileges. Restart computer, and everything should start working as expected.