Exchange

This is a repost from here:https://community.adobe.com/t5/indesign-discussions/cep-extension-digital-signing-with-pkcs-11/m-p/15480576#M634580Sorry for that, just thinking that this is important.  Hi! I know there were similar topics, but none of them answered. Sorry for asking again, but this is a serious issue. We develop .zxp extensions. They need to be updated from time to time. And new extension files need to be signed correctly. The problem is that ZXPSignCmd requires a .p12 file to sign the extension. It's not just another container format, the .p12 file contains a _key_ along with the signing certificate. The key is mandatory, without it you can't sign. And CAs don't seem to export signing keys anymore.For this reason: https://knowledge.digicert.com/alerts/code-signing-changes-in-2023 If there is a CA that still exports .p12 files, please let us know. It would be a lifesaver. At least for a while. But in any case, ZXPSignCmd requires PKCS#11 suppor

I used to be a seller on this platform. (I sold Photoshop plugins)Now I have returned to upload an outdated ZXP plugin to an updated UXP plugin.And this has been the absolute worst experience I have ever had on the internet in all my life.I am unable to upload or simply update my existing ZXP to a UXP plugin.I have to delete my old listing and create a new listing...The old listing allows me to upload up to 300 megabytes,however the new listing only allows up to 50 megabytes.FIFTY MEGABYTES?! What are we supposed to do with that?This whole website feels like a bureaucratic nightmare. It's impossible to find the actual link to get to the developer space. I had to ask chatGPT to find out how to return to my long forgotten profile. Everything seems abandoned and forgotten, and you have to run through hoops over hoops over hoops in order to get anywhere. It feels like the bureaucrats from Hitchhiker's Guide to the Galaxy, where forms have to be signed in triplicate and sent off to an actua

  Recently the Exchange team rolled out a change for compliance reasons. For the change, the Exchange marketplace was disabled for education accounts. Unforutanely, all education accounts were disabled, not just kindergarten - 12th grade accounts as intented (sometimes called primary school). We are working to roll back this change until we can filter K-12 accounts on the Exchange and allow higher education accounts (colleges and universities).   You can verify if your account was affected if you ses the error pictured above and the message "Access Restricted - Plugins are unavailable for your user type" when visitng this page: https://exchange.adobe.com/apps/browse/cc If you log out, you can see and browse plugins as expected.   If you don't have an education account and are still experiencing this error, please reach out to asupport@adobe.com with the affected email address.   Update, December 19:  The change was rolled back. Let us know in this thread if you continue to experience

Hello,    I wanted to share a small issue I encountered while developing a UXP plugin for Photoshop as my university project. The plugin is a custom 3D panel, and everything worked correctly during development and testing with the UXP Developer Tool.    The plugin packaged successfully as a .ccx file. However, when installing it through Creative Cloud or the Unified Plugin Installer Agent (UPIA), the installation consistently failed with the following message:Failed to install, status = -267!After a lot of trial and error, I discovered that the actual cause was much simpler than I initially expected: the plugin "name" in the manifest contained only two characters.{  "name": "3D"}Changing the name to any value with at least three characters allowed the plugin to install successfully without any other changes.    I couldn't find this requirement documented, and the returned error code didn't provide any hint about the actual problem. If this minimum-length requirement is intentional, it

어제 결제되어서 앞으로 사용할 일이 없을 것 같으니 바로 구독 끊고 환불 부탁드릴게요

This is my very first CEP plugin submission for the Adobe Marketplace, and despite following the Creative Cloud Developer Guidelines, I am having significant trouble successfully uploading my packaged file to the Producer Portal.Initially, I provided a.zxp file directly to the portal, the automated validator continuously rejected it with the following parsing errors:"Ensure the bundle version is not empty for CEP or MXI. Your MXI file or CEP manifest file is empty. Could not extract bundle ID from your MXI file or CEP manifest file... Ensure that at least one supported host product and its minimum and maximum versions supported by your extension are present in MXI file or CEP manifest file."To the best of my knowledge, myCSXS/manifest.xmlis perfectly well-formed. It clearly defines the ExtensionBundleId, sets the ExtensionBundleVersion="1.0.0", and explicitly defines the <HostList> with PHSP and PHXS pointing to version ranges [14.0,99.9]. The plugin also functions flawlessly wit

The Adobe Exchange website seems to be having issues for the last 2 weeks or so. Oftentimes I have to refresh the page 2 or 3 times to get it to load otherwise it will just be a blank page. Sometimes it will only partially load as if the CSS is missing and sometimes it will refuse to load at all and return a 500 internal server error. I’ve tried on multiple browsers and the same thing happens. Am I the only one experiencing this?  

