@ErinF @RohitSahu I wanted to check in on this again, as I haven't heard anything via email. Thanks ... View more

@RohitSahu Just sent over an email. Thanks for looking in to this. ... View more

Ok @ErinF , I have something a bit more definitive for you.   The root cause of the extension not opening is due to ERROR Signature verification failed for extension, coming from the CEP11-AEFT.log in the %temp% directory.   I downloaded ZXPSignCmd to check this out, and sure enough when running the -verify option on the extension folder, I get: Error - Failed to verify signature. Signature might have been tampered with.   However - when I run ZXPSignCmd -verify on our .zxp distributable itself, I get: Signature verified successfully. It also has a valid timestamp.   So, something must happen to the signature when using UPIA /install, since the ZXP is verified before install, but the extension folder cannot be verified after install. Then, after opening AE as admin, and then running the extension (which now opens successfully), I can run ZXPSignCmd on the extension root folder and it returns successful.   Checking File Properties for both the extensions root folder and the META-INF/signatures.xml, they seem to have the same permissions before and after running AE as Admin.   I would've thought it was an issue with our signing process, but the fact that it is working on MacOS, and not all Windows users are experiencing this issue, makes me think it's something to do with UPIA? Really not sure though. Please let me know if I can provide any more info, or if the engineering team is looking at this. I'm considering reverting our Windows installer back to ExMan in the meantime if we can't figure it out, since ExMan seems to install correctly.   Thanks again for your support on this! ... View more

Hey Erin,   A couple things to note:    You asked previously if users were able to uninstall our plugin and reproduce the problem a second time if they go to install it again?   --> Yes, it seems after reinstalling a second time, they will have to run AE as Admin again.   Also, I had a user run the UPIA /install command directly, and it still wouldn't work.   Is there a chance there's an issue with our zxp or something? We haven't changed anything with the signing process, only the method of installation (ExMan -> UPIA). Was there any word from the engineers?       ... View more

Thanks @ErinF . I also just got some reports about our plugin working correctly in 24.0.0, but then after updating to 24.0.1, the panel doesn't open, until running AE as admin again. So potentially some permission for the extension is lost between the minor update? Just wanted to pass that along as well. Let me know what the engineering team says, and thanks for your support.  Side note - is this the best place to continue discussion of this, or would you prefer another forum? ... View more

Thanks @ErinF . I will check with some of the users experiencing this and see if they get back to me. Not sure when that will happen.   In the meantime - Is the engineering team aware of any changes between ExMan and UPIA that would cause something like this? Our same zxp, installed with ExMan, works fine, while installed with UPIA requires that a non-trivial subset of users run AE as administrator for the panel to show up. UPIA /list all also shows that the plugin is installed, it just doesn't open. Also, the ZXP installer from https://install.anastasiy.com/ seemed to have the same issue.   I'm trying to think back to when I was testing these installers on my Windows machine. I think I noticed that when running from the command line, upia /install didn't seem to require admin permissions - as in, didn't prompt the user with a popup dialog requiring the approval of the changes being made. While, I believe ExMan did require them. Not sure if that's relevant, since upia is packaged with CC. ... View more

Hi @ErinF ,   I distributed some installers using UPIA, but have found that a subset of Windows users are not able to open the plugin, until they run After Effects as an Admin (i.e. "Run as Administrator"). From this point on, the plugin is functional, even if re-opening AE normally (not as Admin).   Any idea why this may be? The plugin is installed successfully and shows up under Extensions, it just doesn't open.  ... View more

Thanks Erin. There are still some odd issues when using ExMan and updating to AE2024 and UPIA (mostly outlined above), but we will be able to work through them with some custom logic in our installer.   I also understand I'm a late adopter of UPIA and so others may not experience these issues. If you or the engineering team ever need more info, feel free to reach out. Thanks again! ... View more

