AppCode 3.2 EAP, build 141.2000

Thank you for participating in the AppCode Early Access Program. We’ve started one for AppCode 3.2 recently and have got many useful comments and feedback from you. Today we’d like you to try the next EAP build (sorry, but patch update is not available this time). As usual, it doesn’t require an active license. We would really appreciate your feedback in our tracker.

Since Xcode 6.4 is released, we recommend to use this version in AppCode on OS X 10.10. On 10.9 the supported Xcode version is still 6.2. Xcode 7, by-turn, is in beta now, however we do our best to make AppCode 100% compatible and interoperable with Xcode when it’s launched. This time we’ve made AppCode run all the unit tests correctly with Xcode 7, regardless of the testing framework you are using (XCTest, Kiwi or GoogleTests).

In this EAP build, instead of the bundled LLDB, AppCode uses LLDB paired with Xcode you’ve selected in settings. That means, among other things, that you are able to use LLDB introduced in Xcode 6.4.

This build also addresses a couple of regressions while using ‘self’ keyword (OC-12030, OC-12153), fixes for Override/Implement in Swift that was introduced in the previous EAP (OC-12047, OC-11924) and more.

Develop with pleasure,
The AppCode Team

This entry was posted in Announcement, Early Access Preview and tagged , , , . Bookmark the permalink.

6 Responses to AppCode 3.2 EAP, build 141.2000

  1. John says:

    Is there any estimate on syntax checking? I’m waiting on this feature before I can switch back to using AppCode full-time (I’ve been using Xcode full-time for almost a year now, so glad to see that AppCode is almost there).

  2. Andreas says:

    I don’t know if this is the right section for this kind of question, but I’ll ask anyway: Does AppCode, like other JetBrains software, run on Java in OS X? If so, is there a timeline to do this app in the native language? I find Java a real hassle in OS X, so I avoid it anywhere I can. But I like the JetBrains software approach – so I’m kinda stuck here. Also, Apple is moving away from Java. I think, I’m not the only one with this issue. I’d like to see all JetBrains software written in Objective C for maximum performance.

    • Anastasia Kazakova says:

      AppCode is based on IntelliJ platform that includes all JetBrains expertise for over 15 years already. After Apple stopped supporting Java we actually turned into building our own custom JDK, based on 1.8, with fixes for many known Java 1.7, 1.8 problems (including performance and font anti-aliasing). The distribution package with the bundled custom JDK build is available for AppCode 3.2 EAP, that means that AppCode 3.2 will also be available with the custom JDK.
      Taken into account that AppCode is based on this platform and all features contributed to the platform are delivered together with the AppCode releases, it’s very unlikely that AppCode will change this in the nearest future and AppCode team will rewrite all the functionality in smth like Objective-C. Also there are no plans now to platform to migrate from Java (and Kotlin).
      We are trying the improve the look&feel on OS X, and do quite a lot in that direction. You are very welcome to address any specific problems/things you don’t like in our tracker: We’ll try to address.

Leave a Reply

Your email address will not be published. Required fields are marked *