Also, Extension Manager works fine for CS5.5 under 10.7, but fails for CS6. That implies that it's not just something about 10.7 that's broken.

Xiaoyi--

As Harbs noted, Chris and I both work on the same team at Em Software, so we're talking about the same problem.

Chris can explain in more detail why this immediately breaks at least one of our plugins.

However, we believe it will eventually fail for ALL plugins on update, as Extension Manager won't find the appropriate resources. Try it yourself--install some plugins that seem to work on first installation, and then update them.

Thanks!

To add to what Chris said, I doubt if it's really a 10.7 bug--it'd be hard for them to have such an egregious error and have no one spot it to date.

It's more likely an interaction bug between the Flash/Air runtimes that Extension Manager is running on, and some change in 10.7 behavior.

Just a theory, of course.

Xiaoyi--

I think this issue affects any Extension Manager user under 10.7, as we noted above; it often fails when updating plugins, even under CS5/5.5, in our experience, symbolic links or no. (I just hadn't put the two facts together.)

So this is pretty critical, and apparently not a burning issue because so few developers use Extension Manager to distribute their plugins (partly because of its flakiness in the past, I'm sure).

So it may be past time to evaluate its impact and treat it as an emergency situation needing an immediate fix.

Thanks.

Great, looks like it works in Extension Manager.

However, it looks like this problem also exists in ucf.jar in the packaging and signing toolkit.  Will it be fixed there as well?  This affects how our plug-ins work on Adobe Exchange, since they need to be signed.

Lawrence

Hi Xiaoyi,

I'm not sure I understand the workaround you suggest.  Are you suggesting going into the .zxp file produced by ucf.jar, unzipping it, and replacing all the resolved links (i.e. the duplicate files) with symbolic links?  Besides being quite labor intensive, won't this invalidate the code esignature?

Is the new signing and packaging tool you're referring to "Adobe Exchange Packager"? If so, it seems to display the same problem of not honoring symbolic links, and it won't accept my signing certificate.

Additionally, I just tried the latest version of ucf.jar, with a creation date of October 3, 2012, and it displays a new issue.  When I try to install an Extension created with that version of ucf.jar, Extension Manager displays the error "The extension 'com.[package name]' does not contain valid signature. The extension will not be installed."  The identical files work fine with the ucf.jar version with a creation date of June 12, 2012.

Lawrence