AppCode 2.0 EAP build #126.206

Hey guys,

once again we have some new features for you for a great beginning of the week, some of them are long-awaited, some are just cool. Here’s the list:

  • Navigation between tests and classes (Cmd+Shift+T).

  • Surround code with -respondsToSelector: (Alt+Cmd+T).

  • New code generation options: -initWithCoder: and -encodeWithCoder: (Cmd+N).

  • Analyze Crash Report action that symbolicates crash reports and adds links to actual code.

  • New code inspection: “Symbol is assigned but never accessed”.

Additionally we have sped up the reindexing upon external project changes, fixed a number of issues you have reported, plus we continue working on memory usage optimization.

You can download the latest build from EAP page. As usual, issue reports and feature suggestions are very welcome in the tracker.

Develop with Pleasure!
The AppCode Team

This entry was posted in Announcement. Bookmark the permalink.

16 Responses to AppCode 2.0 EAP build #126.206

  1. Nikita says:

    extremely slow download

  2. Dmitriy Isaev says:

    Thanks for crash reports, good job! Aren’t you planning to introduce automatic dSYM management? I think it will be great, just to choose the correct build (UI like in VCS “Browse changes”) and AppCode reads the stored dSYM for that build.

  3. Miķelis Vindavs says:

    I really regret I installed this EAP.
    I have spent the last 2+ hours trying to figure out why my app doesn’t work. Turns out AppCode has decided to completely ignore changes in a file and compiles some old version where I had added an early return for debugging.
    Breakpoints don’t work in the file and changing something results in runtime errors. Breaking in a function that gets called from said file shows that the stacktrace is completely misaligned with the actual lines.

    I’ve invalidated caches, cleaned the project, nothing helps. It works fine in xcode. What should I do?

    • Anton Makeev says:

      Miķelis,
      we are sorry that you are experiencing problems with AppCode; though, they are unlikely to be introduced by this very build – we haven’t changed anything regarding compilation.
      We recommend you to, first, make sure that your project is correctly configured and that you have ‘Build before launch’ enabled in the corresponding Run Configuration. If the problem persists, check the build log (Messages tool window, Show Build Log button) – are the files you expect being compiled?
      If you are unable to resolve the problem, please file a bug report – we’ll investigate it further.

      • Miķelis Vindavs says:

        Thanks for the response. It turned out to not be AppCode’s fault, but what seems to be a glitch in the simulator – I think it just launched an old binary even after recompiling.
        With that out of the way, this is the most amazing build yet! Looking forward to the 2.0 release.

  4. George Cook says:

    great build guys – LOVE THE NEW APP ICON.. looks much more mac ish.. previous one had a firefox-like color scheme.

    nice attention to detail :D

  5. Lee says:

    This EAP has extremely bad performance. The app is very sluggish and during editing becomes non-responsive.

    • Anton Makeev says:

      Lee, please check the corresponding issue report for a workaround: OC-6339.
      If it doesn’t help, please take and attach a CPU snapshot as described in the issue.

      • Lee says:

        Which workaround are you referring to? It sounds like there are a number of suggestions on that thread.

        Is it the one related to memory usage?

        • Lee says:

          I tried the memory workaround but as soon as I start typing CPU is up to around 80%.

          I’ll try the next EAP when it comes out – this one at least looks nice visually.

          • Anton Makeev says:

            You need to increate max memory limit (Xmx option).
            If after increasing Xmx you still have CPU issues, please take a CPU snapshot and attach it to a new issue report.

            Please keep in mind that the main purpose of EAP is to collect feedback and fix the emerging problems; and we expect collaboration from our EAP users.

  6. Pingback: WebStormで実装ファイルとテストファイルを切り替えるのにJS Toolboxが便利 | Web scratch

Leave a Reply

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

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>