I’m trying to update my extension for Premiere and Audition, but I haven’t been able to upload due to the version numbers. It looks like this was an issue before. Versions in manifest:<Host Name="PPRO" Version="[14.4,26.9]"/><Host Name="AUDT" Version="[14,26.9]"/>The errors I’m getting: The maximum version you mentioned is greater than the maximum supported version for product PPRO. The maximum version you mentioned is greater than the maximum supported version for product AUDT. https://community.adobe.com/questions-628/cannot-upload-zxp-for-illustrator-v29-to-the-developer-distribution-platform-685895?postid=2315959#post2315959 

I am an Adobe Exchange publisher with already published paid ZXP extensions:https://exchange.adobe.com/apps/cc/204619/social-exporterhttps://exchange.adobe.com/apps/cc/204633/effect-remover-proMy Adobe account is currently broken:- Adobe Account shows "Unable to load plans"- Exchange app pages show: "Something went wrong and the Details app crashed"- Adobe support says I have no paid products, which is incorrect for a publisherThis is clearly an ACCOUNT ENTITLEMENT / SYNC issue.Please escalate this to the Adobe Exchange / Commerce team to resync my account.This issue is blocking me from managing and accessing my published Exchange listings.

I've been wondering how it works for listing when the price is changed from Free to let's say a subscription of $5 a month. Do users that installed the plugin when it was free keep the plugin? Or do they have to make the decision to pay for the new set price? I can't find any information on this online so would really appreciate any insights in this! Many thanks in advance.

 Hi everyone,I’m currently developing a CEP extension for After Effects using plain HTML, JS and node modules. During development I ran into an issue that only happens on Windows, not on macOS. The root cause is that the Node runtime embedded in CEP on Windows is significantly older than the one used on macOS.This leads to very inconsistent behavior between platforms. One example is that many modern npm packages internally import core modules using the node: protocol, such as:  import { EventEmitter } from "node:events"  This syntax is fully valid in modern Node, but on Windows CEP it results in:  Error: Cannot find module 'node:events'  Even though the exact same code works perfectly on macOS.The problem is not the package or code I write it’s simply the fact that CEP on Windows runs an older Node version that doesn’t support this syntax. Developers are now forced to downgrade packages, patch node_modules manually or use heavy bundling workarounds ju

Please correct me if I'm wrong, but as far as I know, Auto FX Software has been out of the Photoshop plugin business for a few years, yet it's still listed for sale on the Adobe Exchange. https://exchange.adobe.com/apps/cc/20033/auto-fx-software-mystical-ultimate-bundle-gen2

I tried different approaches to preserve "set kerning between two characters" options. For some reason after I change text inside textItem and try to preserve styles - it changes from "Optical" to "Metrics". How do I overcome this behaviour? Nowhere in code I set kerning option to metrics and I expect it to be saved. It is not in 100% of cases. I attached file with reproduction. For first string in file - everything works as expected - for second kerning changes.  

Hi Everyone,I'm wondering about if how I'd go about creating a sequence with some clips from the active sequence with ExtendScript.The #track-insertclip function won't really work since it's looking for a project item, so my cuts would be lost. I noticed that I can call #trackitem-setselected  on clips but calling #sequence-createsubsequence does not create a subsequence from only the selected clips like it does in the UI.The last thing I tried was calling #trackitem-remove on the clips I don't want in the sequence clone. But this one is too slow if my project is larger than a basic case. Is there a way to do this directly? Or alternatively, can I mass delete all selected clips in anyway?I'd appreciate any pointers and thoughts.Thanks!

