New AppCode 3.4 EAP, build 145.61

Posted on by Stanislav Dombrovsky

Hi,

New AppCode 3.4 EAP, build 145.61 is available for download. The patch update is also available if you are using previous 3.4 EAP build.

This build delivers the following improvements:

  • Starting from this version AppCode will use the same DerivedData directory location as Xcode (see OC-13193). It means that in case you have already built your project in Xcode, AppCode will not start compilation process from scratch and vice versa.
  • Variadic templates support in C++ (CPP-5465) which includes a lot of fixes, especially for problems in overload resolution and false positives in code analysis for related code constructs.

Important note: the issue with autocompletion is still present in this build and it should be fixed in one of the upcoming EAPs.

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

Your AppCode team
JetBrains
The Drive to Develop

Comments below can no longer be edited.

5 Responses to New AppCode 3.4 EAP, build 145.61

  1. Marcel Bradea says:

    February 26, 2016

    What does this mean for some of the following scenarios:

    1) Compilation is started in Xcode/Appcode and you switch to the other IDE and start another compilation before the first one completes? Because this used to run separately there was no chance for the IDEs stepping on each other’s toes. Is this still the case? Or will the developer have to take care to not start simultaneous compilations in the 2 IDEs?

    2) You can currently run a debug session in Appcode (on say the simulator) and a separate one in Xcode (on say your device). Is this scenario still supported? This is critical for apps that have real-time in them (Websockets, live messaging etc) and the regular development flow involves making a change on one device and ensuring data gets synched on another device properly (in real-time).

    PS: One the point of running multiple debug sessions at the same time, is there any way for this to work with two instances of Appcode instead of using one in Xcode and the other in Appcode?

    Cheers!

    • Stanislav Dombrovsky says:

      February 29, 2016

      Compilation is started in Xcode/Appcode and you switch to the other IDE and start another compilation before the first one completes?

      AppCode uses xcodebuild for building/cleaning the project, so this case is defined by xcodebuild behaviour. And in most cases it should be OK to start build from Xcode and AppCode simultaneously. Corner-case is cleaning your project from one IDE and building it in other IDE at the same time – if these 2 processes will be started simultaneously, build action will fail because cleaning your project requires build directory contents to be deleted. Another case is the project with 2 build phases, when one of them generates temporary sources and second deletes the same sources while building – and it’s quite similar to building and cleaning your project at the same time. But from my understanding these use-cases should not happen really often.

      You can currently run a debug session in Appcode (on say the simulator) and a separate one in Xcode (on say your device). Is this scenario still supported?

      Yes, this scenario is supported and changes described in the post will not affect it.

      One the point of running multiple debug sessions at the same time, is there any way for this to work with two instances of Appcode instead of using one in Xcode and the other in Appcode?

      If you want to use 2 different AppCode instances for the same project – it’s not possible. But you can run 2 debug sessions – one on device and another on simulator – from the single AppCode instance, and track debug changes on 2 different tabs in “Debug” tool window. Have you tried it?

    • Stanislav Dombrovsky says:

      March 3, 2016

      In addition to the previous comment – currently we found the issue that breaks this behaviour, so in this EAP build interaction between 2 IDEs will not work as expected. Sorry for that, we will try to fix it in upcoming EAP builds.

  2. Frank says:

    March 3, 2016

    Looking forward to a build with IDEA-151684 fixed 🙂

    • Stanislav Dombrovsky says:

      March 3, 2016

      It will be fixed in the EAP we are currently working on.

Subscribe

Subscribe to product updates