AppCode 2016.1.1 update is out

Hi everyone,

AppCode 2016.1.1 update is available for download. If using AppCode 2016.1 you will get an automatic notification in the IDE.

This update delivers the following fixes and improvements:

  • Now in case you’ve opened Xcode project which is already included into workspace with the same name located in same directory, you will get the notification with the Reload project as workspace option:
  • This update includes several fixes for rendering Included from… compiler messages which can appear for some compiler notes. Starting from this version these messages will be displayed as a sub-node for corresponding note and will be collapsed by default:included_from@2x
    In addition, we fixed the issue when it was not possible to hide such messages by pressing Hide warnings button in Build messages tool window (OC-7637).
  • Issue with the #import statement added to the end of another import when creating new class from usage (OC-12544) is fixed.

Find complete release notes here and feel free to share your feedback in the comments section below.

Your AppCode team
The Drive to Develop

Comments below can no longer be edited.

4 Responses to AppCode 2016.1.1 update is out

  1. Avatar

    Ali kiran says:

    April 7, 2016

    Another bunch of nonsense fixes let’s hope in next build appcode will support swift better than TextMate

    • Avatar

      Dev says:

      April 7, 2016

      That’s a bit of an exaggeration.

    • Stanislav Dombrovsky

      Stanislav Dombrovsky says:

      April 7, 2016

      Let me explain. It’s the minor bug-fix update that we usually make to address critical issues. As there were no really critical issues with the current release – we decided to put some minor fixes in this update together with regressions. The issue with #import addressed in this build was reported by many users in the past. And it’s quite important for Objective-C programmers. Other fixes are minor improvements made on the way.

  2. Avatar

    Michał says:

    April 7, 2016

    Thanks for fixing OC-12544!
    @Ali: While I would love to see a better Swift support, I realise how complex the language is and I imagine how hard can it be to support it, given how often Apple changes the language. Also Apple had been working on Swift tools long ago before it was announced, and they probably have more resources than JetBrains. I think there’s no need for such negative comments, they won’t help anyone.

Discover more