AppCode 2016.3 Release Candidate

Posted on by Stanislav Dombrovsky

Hi everyone,

Today we are glad to announce that AppCode 2016.3 Release Candidate (build 163.8703.1) is available for download. That means 2016.3 release is just around the corner!

The following issues are fixed in this build:

  • Displaying Swift instance variables in the debugger (OC-14513)
  • Problem with SourceKit inspections in some projects (OC-13999)
  • False spellchecker errors when using class member in C++ (CPP-8185)

We appreciate your feedback and comments, and if you find any bug at all, please file an issue in our tracker.

Note, that this RC build does not require an active AppCode subscription. The full list of fixes and improvements can be found here.

Your AppCode team
JetBrains
The Drive to Develop

Comments below can no longer be edited.

17 Responses to AppCode 2016.3 Release Candidate

  1. Matt says:

    November 23, 2016

    Looks like method calls/instance variables to classes that extend from a generic class aren’t correctly styled/discovered/autocompleted.

    java.lang.Throwable
    at com.intellij.openapi.diagnostic.Logger.assertTrue(Logger.java:168)
    at com.jetbrains.swift.codeinsight.resolve.reference.SwiftSubstitutionCache.a(SwiftSubstitutionCache.java:241)

    • Stanislav Dombrovsky says:

      November 23, 2016

      Could you please submit a sample project to our tracker, so we could investigate the problem?

      • Matthew Reilly says:

        November 25, 2016

        Sure thing! Great work so far, love AppCode.

  2. Максим Наумов says:

    November 25, 2016

    “To support Swift interoperability with Objective-C, AppCode also resolves Swift symbols from Objective-C code and vice versa, providing find usages, navigation and other useful features throughout your whole codebase.”

    This is a lie.

    Year passing by, and I keep getting warnings like this in my mixed project:
    Incompatible pointer types ‘id’ and ‘AnyObject *’
    Taking boolean from pointer ‘Bool *’ without a cast

    • Stanislav Dombrovsky says:

      November 25, 2016

      This issue is not related to the symbol resolution – it’s related to the CLang inspections integration and it seems like somewhere inside generated headers for the mixed code Xcode simply disables the warning about incompatible types, so CLang just skips such code. But it should not affect the resolution or navigation. Does it work for you?

      • Максим Наумов says:

        November 28, 2016

        The only generated header I’m aware of is -Swift.h. And the types there are correct. For example, a Bool property of a swift class is declared as BOOL, not Bool * etc.
        As to your question, what do you mean by ‘it’?

        • Stanislav Dombrovsky says:

          November 29, 2016

          Looks like I was wrong with the CLang, sorry for that. It looks like we have an issue with our CLang integration which currently produces this warning. Still, it should not affect the resolution of symbols on the same line, where such warning is shown – you should be able to resolve entities in the code, e.g. navigate to the declaration for example.

          As a possible workaround before we fix this issue, you can disable the warning about incompatible types via Alt+Enter -> Press right arrow on the quick-fix action -> Select “Disable inspection”.

          • Максим Наумов says:

            November 29, 2016

            Thank you for the reply.

            However, there are more similar issues that prevent me from using AppCode with my mixed project, and disabling a dozen helpful inspections is not an option for me.

            • Stanislav Dombrovsky says:

              November 29, 2016

              Is it possible for you to share with us which issues you have in addition to mentioned above (by email or in tracker)?

  3. Igor Nikitin says:

    November 26, 2016

    So, what about of full Swift 3 support?

    • Stanislav Dombrovsky says:

      December 1, 2016

      We are working on it and it’s hard to give an exact date when all support features will be ready. Here you can see which features are in progress, which are already included into the release. We will try to share which features we plan to include into 2016.3.x updates later.

  4. Petr Tikhomirov says:

    November 28, 2016

    Trying out Appcode to replace Xcode
    One feature that is missing for me is auto method delegate methods (or any available methods) completion.

    Say, for instance when in UIViewController and start typing “viewDid” … Xcode auto-proposes to complete your query with viewDidLoad, viewDidAppear etc…
    If UIViewController conforms to UITableViewDelegate / UITableViewDataSource – typing “tableView” … auto suggests the available delegate methods and a bunch of stuff associated with tableView.

    Is this feature available in Appcode? Maybe I am missing something?

    • Stanislav Dombrovsky says:

      November 28, 2016

      This feature is not implemented yet. You can use Override/Implement (^O/^I) to override/implement multiple methods at once.

  5. Ahmet Karalar says:

    November 30, 2016

    In this and RC2 (as well as the old builds for 2016.3 EAP), even after processing modules phase finishes, SourceKitDaemon uses too much cpu (probably on the main thread), so much so that generally the computer and especially Alfred is very unresponsive, and this is the only reason I can’t switch to AppCode from Xcode for swift 3 🙁 Are you aware of this problem and is it expected to be fixed in the near future? I really miss AppCode since I took on a Swift 3 project.

    • Stanislav Dombrovsky says:

      November 30, 2016

      Could you please submit your project to our tracker, so we could check if the problem is on our side?

      • Ahmet Karalar says:

        November 30, 2016

        I can’t upload the project but is there any other way I can help?

        • Stanislav Dombrovsky says:

          November 30, 2016

          Could you please try the following:

          1. Close AppCode, close all Xcode instances, kill all SourceKitDaemon instances.
          2. Start AppCode and reproduce the situation (all symbols processing steps should be finished, no progress at the bottom, high CPU usage from SourceKitDaemon).
          3. Paste #com.jetbrains.swift.sourcekitd.SourceKitService into Help->Debug log settings, press ok and wait for 5 minutes so logs could be recorded.
          4. Help -> Show log in Finder -> please, attach idea.log to the ticket in our tracker.

Subscribe

Subscribe to product updates