Moving on to AppCode 2018.3

Hi everyone,

It’s time to share our preliminary plans for the next release (note, that not all the features listed below may make it into AppCode 2018.3).

  • Swift:
    • Swift 4.2 and 5.0
    • Generate (init, description, enum cases, etc.)
    • Type hierarchy
  • Objective-C:
    • Issues related to header maps support (OC-15000)
  • Resolve performance and correctness (OC-17449)
  • Debugger:
    • Ability to debug app extensions (OC-10697)
    • Swift completion in LLDB console (OC-11180)
  • Problem with the resolve of the EFFECTIVE_PLATFORM_NAME property (OC-6170) that leads to various other problems, such as false warnings and errors in the code analysis for Objective-C/C++/Swift

We plan to open the AppCode 2018.3 EAP around mid-September. If you have any questions, feel free to ask them in the comments below.

Your AppCode team
The Drive to Develop

Comments below can no longer be edited.

4 Responses to Moving on to AppCode 2018.3

  1. Avatar

    ssdf says:

    August 24, 2018

    Will follow CLion’s lead and move away from custom Jetbrains parser?

    • Stanislav Dombrovsky

      Stanislav Dombrovsky says:

      August 24, 2018

      We have clang integrated as a linter for showing warnings/errors for years (specifically, clang-analyzer), so currently CLion follows our approach. Right now it’s not clear if it’s possible to use it for any other code-related functionality in the IDE, because the performance impact is not clear.

  2. Avatar

    Marcel Bradea says:

    September 3, 2018

    Fantastic to see some focus on the generators and type hierarchy.

    These are huge time savers in other JetBrains IDEs (Rider/Resharper) and have been missed in the Swift world.

    Also, a big up for app extensions. Would be great to see these make it in.

  3. Avatar

    Olaf Panz says:

    September 15, 2018

    Whats about CoreDate support? CoreData generated classes are still marked as error.

Discover more