AppCode 3.2 EAP, build 141.2391

Hi everyone,

Today AppCode 3.2 EAP 141.2391 is available for download. The patch update is also available if you are using previous 3.2 EAP build.

This build introduces mostly bugs/regressions fixes and small improvements, like unresolved Swift parent class members used in Objective-C code (OC-12245), incorrect unused code inspection (OC-12238), regression with block parameter autocompletion (OC-12233) and Inline Variables View for Swift now working correctly.

Please, note that in case you have custom appcode.vmoptions file (for example, you were increasing memory to fix some performance issues) EAP build without custom bundled JDK won’t run, until you delete this custom appcode.vmoptions and copy (and update if you still need it) an actual version from

The full list of fixes can be found in our tracker.

Develop with pleasure,
The AppCode Team

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

20 Responses to AppCode 3.2 EAP, build 141.2391

  1. tigor says:

    What about the support of iOS 9 (beta)?

  2. sacred says:

    AppCode since 3.2 eap became completely unusable. Almost all project mark as red, but build finished successfully. But it’s rather inconvenient.

  3. Fabian says:

    “This build introduces mostly bugs…” haha :-)

  4. Mark says:

    Will AppCode 3.2 support Swift 2.0 syntax? Currently constructs like “do..catch” and “try” are flagged as syntax errors. There may be others.

    Is there a list anywhere of what’s supported and what’s not?

    It’s confusing when valid constructs are marked as errors.

    • Anastasia Kazakova says:

      Swift 2.0 is not supported yet, and not going to be included into 3.2 version. You can follow this: to know about the progress and subtasks.

      • Chris says:

        No Swift 2.0 in Appcode 3.2?

        Seems a little odd, this decision. Xcode 7 GM is just around the corner, and breaks compatibility with Swift 1.2 big time. So much effort on your part is put into releasing a major stable version (which brings serious improvements, like resolution of external frameworks), just to make it last for 1 month?

        Don’t get me wrong, the work put into AppCode is phenomenal. It just seems a strange move to not support Swift 2.0 early. On the other part, I do understand, that Apple isn’t actually making it better for you, people, keeping things closed, and that you are waiting for things like Swift Open-Source and Xcode 7 to be finalised before making decisions.

        In any case, keep up the good work.

        • Anastasia Kazakova says:

          Thanks for your support and understanding.

          We know that Xcode 7 and especially Swift 2.0 will become crucial in a month or so and understand that AppCode should support them asap. However we’ve decided to finish our current work on Swift intellisense features in AppCode 3.2 based on more stable Swift 1.2 release and Xcode 6.4 (like quick documentation, override/implement, Swift debugger, a lot of resolve issues, etc.). And then to start further work and introduce Swift 2.0 ( and Objective-C generics ( In general the work on Xcode 7 has already started. We do hope to have new features support quite soon.

  5. Tropper says:

    Should be fixed in this EAP? Because YouTack says so but it seems not be the case. It’s different now – but far from fixed… :-/

    • Anastasia Kazakova says:

      Should be. If it’s not for you, please, leave a comment with some sample in the corresponding issue.

Leave a Reply

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