AppCode 3.1 released!

Posted on by Anastasia Kazakova

Hi everyone,

Great news for all of us: AppCode 3.1 is officially available! You will especially like it if you’ve already started developing with Swift. AppCode will help you with many basic tasks in the smartest way possible.
AC31_970x250

Start with creating a Swift-based project or just a new Swift file (select New | File from Xcode Template…) in your existing project. As you code in Swift, autocompletion for types, methods and variables will help speed up the process. To follow your preferred formatting rules, configure them in Editor | Code Style | Swift:
code_formatting

The on-site preview will highlight the changes. As for colors & fonts, you can use the pre-defined color scheme for Swift or configure a new one in Editor | Colors & Fonts | Swift.

AppCode makes it possible to navigate across the source code using the code structure rather than plain scrolling. You can find your way in the source code using declarations/definitions, class/file/symbol name, or current file structure. All these navigation features work for Swift as well. For example, bring up the current file structure by pressing Cmd+F12 and select the function or variable to go to:
file_structure

You can also use search features in Swift code, for example highlight all usages of the symbol at the caret within a file, or find usages across the project (Alt+F7):
find_usages_and_highlight

Famous for its code refactorings, AppCode 3.1 brings to Swift the most popular and widely-used refactoring: Rename (Shift+F6). Use it to rename variables, constants, functions, type names or classes, and rest assured that AppCode will update all the usages across the entire code base for you:
rename_variable

To support Swift interoperability with Objective-C, AppCode 3.1 resolves Swift symbols from Objective-C code and provides find usages, navigation and other coding assistance features for Swift. When writing unit tests in Swift with AppCode 3.1, you can run all tests in one go or just toggle a single one, explore statistics, navigate to source, and rerun tests from the dedicated results view.

And that’s not all! Find details about Inline Variables View in the debugger, use Smart Backspace and more. For more details see our What’s New page, especially since version 3.1 brings other improvements and fixes, including stability and performance optimizations.

As we said before, we’ll continue to enhance Swift functionality to deliver more goodies for you to use in the following 3.1.x updates.

Please note that system requirements have slightly changed: the lowest supported OS X version is now 10.9, and the lowest supported Xcode version is 6.1.

Finally, note that this update is free for all AppCode users with an active license! To download the release build, please visit our site.

We want to thank everyone who has evaluated our Early Access Program builds. Your feedback and comments were really helpful in making this release as useful as possible.

Develop with pleasure!
JetBrains AppCode Team

Comments below can no longer be edited.

20 Responses to AppCode 3.1 released!

  1. Alex Tang says:

    December 10, 2014

    This is great news!

  2. dcty says:

    December 11, 2014

    https://www.youtube.com/watch?v=3qSRoGXl-ZY
    the problem when appcode full screen

    • Anastasia Kazakova says:

      December 11, 2014

      Thanks, we know about the problem – https://youtrack.jetbrains.com/issue/IDEA-131593. Unfortunately, this is a java 6 problem, and java 7,8 is not good as well because of some problems. We are customizing the JDK right now to provide you with the acceptable solution.

  3. Ben says:

    December 11, 2014

    You guys are awesome!

  4. Daniel says:

    December 11, 2014

    Congratulations! I’m really enjoying 3.1 – thanks for the great work 🙂

  5. Andriy says:

    December 11, 2014

    Thanks for the great job.
    When are you planning to add autocompletion for class properties, Initializers, method parameters and etc. ?

    • Anastasia Kazakova says:

      December 11, 2014

      yes, sure. We’ll continue with Swift support and provide update with improvements.

  6. Bimawa says:

    December 11, 2014

    I love you JB!!!!

  7. John says:

    December 12, 2014

    Any timeline when you will support full autocompletion?

    I have the same concern as Andriy.
    Its pretty inconvenience to use AppCode if there is no full featured autocompletion for e.g. initialisers.
    Thanks!

    • Anastasia Kazakova says:

      December 12, 2014

      What exactly is not working in autocompletion for you? Could you please list all the cases. Most of them should work now.

    • Anastasia Kazakova says:

      December 12, 2014

      Some cases that are not ready yet are listed in subtasks here: https://youtrack.jetbrains.com/issue/OC-10939

      • John says:

        December 12, 2014

        basics like: aCoder. … e.g. aCoder.encodeInterger/Bool
        or super. …, or view. … view.addGestureRecognizer(…), myLable. .. (myLable.text)
        as well as own classes like Foo(position: CGPosition). The Class name “Foo” gets completed, but its initializers/methods are not suggested. In Xcode it works fine.
        To sum up only the variables and class names get completed, any methods or initializers don’t. So the question should be where exactly does autocompletion work. At least it seems that way for me atm. Don’t get me wrong, I really would like to switch back to AppCode. But this is a critical feature of any IDE. Maybe I am doing something wrong?

        • Anastasia Kazakova says:

          December 13, 2014

          Please, check this tree https://youtrack.jetbrains.com/issue/OC-10408 for the non-ready cases. There are some known problems with ‘super’, ‘this’ and some super class’s methods. If you meet any other cases please report them to us. We hope to improve this in the next updates.

    • Andriy says:

      December 12, 2014

      As Robert F. Beeger mentioned here https://youtrack.jetbrains.com/issue/OC-11161, AppCode without this feature is not more than a nice “refactoring” tool.

      Do you have any estimates for finishing these feature?

      • Anastasia Kazakova says:

        December 13, 2014

        We do hope to improve in one of the next updates.

        • Andriy says:

          December 13, 2014

          I hope it will be soon, I will not suffer working in xCode too long 🙂 Best regards to all member of JetBrains.

  8. Raphael says:

    January 12, 2015

    Hello AppCode Team! I love your IDEs, and I used IntelliJ and AppCode for years now. They are definitively the best and most intelligent IDEs on the market.

    But I currently work with Xcode for my Swift projects. Its a pain in the ass but its currently the more advanced and better IDE for Swift.
    I really hope that you implement full auto completion and all the other smart tools (that ObjC has) for Swift soon. I’m so looking forward to it!

    • Anastasia Kazakova says:

      January 12, 2015

      Thanks. We’ll do our best.

  9. huynh van sen says:

    February 27, 2015

    Why Not video demo how IBAction event Button with StoryBoard, OutLet UIText field.
    I try Using AppCode >Button I don’t how IBaction UIButton for event TouchUP inside

Subscribe

Subscribe to product updates