AppCode 3.3.2 Update is Out

Stanislav Dombrovsky

Hi everyone,

We are glad to announce that AppCode 3.3.2 bug-fix update is available for download.

new_splash_33

And if you’ve noticed our new splash, it’s not only a new picture – it’s a whole makeover! Read about the new JetBrains branding in our company blog.

Let’s take a quick look at the features and improvements added into this update.

Swift

  • “Surround with do/catch” and “Propagate call error with try”  quick-fixes are available for throwing functions as well as parser improvements for constructions with rethrows keyword
    Surround with do/catch
  • Quick-fix added for splitting multiple variable declarations into separate ones

Swift debugger

This update delivers one of the long-awaited debugger features: support for watches and expression evaluation.

evaluate_expression@2x

Now you can view values of variables added to Watches tool window, evaluate Swift expressions using Evaluate expression… action (Alt+F8), and benefit from code completion for both cases while debugging your Swift projects.

Apple TV simulators

We’ve added support for Apple TV platform which includes running and debugging tvOS apps on Apple TV simulators (note, that running applications on tvOS device is currently not possible due to this issue).

tvOS simulators

Search and navigation

Objective-C and Swift project symbols are now included into Search Everywhere results:

search_everywhere@2x

And more 

  • Improved performance in loading Swift modules after initial indexing and building of symbols (OC-12345)
  • A number of stability fixes for project model loading

The full list of fixes and improvements can be found here.

In future versions we will continue to work on features from our roadmap, improvements in loading Swift modules and overall performance of the AppCode.

Stay tuned and don’t miss the next EAP launch!

Develop with pleasure,
The AppCode Team.

Comments below can no longer be edited.

20 Responses to AppCode 3.3.2 Update is Out

  1. Bill A says:

    December 10, 2015

    I get this message when starting it:

    Unsupported JVM
    Non-Apple Java is not supported, please install it from Apple’s support page

    and all the fonts are blurry. This wasn’t the case in the latest EAP.

    Is there still an option to download the custom JDK or has something changed there?

    • Stanislav Dombrovsky says:

      December 10, 2015

      Installer includes custom JDK, so it should work without any additional downloads. Did you select non-bundled JDK before you updated? Do you update from 3.3.1 or other build?

      • Bill A says:

        December 10, 2015

        Hi Stanislav,

        I downloaded the DMG file from the link and dragged to Applications.

        • Bill A says:

          December 10, 2015

          Hmm it looks like the link in the blog post goes to AppCode 3.2

          • Stanislav Dombrovsky says:

            December 10, 2015

            Bill, sorry, which link in the blog post do you mean?

          • Bill A says:

            December 10, 2015

            This post we’re commenting on. The “available for download” link goes to https://www.jetbrains.com/objc/download/ which points to AppCode 3.2

          • Bill A says:

            December 10, 2015

            I clicked “Previous Versions” on that page and grabbed 3.3 from there. That version works properly with respect to the bundled JDK. I think the Download page just needs to be updated.

            • Stanislav Dombrovsky says:

              December 10, 2015

              Looks like a cache issue. Please, use this link for the moment

  2. Florent Pillet says:

    December 10, 2015

    Thanks, AppCode team! Hopefully Swift support is progressing because I’m sorry to report that I had to go back to Xcode for Swift 2 development – Language support in AppCode is just incomplete, code completion barely works and I found out that overall I was spending more time writing code in AppCode than in Xcode because the IDE was not helpful in spotting code that would not compile.

    Anyway keep up the great work, I can’t wait to go back to using AppCode full time (and will definitely give a chance to 3.3.2 to show off). I miss the environment very much.

    • Stanislav Dombrovsky says:

      December 10, 2015

      We will do our best – better language support is on the way.

  3. Alex Manarpies says:

    December 10, 2015

    Hi there,

    Release is working well, except for one thing: it seems AppCode is auto-generating block implementations wrong for me. For example, it generates this (syntax error in ObjC — using ReactiveCocoa):

                    ...
                    subscribeCompleted:^(void v) {
                        [self.tableView reloadData];
                    }];
    

    While it should be:

                    ...
                    subscribeCompleted:^{
                        [self.tableView reloadData];
                    }];
    

    AppCode 3.3.1 did not exhibit this behavior.

    Keep up the good work!

    • Stanislav Dombrovsky says:

      December 11, 2015

      It is related to this issue and should be fixed in the upcoming EAPs for 3.3.3

      • Alex Manarpies says:

        December 11, 2015

        Okay, thanks. A minor issue I’ll put up with then.

  4. Anver Bogatov says:

    December 11, 2015

    Hi guys!

    I know this is to early to discuss, but – do you have any plans on expanding support of AppCode on other platforms? Since Swift became open sourced it is possible to run simple programs on Swift on Linux.

    • Stanislav Dombrovsky says:

      December 11, 2015

      We will look on how Swift developer community will grow on Linux and will decide it later.

      • Anver Bogatov says:

        December 11, 2015

        Thank you for the answer, Stanislav!

  5. Stewart says:

    December 11, 2015

    Good update overall, but disappointed that this bug isn’t fix yet:
    Swift debugger: “value is not of a pointer type”

    Any time frame for it being fixed? IMO, its quite a show stopping bug.

    • Stanislav Dombrovsky says:

      December 11, 2015

      We are already working on it, so it should be fixed soon.

      • Eugene M says:

        February 4, 2016

        any updates on this? would really like this to get fixed, please.

        • Stanislav Dombrovsky says:

          February 4, 2016

          We are working on this problem right now and the corresponding issue is already ready to test. Not this week, but the most probably next week you will be able to check it in thew new EAP.

Subscribe

Subscribe to product updates