AppCode 2020.2 Roadmap

Stanislav Dombrovsky

Hi everyone!

It’s time for us to share our plans for AppCode 2020.2:

  • Add Xcode 12 and Swift 5.3 support.
  • Provide support for Xcode projects that use Swift Package Manager dependencies.
  • Enhance SourceKit-based completion.
  • Implement the Change Signature refactoring for Swift.
  • Improve caching speed and eliminate as many freezes as possible.

If you have any questions, please ask them in the comments below.

Your AppCode team
JetBrains
The Drive to Develop

Comments below can no longer be edited.

12 Responses to AppCode 2020.2 Roadmap

  1. Juan says:

    April 30, 2020

    Hi, do you have plan for these requests?

    https://youtrack.jetbrains.com/issue/OC-18314
    https://youtrack.jetbrains.com/issue/OC-18544

    • Stanislav Dombrovsky says:

      May 7, 2020

      No, we do not have such plans.

      • Juan says:

        May 30, 2020

        It’s a pity, things like that are the things that still keeping me and many others from giving AppCode a serious go.

  2. Marcel Bradea says:

    May 1, 2020

    Would you guys elaborating on ‘Enhance SourceKit-based completion’?

    We’ve noticed recently that completion is blockingly slow (ie: doesn’t work for usually long periods at a time) – to the point that we’re switching back to Xcode to see what comlpetion drop-down options exist on a regular basis.

    This is extremely unproductive and interruptive to development flow.

    Or would this more be part of the ‘Improve caching speed and eliminate as many freezes as possible.’ focus area?

    • Stanislav Dombrovsky says:

      May 7, 2020

      Would you guys elaborating on ‘Enhance SourceKit-based completion’?

      That’s about using SourceKit during indexing and caching to provide completion – further improvements.

      We’ve noticed recently that completion is blockingly slow (ie: doesn’t work for usually long periods at a time) – to the point that we’re switching back to Xcode to see what comlpetion drop-down options exist on a regular basis.

      Would be great to have a CPU snapshot from 2020.1 to understand why the code completion is slow (if it’s not yet there in one of the tickets in our tracker).

  3. Jindrich says:

    May 12, 2020

    Please, please, focus on speed. The indexing times are really bad, something like 20 minutes after opening project. Why is needed to reindex everything again and again? For example Apple frameworks or sources that I didn’t touched?

  4. Bruce says:

    May 14, 2020

    I am disappointed that performance is not the first bullet point. 2020.1 has been awful:

    1) 200-400% CPU usage when indexing and it often takes a long time.

    2) Serious memory leaks. I have seen RAM use climb as high as 32GB.

    3) Code completion seems to stop working often. Doing a ‘Find Usage’ will often result in the dreaded ‘Resolving…’ dialog that never seems to finish.

    • Stanislav Dombrovsky says:

      May 15, 2020

      Hi Bruce, we’ve received your support request and our engineers will try to help. We are really sorry that after all our work on performance you still have problems, though for 2020.1 we’ve heard more positive feedback about the performance compared to previous versions. Looks like we need to take a look at your project, because it’s really big and complex.

      In any case, please, note that the order in this blog post is not a priority – it’s just an order of tasks, where performance issues still have a higher priority compared to almost any bug fixes or features and the same priority as Xcode/Swift support.

  5. Marcel Bradea says:

    June 10, 2020

    What is the reason why Combine framework does not seem to be resolved? (ie: no auto-complete etc.)

    Is this not yet supported due to the lack of above-mentioned Swift 5.3 support or is this a bug that’s potentially caused by something else in our project setup?

    Our min SDK is iOS 13, our codebase has been all updated to Swift 5 (except some Cocoapod libs which are still on 4.x)

    • Stanislav Dombrovsky says:

      June 10, 2020

      Combine should work and be resolved. As example – it is resolved here, there is a completion for that in 2020.1.4. If it’s not resolved in your project, we need a minimal example of such a situation to reproduce it on our side (and also it makes sense to check if it’s a cache issue using File | Invalidate Caches / Restart)

      • Marcel Bradea says:

        June 10, 2020

        Thanks for the fast turnaround Stanislav.

        I just checked whether it’s the caches and still doesn’t resolve.
        I was worried this might be an unexpected bug…

        Not sure the level of effort needed to set up a project to reproduce in. Any best practices on getting this type of info from teams? (considering code IP etc.)

        • Stanislav Dombrovsky says:

          June 11, 2020

          I think first it makes sense to check if the sample project I’ve mentioned works on your side. If it works, the only way to analyze such issue is usually to take a look at the actual project during the remote session. I’m ready to do it (please, drop an email to stanislav.dombrovsky at jetbrains.com)

Subscribe

Subscribe to product updates