# Plugins autoupdate

**URL:** <https://forums.creativeclouddeveloper.com/t/plugins-autoupdate/1469>\
**Category:** UXP Plugin API\
**Tags:** feature-request\
**Created:** [December 8, 2019, 1:29pm UTC](https://forums.creativeclouddeveloper.com/t/plugins-autoupdate/1469 "2019-12-08T13:29:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gdreyv](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/gdreyv/32/358_2.png) [@gdreyv](https://forums.creativeclouddeveloper.com/u/gdreyv)\
**Post date:** [December 8, 2019, 1:29pm UTC](https://forums.creativeclouddeveloper.com/t/plugins-autoupdate/1469/1 "2019-12-08T13:29:31Z")

</div>

Just curious is it possible to enable plugins auto update by default? We keep getting errors reports from plugins which are 2-3 releases back from current one. It looks like people just don’t see that updates are available.

---

<div class="post-metadata">

**Author:** ![stevekwak](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/stevekwak/32/48_2.png) [@stevekwak](https://forums.creativeclouddeveloper.com/u/stevekwak)\
**Post date:** [December 9, 2019, 3:03pm UTC](https://forums.creativeclouddeveloper.com/t/plugins-autoupdate/1469/2 "2019-12-09T15:03:50Z")

</div>

@afuchs can provide more details here but auto updates are currently not possible

---

<div class="post-metadata">

**Author:** ![Velara](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/velara/32/1278_2.png) [@Velara](https://forums.creativeclouddeveloper.com/u/Velara)\
**Post date:** [December 9, 2019, 7:00pm UTC](https://forums.creativeclouddeveloper.com/t/plugins-autoupdate/1469/3 "2019-12-09T19:00:55Z")

</div>

> [@gdreyv](#):
>
> We keep getting errors reports from plugins which are 2-3 releases back from current one.

Or some companies are a version or two behind in XD because an XD project created in v24 will not open in v23. So teams usually have to be on the same version. And that means upgrading has to be approved and everyone has to upgrade at the same time.

In one case I had to require version 21 to support some new plugin features and their team had to update XD if they wanted to use the new version of the plugin. But not everyone can do that.

An auto update would be a nice addition to keep people updated.

---

<div class="post-metadata">

**Author:** ![gdreyv](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/gdreyv/32/358_2.png) [@gdreyv](https://forums.creativeclouddeveloper.com/u/gdreyv)\
**Post date:** [December 10, 2019, 8:37pm UTC](https://forums.creativeclouddeveloper.com/t/plugins-autoupdate/1469/4 "2019-12-10T20:37:31Z")

</div>

I’m not saying it is not possible. I’m saying (correct me if I’m wrong) now to update plugins users have to press Update button in the bottom of the screen. The point is not to wait for users approval and update plugins automatically.

---

<div class="post-metadata">

**Author:** ![kerrishotts](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/kerrishotts/32/8_2.png) [@kerrishotts](https://forums.creativeclouddeveloper.com/u/kerrishotts)\
**Post date:** [December 13, 2019, 8:55pm UTC](https://forums.creativeclouddeveloper.com/t/plugins-autoupdate/1469/5 "2019-12-13T20:55:16Z")

</div>

Auto update is something coming in the future, but it’s not currently possible in the plugin manager.  
You _could_ check your plugin version with one on your server and then notify the user that things may be out of date, but of course that won’t apply retroactively to existing installs.

---

<div class="post-metadata">

**Author:** ![gdreyv](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/gdreyv/32/358_2.png) [@gdreyv](https://forums.creativeclouddeveloper.com/u/gdreyv)\
**Post date:** [July 23, 2020, 3:08am UTC](https://forums.creativeclouddeveloper.com/t/plugins-autoupdate/1469/6 "2020-07-23T03:08:32Z")

</div>

do you have any updates on that? It’s really huge pain for us that users keep complaining on the issues we fixed and released several months ago. It’s really weird that we have to implement custom workaround to show that they are using not the latest version of the plugin.