Hi Erin,   Thanks so much for the response.   You're right that we've packaged ExMan as part of our installer / script-based installation process. We're moving to UPIA currently. I think this issue would affect us even if we'd updated installers to UPIA, as we would have a portion of the user base that chooses not to update - so eventually they'd update to AE 2024 with an ExMan-installed extension.   I've done a bit more digging based on some of the info you provided. Apologies if it's TMI but I wanted to lay out what I found.   1. (Before updating AE) Installing our extensions via ExMan (v7.11) still works, and updates the UPIA database file accordingly. We don't write to any DB file in the installer, we rely on ExMan to do that. The ExMan database files are empty after installation. Both UPIA --list all and ExMan --list all show the same extensions, presumably because ExMan v7.11 is referencing the UPIA database in some fashion.   UPIA/ExMan --list all --> com.my.Extension   Most notably, in the UPIA table Tb_ExtBasicInfo:         ExtName: com.my.Extension         ExtIDInFile: ""         InstallSource: ExManCmd   2. Then updating AfterEffects to the 2024 version... This is when the extension file duplication happens.    In Library/Application Support/.../Extensions, the file is duplicated (causes issues in AE):         -com.my.Extension         -Extension   UPIA/ExMan --list all --> Extension   In the UPIA table Tb_ExtBasicInfo:         ExtName: Extension         ExtIDInFile: com.my.Extension         InstallSource: ExManCmd   UPIA/ExMan --remove com.my.Extension --> -406   So the original com.my.Extension is lost in the Ether as far as UPIA/ExMan are concerned, but the folder still exists in the Extensions folder. When updating AE to 2024 it seems the original DB entries are modified. I think the crux of the issue is that when installing, based on the Tb_ExtBasicInfo entries, it seems that ExManCmd uses the ExtensionBundleId "com.my.Extension" (presumably from the Extension Manifest file) as the ExtName, and UPIA uses the  ExtensionBundleName "Extension" as the ExtName.    Unfortunately, since the DB entries are overwritten on update, it seems there is no way to rely on either UPIA or ExMan to remove the old com.my.Extension folder. We'll probably have to rm -rf that folder in a new installer.  ... View more

Careful here, your entry for  "�­":173, has a hidden space (<0xad>) in the key string. Took me forever to find it. You can paste it in Sublime or a console to verify.  ... View more

Great, thanks! ... View more

@JohnColombo  I suppose it could be that AE is setting / re-setting the $.global object sometime after startup as well?  ... View more

Hey John, we run our extension as a panel. Unfortunately the issue is transient, and not reliably reproduced. All I know is that it started with 22.6. Users have reported that it resolves by: a) Downgrading back to 22.5 b) Over time, by either refreshing the panel, restarting AE, or their computer. This doesn't work 100% of the time however.   It happened on my machine once, and I was able to troubleshoot a little bit. The issue indicates to me that our jsxbin did not load into AE correctly via the code I pasted above. Calls to our extendscript functions were all throwing errors about a field in the $.global object being undefined - an object which we set when our jsx loads. ... View more

Hi There, Were any changes made with respect to how CEP extensions' JSX files are loaded into the host application? We've been seeing many user reports with this update specifically, indicating our jsxbin file is not being loaded properly.    We've been loading our jsxbin as such and have never had any issues prior to this update:   const __dirname = getSystemPath('extension') evalExtendscript( `$.global[${JSON.stringify(process.env.CEP_ID + '.meta')}] = { extensionPath: ${JSON.stringify(__dirname,)}, version: ${JSON.stringify(process.env.BUILD_NUMBER)} }; $.evalFile(${JSON.stringify(path.join(__dirname, 'ourjsx.jsxbin'))})`, ) ... View more

Has anyone noticed an issue using composition.markerProperty.setValueAtTime(...)? This was working until one of the latest updates (22.1).   The call is failing with "After Effects error: CSelectronASSERT fail: CSelectron: layer is null". Wanted to see if this was just an issue on my end, or a potential bug in the latest release?   ... View more