Bug Reports

Снял деньги за план который я отменил 23 июля. Верните мои деньги 

  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

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 

 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

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.  

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

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?

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.

Hello,  I have an ALE metadata tool I've developed and from all of my testing I'm finding that I can't update the Original Audio File Name field using the setProperty() function on a XMPMetaInstance.  For example:  var kPProPrivateProjectMetadataURI = "http://ns.adobe.com/premierePrivateProjectMetaData/1.0/"; var xmp = new XMPMeta(childItem.getProjectMetadata()); xmp.setProperty(kPProPrivateProjectMetadataURI, "Column.PropertyText.OriginalAudioFileName", "MyWaveFileData.wav") var xmpAsString = xmp.serialize(); childItem.setXMPMetadata(xmpAsString); This works completely as expected when updating any other default property, such as Column.PropertyText.OriginalVideoFileName. Also, when I use dumpObject() I can see the Column.PropertyText.OriginalAudioFileName property, but premiere isn't reading it correctly, and will display incorrect data. See screen grabs and txt file attached. Peremiere 2025 (25.1.0)MacOS - 15.

Re-posting here from a Premiere Pro forum:  https://community.adobe.com/t5/premiere-pro-bugs/zxpsigncmd-sign-process-is-broken-segmentation-fault/idi-p/15276774 Just looking to see if there is awareness of this issue and/or a timeframe for a fix. For Apple, workaround seems to be to use Apple's TSA: http://timestamp.apple.com/ts01 For Windows, seems the best option currently is to sign without using a TSA, but I understand that is not recommended. Given the known issues and recommendation to sign ZXPs on the platform they are expected to be run on, we'd like to know if there is a plan for a fix before pre-emptively going with a sub-optimal workaround.

I'm using a MacBook Pro 14, and my extensions are not showing in After Effects. Can you help me with this?

Hi!We have some users resporting that they cannot use Anastasiy's Extension Manager to install our Extension.If they download our extension through this page  a very old version of the Extension (version 1.2.1) eventhough the latest one is 1.13.1.Can you please advise what to do?

Show all ticket but create new ticket not working also. my old all ticket show solved. now how can we connect for create and support for extensions https://commercedeveloper.adobe.com/extensions/ 

I am trying to submit a CEP extension which has been packaged as a ZXP. I have tested the ZXP file extensively successfully on both Windows and Mac, however the ZXP has been rejected multiple times with the reason being it fails on Windows. Does anyone have an idea how Adobe's submission process tests Windows devices or if they know of any reason a working ZXP file might be rejected due to a Windows error?

not able to set the font baseline option using the below Adobe CEP or extended script. textRange.characterAttributes.baselinePosition = FontBaselineOption.NORMALBASELINE;

Hello, we tried to publish a new patch to support Illustrator v29 today on the Developer Distribution Platform. We have set the version in the manifest.xml as :<Host Name="ILST" Version="[21.0,29.9]" /> The .zxp file is rejected for the following reason:The maximum version you mentioned is greater than the maximum supported version for product ILST.Is this a bug or did we do something wrong with the manifest?

Here is my dilemma:If my xmi filename, which must be the bundle id, is too long, Adobe Exchange submission rejects my zxp with an unknown error.If I shorten the mxi filename, Adobe Exchange rejects my zxp because it now does not match with the bundle id.  The solution should be to shorten the bundle id at Adobe Exchange. How can I do that without bothering Adobe staff?

Hi support my magento version is :Magento ver. 2.3.4Getting email from FedExPlease be reminded that on and from 15 May 2024 our support for your connection with FedEx Web Services will end and be replaced by the new FedEx RESTful APIs. Our technical team will no longer be available to support FedEx Web Services from that day forward.FedEx RESTful APIs simplify system integration, improve security, and elevate the customer experience. We are developing additional features, and all new enhancements will only be available in FedEx RESTful APIs. Get ready to serve your customers with greater ease, flexibility, and agility by upgrading your system now! Let me know how update it , or avalible patch for it ?

Hey all, I have an extension I work on, which is installed using ExManCmd (have not moved to UPIA yet). In the /Library/.../extensions folder, the extension is installed with the bundleId from the manifest (not the bundleName). As in, com.my.TestExtension, instead of TestExtension. When updates land, the previous version is removed via exmancmd --remove, and the new one installed via exmancmd --install. This has worked and still works perfectly. With the landing of the 2024 update, it seems the extensions in the /extensions folder were duplicated, but instead of using the bundleId, it used the bundleName. So now there are two of the same extension with different folders: com.my.TestExtension, and TestExtension. This is causing issues when updating using the process previously described.  A few questions... 1. Why were the extension folders duplicated - is this a bug or something on my end I'm missing?2. If I release a patch to remove the Tes

There's nothing in your post related to PPro's API, so I'm moving this somewhere it might receive more expert attention...

Good day, ZXP plugin section allow to upload files upto 300mb but I can succesfully upload not more than 100mb files. When I trying to upload zip files more than 110mb - its starting upload process and stopped soon (1-2 minutes) without any notices or errors from Exchange. I trying some browsers, shutdowning firewalls but it's not help. --Also I want to ask: Is it planned to increase file limit more than 300mb in future? 

I have a ZXP plugin that has been maintained for 2 years and has released many versions before without problems. Recently updated a version, on the new publishing site (https://developer.adobe.com/distribute/) to submit, the result could not upload the file, as shown below. The package failed scanning due to containing a 0 byte file.   Have you encountered such a problem and how to solve it? thanks a lot!

Hi, I have developed a CEP extension which is packaged as a ZXP for distribution. After packaging and signing ZXP package using ZXPSignCmd, I got the issue in the Adobe Exchange the ZXP file had 0 Byte files. I have cleaned it up and repackaged and resigned and tried to upload to the Exchange but now it shows this error (Image below) Please guide me on this regard!