New AppCode 2016.3 EAP: Xcode 8.1 support and Create from Usage in Swift

Posted on by Stanislav Dombrovsky

Hi everyone,

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

In this build we fixed critical issue with running/debugging iOS applications on simulator and device with Xcode 8.1 set in AppCode preferences. Currently it’s the only issue related to this particular Xcode version support, so in case you see any other serious issues, please let us know about them.

The most important new feature included in this build is the first part of Create from usage feature for Swift. You may know that similar ability is available in Objective-C/C/C++ in AppCode – you can create variables, constants, methods, functions and classes just by pressing ⌥⏎ on the unresolved entity:

Create from usage in Objective-C

Now this functionality is also available for Swift functions, methods, variables, constants and properties. Try using the function which does not exist, press ⌥⏎ and choose if you want to create the global function or class method:

Create function from usage

Press  to generate the function/method stub and change parameter names or return type if needed:

Generate function

Try using the non-existing variable, press ⌥⏎, select the proper scope and press  to create it automatically:

Create variable from usage

Create from usage functionality for new types (classes/structs/etc) is still in progress.

That’s it! 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.

6 Responses to New AppCode 2016.3 EAP: Xcode 8.1 support and Create from Usage in Swift

  1. Tropper says:

    November 3, 2016

    This one is really a huge step!

  2. Matt says:

    November 3, 2016

    None of the inspections seem to work for me. I get a yellow balloon if I focus on it, though. No red underlining, sadly.

    • Stanislav Dombrovsky says:

      November 3, 2016

      Currently there is a not completely clear issue with the SourceKit inspection engine (which actually shows such highlighting in case of some unresolved entities) we are currently working on, which can cause such behaviour. Hopefully we will be able to fix it before the release.

      • Matt says:

        November 4, 2016

        Sweet thanks! Love AC, so much better than XCode.

  3. Ibrahima Ciss says:

    November 8, 2016

    Great job to the team.
    But I wonder when the imageLiteral syntax will be supported. It’s causing errors currently?

Subscribe

Subscribe to product updates