The following is a simplified version of the ScriptUI code I am working on. var win = new Window("dialog{\ e:EditText{characters: 4, text:'0'}}"); win.e.addEventListener ("keydown", function(e){ if(e.keyName == "Up"){ var num = this.text - 0; this.text = ++num; } }); win.show(); EditText aims to allow you to enter text freely as usual, and if the text is a number, press the UP ARROW on the keyboard to add 1. However, when I execute this code, 2 will be added when I press theUP ARROW.   What I tried. Insert “e.stopPropagation();”  ...There was no change in the result. Insert “e.preventDefault();”  ...The point where 2 is added at a time has improved, but text can no longer be entered. Insert “$.writeln(e.timeStamp); $.sleep(1000);” ...A timestamp that was offset by 1 second was output. Change the event to “keyup” ...The event handler is now executed 3 times (I'm laughing).   Is there a good solution? Regards.

If you encounter the message "This listing is not currently available in the EU. This developer has not submitted the trader information required by the EU Digital Services Act." and you cannot install or re-install a plugin or other listing  from the Adobe Exchange Marketplace you may wish to reach out to the developer or owner of the listing and let them know you're unable to access their listing.   Some (but not all) listings provide contact information in the Marketplace under the "Help & Support" section:     Reach out to the developer and gently encourage them to add required profile details to their developer profile to stay compliant with the EU Digital Services Act (DSA). FAQs are available here. 

I'm having problems creating a plugin for IllustratorNo matter how I make it, it won't show up in IllustratorI tried the following, but to no avail:- The script type works, but it is not suitable for my job- I tried several kinds of CEP/ExtendScript, but it doesn't work and doesn't appear in Illustrator- I used C++/SDKs  and created an .aip file, but it still doesn't appear in Illustrator- The UXP type doesn't support Illustrator at the moment, although I tried to find a way to do thatWhat should I do? I feel really confused, because I tried it on three different computers, but none of them worked

I am adding a flyout menu to my CEP extension that is targetted to InDesign. The menu is added fine, i add the eventhandler to com.adobe.csxs.events.flyoutMenuClicked even as well. However, inside the event handler the data object that is supposed to contain the menuID and menuName has a strange string which seems like a JSON but is an invalid JSON. My code is as following const flyoutMenu = ` <Menu> <MenuItem Id="option1" Label="Autolayout" Enabled="true" Checked="false"/> </Menu> `; csi.setPanelFlyoutMenu(flyoutMenu); csi.addEventListener("com.adobe.csxs.events.flyoutMenuClicked", function(event) { const clickedMenuId = event.data.menuId; switch (clickedMenuId) { case "option1": alert("Autolayout selected"); break; } }); When I check event.data in the console I get the following "${"menuName"=2"Autolayout","menuId"=2"option1"}"  Notice the $, =2 I am not sure wh

Extension License damagedI cant install extensions usinmg creative cloud desktop and when i tried using extenstion manager i still get an error code adobe error code 604

Sooo I know the update was made just a few hours ago, but I already have an issue... I can't start a debug session nor run a script, it always gives me this message: When I install the previous version, it works just fine, and I can't find anything in the change logs that would justify this new error...  Can I please get some help on that one?

At the bottom of my plugins page on Adobe Exchange, there is a MORE BY THIS PUBLISHER column that shows the other recommended plugins that I have developed.     The problem is, they will always show the two oldest and most unsophisticated ones that I have just started submitting to Adobe Exchange. Furthermore, those are plugins for Adobe XD, and Adobe has already treated XD as a maintenance mode and has stopped developing and adding new features.   So, MORE BY THIS PUBLISHER is now showing only plugins that neither Adobe nor I want and that are less likely to be useful to the user. It is of limited benefit to anyone.   Is there any way to make this column more user-friendly, such as allowing developers to choose which plugins to display in this column, automatically displaying the best-selling (most popular) ones, or displaying them in the order of new releases?

Hey FolksI know it's weekend but I keep getting this error trying to upload an update to my extension. Is there a known error, is there somewhere to check on the status?I tried again after several hours, from both Chrome and Firefox. Tried uploading the previous version that was accepted before, and same error.thanksThere were errors with the Plugin file objectThe scanning service encountered an unknown error. Please try again later.Refer to this guide for most frequent errors on package upload.

The problem: ZXP files signed on macOS are failing when installed and run on Windows machines, and vice versa. On Windows, this may mean that the installed panel appears blank, or only functions as expected with debug mode enabled.   Expected Behavior: Historically ZXP files signed by ZXPSignCmd may be installed and used succesfully on both macOS and Windows, regardless of which platform they were signed on. The Workaround For the time being, the work around is to sign ZXPs on the platform they are expected to be run on. Sign ZXPs for use with macOS on a macOS machine, and ZXPs intended for Windows on Windows devices. FAQ Q. Which versions of Creative Cloud apps are affected? A. We're not sure. It could be related to Creative Cloud desktop app 6.4. It may only be for 2025 versions of dektop apps. Please help us report this issue by letting us know in this thread. Q. Will I need to maintain two different listings on the Adobe Exchange Marketplace? A. We're still invest

Hi All,I have created HTML5 extension for InDesign CC 2017 and CC 2018.The extension makes GET request to communicate with the server and get the required data.a. In case of CC 2017, GET request fails with ERR_SSL_VERSION_OR_CIPHER_MISMATCH.b. In case of CC 2018, works fine.I looked further into this and my findings are,- HTML5 extensions are hosted in embedded version of Chromium (Google Chrome).- CC 2017 uses Chrome version 41. Chrome 41 supports TLS version 1.2 (and previous versions).- CC 2018 uses Chrome version 57. Chrome 57 supports TLS version 1.3 (and previous versions).The server that the extension connects to supports TLS 1.2, therefore Chrome 41 (CC 2017) should work fine. Do I need to make any change for CC 2017? Please advise.Regards,Narayan