AppCode 2016.3 EAP, build 163.6957.25

Stanislav Dombrovsky
Important note: build 163.6957.11 is no longer available because of the critical issue with completion in mixed Objective-C/Swift projects. Please, use 163.6957.25 build instead which contains fixes mentioned below and does not have such problems with completion. We sincerely apologize for this issue.

New AppCode 2016.3 EAP is available for download on our confluence page. If you are using previous 2016.3 EAP build, the patch update is also available.

This build brings fixes for the following issues:

  • Problems with Swift operators formatting (OC-12352OC-12353)
  • Incorrect indentation for catch on a new line (OC-14278)
  • Issue when typealias with access modifier was incorrectly formatted (OC-14317)
  • Resolve issue with ()->Void type (OC-14298)
  • Parser error for function type parameter with label and underscore (OC-14343)
  • Problem with building project after switching Xcode toolchain (OC-14188)
  • Issue with Objective-C string concatenation (OC-14308), which also caused parser errors when using XCTAssert and some other macros
  • Problem with run configurations specified in Before launch section (OC-14017)

The following Swift 3 support features are included into this build:

For the full list of fixes please see the release notes.

Your AppCode team
JetBrains
The Drive to Develop

Comments below can no longer be edited.

15 Responses to AppCode 2016.3 EAP, build 163.6957.25

  1. Bill says:

    October 26, 2016

    Does this version work with Xcode 8.1 GM?

    • Tatiana Shabaeva says:

      October 27, 2016

      This EAP doesn’t include the fix for running/debugging apps (https://youtrack.jetbrains.com/issue/OC-14191) which should be available in next week’s EAP. Otherwise it should work. Please get back to us if you encounter any issues.

      • Bill Atkins says:

        October 27, 2016

        I get the message “You are using Xcode 8.1. AppCode currently does not support this version. We recommend that you switch to Xcode 8.0.” and the Xcode screen in Preferences says Xcode 8.1 is not supported. Is that just because of the simulator issue?

        • Tatiana Shabaeva says:

          October 27, 2016

          Partially, yes. And also because we normally don’t have official support for new Xcode versions until they go out of ‘beta’ stage. But since Xcode 8.1 GM is out, and as soon as we’re sure there are no other major issues, we’ll remove the warning.

          • Bill says:

            October 27, 2016

            Got it – thanks

  2. leviathan says:

    October 28, 2016

    Xcode 8.1 is out …. and AppCode does not support Xcode 8.1 – seriously ?!
    Soo, I have to manually install Xcode 8.0 again to use AppCode.
    That’s the way it’s supposed to work?

    • Stanislav Dombrovsky says:

      October 28, 2016

      >Xcode 8.1 is out …. and AppCode does not support Xcode 8.1 – seriously ?!

      The only reason for now is the issue with run/debug on the simulator/device in Xcode 8.1 appeared after “yet another change” in the released version. It’s the common situation that run/debug works with the Xcode betas, and next it stops working in the released one because of some changes in LLDB bundled in Xcode/something else.

      We are working on this issue right now and hopefully it will be resolved in the one of upcoming 2016.3 EAPs.

  3. Dev says:

    October 28, 2016

    I’ve stayed away for a month or two, thought I’d check things out with AppCode again. It still uses tons of CPU when the app is in the background (and it’s not even indexing), the SourceKit errors still don’t show up in the editor, OC-13714 is still not fixed. I’m sad 🙁

    Hopefully you can get to these problems when the Swift 3 work is complete.

    • Stanislav Dombrovsky says:

      October 28, 2016

      Unfortunately, CPU usage and even showing SourceKit errors could be related to the resolution performance. For now the main part of this really huge task is in internal testing and the current plan is to include it into the release.

      • Dev says:

        October 28, 2016

        That’s great news! I’ll keep watching the 2016.3 EAP updates then. Thanks, Stanislav!

      • Francis says:

        October 28, 2016

        Does this fix address performance issues related to code completion and resolve?

        • Stanislav Dombrovsky says:

          October 28, 2016

          OC-13714 is the first big step here, because code completion, navigation, find usages, even code highlighting are built around the resolution engine, almost all functionality could be affected. We are currently checking possible side-effects and regressions, which unfortunately can appear because of the amount of changes.

          • Francis says:

            October 28, 2016

            I’m excited to see some progress on this. I’ve had to jump the AppCode ship for the time being due to incredibly slow code resolve and am really looking forward to coming back onboard.

  4. Dusan Klinec says:

    November 1, 2016

    What is pls an expected release date of new EAP supporting XCode 8.1? We would highly appreciate it. Thanks!

    • Stanislav Dombrovsky says:

      November 1, 2016

      Fix for running/debugging applications should be available this week.

Subscribe

Subscribe to product updates