Auto update extension once deployed...

[Mateo666]

Hello !

once a user install my extension how can it be updated? does it have to be redownloaded again ?

the extension we are developping will change every couple months and we want a user to have always the latest installed.

Would it be possible to have a basic extension that would check on our website if a new version is available and would download the new js jsx html files?

of course we want to sign this extension with a certificate.

Thanks

mateo

[Erin F.]

Hi Mateo,

For Adobe XD plugins this process is simple; users are prompted to update when one or more of their installed extensions have an update available.

However, I don't think this is the case for extensions listed on the Exchange. I'm asking around about this.

Best,

Erin

[Adam DeHaven]

I believe this is still an issue. Users that download Illustrator plugins via the Creative Cloud Desktop app are not prompted to update Plugins, and Plugins do not auto-update. 

Does this need to be fixed, or it never worked? Auto-updating plugins or at least notifying users when there is a new version of a plugin available seems like it would be the standard. 

[VIRGO1225 · Accepted solution]

Hello,

You can submit a patch update on the Adobe Exchange (https://partners.adobe.com/exchangeprogram/creativecloud/app-posting.html)

when you have a new product version available. Users who had downloaded your extension will receive an automatic update, ensuring they're always on the latest version of your integration.

Marie

[Sreejith5FF4]

We've observed even though we give a patch, users are neither downloaded nor notified of the new version of the extension. Users have to manually open the creative cloud and go to mange plugins and click on update button. We can't make user to do that each time. 😕 

[Trevor:]

If you where not going through the exchange then you could have the extension download from you site and store the files in an accessible location outside of the extensions folder in a way that won't mess up the signature.

There are quite a few caveats for doing this including.

HTTPS connections can be a real pain in the neck when the IT department etc. uses it's own proxies and you need to be able to add the appropriate security certificates to the extension.

Similarly the IT departments might not have you site opened.

The  "accessible location"  is going to be user based and not Admin based so it would need to be done for each user

The  "accessible location"  can well be not that accessible on some users systems

Adobe doesn't want you doing this as they don't want you loading malicious code onto their users system's. It's a bit mean hearted of them but one can see where they are coming from.

Best of luck.

Trevor 

[Erin F.]

Hi Mateo,

What Trevor is talking about is valid, but I think it depends a lot on what kind of Adobe Creative Cloud licenses your client has. If you're marketing to Creative Cloud Enterprise or Creative Cloud Teams customers, their updates might be managed through an Admin or they might use self-service installs.

If the clients/customers have individual Creative Cloud seats, the update experience is more like what Marie outlined.

Best,

Erin

[Mateo666]

Thanks everyone, we will go the standard way and publish a patch update.