Open speedgeil opened 2 days ago
Hello!
This could be related to a wider problem we've been noticing. If you enable debug mode and the extension runs as expected, it's probably the same difficult-to-reproduce bug.
Here's the forum thread where's I'm tracking the problem, and there are some workarounds to try.. Try the steps there and report back here or in the forum thread.
Hi Erin, thanks for your quick reply. Meanwhile i was able to identify the problem. BR 2025 won't accept the certificate of the plugin. It will throw an error in the BR log when trying to start the extension. BR 2024 will accept it, no problems. When enabling the debug mode on Mac and Win, the extension will start. So it seemed to me i would need to re-sign the extension.
There seems to be an issue with ZXPcmd: https://github.com/Adobe-CEP/CEP-Resources/blob/master/ZXPSignCMD/KnownIssue2024.md
Seems like this issue struck me here. I re-signed with Win11: No luck with starting the extension under Win11 or Mac. Then i re-signed with a Mac M1 on Sonoma and was able to start the extension on the same Mac. Didn't try Windows yet. Will report back later when i know more.
I have a CEP extension here that refuses to load in BR 2025: "(name of the extension) can't be loaded + (path to html file of the extension)" without any additional infos. Worked fine for years until upgrading to 2025. Checked manifest.xml and updated all node modules in the extension folder, but still not loading. The extension is also using a startup script. Usually there is a notification when upgrading or installing the extension, that a new startup script has been found etc... But not on 2025. But it is showing under startup scripts in the Bridge preferences.
Happened on Mac M1 on MacOS Sonoma and Sequoia BTW