AppCode 2016.1.2 bug-fix update

Hi everyone,

AppCode 2016.1.2 update is available for download. If using AppCode 2016.1.x or 2016.1.2 RC, you will get an automatic notification in the IDE.

In addition to changes described in the blog post about AppCode 2016.1.2 RC, this update contains important fixes for two security issues inside IntelliJ Platform. The vulnerabilities, in various forms, are also present in older versions of the AppCode; therefore, patches for those are also available.

Find more information about the issues, the affected versions and ways to update in this special blog post.

It is strongly recommended for all users to install the update as soon as possible.

The minimum AppCode release version for which update will be released is AppCode 2.1. Please find below the information about updates and patches availability:

Release version Version with security fixes Patch availability
2.0 or 2.0.x update,
2.1 or 2.1.x update
2.1.3 For 2.1.2
2.5 or 2.5.x update 2.5.6 For 2.5.5
3.0 or 3.0.x update 3.0.7 For 3.0.6
3.1 or 3.1.x update 3.1.8 For 3.1.7
3.2 3.2.1 For 3.2
3.3 or 3.3.x 3.3.4 For 3.3.3
2016.1, 2016.1.x
or 2016.1.2 RC
2016.1.2 For 2016.1.1

In case you need to download the full build with all the necessary security fixes, you can either use link from the Version with security fixes column in the table above or download specific build from the page with previous AppCode releases.

Your AppCode team
The Drive to Develop

Comments below can no longer be edited.

4 Responses to AppCode 2016.1.2 bug-fix update

  1. Avatar

    Tropper says:

    May 11, 2016

    “[…] In addition to changes described in the blog post about AppCode 2016.2 RC, this update contains important fixes […]

    I guess there is a “.1” missing and it should be AppCode 2016.1.2 RC ^^

    • Stanislav Dombrovsky

      Stanislav Dombrovsky says:

      May 11, 2016

      You’re right, fixed!

  2. Avatar

    Werewolf says:

    May 23, 2016

    This version broke indexing of my project :-(((

    • Stanislav Dombrovsky

      Stanislav Dombrovsky says:

      May 23, 2016

      That’s strange. Could you please submit a ticket to our tracker with some explanation of your problem so we can investigate it?

Discover more