AppCode
CLion
DataGrip
GoLand
IntelliJ IDEA
MPS
PhpStorm
PyCharm
Rider
RubyMine
WebStorm
Toolbox App
.NET Tools
ReSharper C++
Space
TeamCity
Upsource
YouTrack
HubAppCode 3.2 EAP, build 141.2391
Hi everyone,
Today AppCode 3.2 EAP 141.2391 is available for download. The patch update is also available if you are using previous 3.2 EAP build.
This build introduces mostly bugs/regressions fixes and small improvements, like unresolved Swift parent class members used in Objective-C code (OC-12245), incorrect unused code inspection (OC-12238), regression with block parameter autocompletion (OC-12233) and Inline Variables View for Swift now working correctly.
Please, note that in case you have custom appcode.vmoptions file (for example, you were increasing memory to fix some performance issues) EAP build without custom bundled JDK won’t run, until you delete this custom appcode.vmoptions and copy (and update if you still need it) an actual version from AppCode.app/Contents/bin/.
The full list of fixes can be found in our tracker.
Develop with pleasure,
The AppCode Team
tigor says:
August 11, 2015What about the support of iOS 9 (beta)?
Anastasia Kazakova says:
August 12, 2015What exactly do you mean? You can try Xcode 7 with AppCode, though some issues are still present since Xcode is in beta now.
tigor says:
August 14, 2015Aha!
Just for info: if we set Xcode to version 7.0 (7A176x) , then our sources become overflowed with warnings (to many to handle :), but – the app (deployment target is iOS 8.0+) still compiles and runs without problems. Program is written in ObjC. There is no warnings if Xcode 7.0 (7A176x) is used directly.
Anastasia Kazakova says:
August 14, 2015Since Xcode 7 is still in beta, AppCode doesn’t officially support it.
Warning with Xcode 7 in AppCode can be caused by unsupported Objective-C generics: https://youtrack.jetbrains.com/issue/OC-12086, or nullability in Objective-C: https://youtrack.jetbrains.com/issue/OC-12146 (it’s now supported for Xcode 6.4 only).
sacred says:
August 11, 2015AppCode since 3.2 eap became completely unusable. Almost all project mark as red, but build finished successfully. But it’s rather inconvenient.
Anastasia Kazakova says:
August 12, 2015We are unaware of such problems, so some prj sample will be very useful to investigate and fix problems. Could you please help us with some?
Fabian says:
August 12, 2015Same here
Anastasia Kazakova says:
August 12, 2015Any prj sample to reproduce you can share?
Pit says:
August 12, 2015I have the same problem from time to time, a restart usually fixes this (for the time being). I have the feeling it happens when switching branches (maybe only when the project file is different after the switch).
I think it is not really tied to a specific kind of project.
Anastasia Kazakova says:
August 12, 2015Ok, can you then described details scenario and what is going wrong in details? The problem is that we currently can’t get it reproduced.
Jason Hanson says:
August 14, 2015I have this problem too. It happens specifically when
1. Running in the simulator
2. And halted on a breakpoint
3. Switch branches with SourceTree to a branch with very different version of the code
–> See red everywhere till I restart AppCode
Anastasia Kazakova says:
August 14, 2015Interesting scenario, thanks, we’ll try to investigate.
Could you please also try and make CPU snapshot (https://intellij-support.jetbrains.com/entries/29983118-Reporting-performance-problems) and thread dump (https://intellij-support.jetbrains.com/hc/en-us/articles/206827507-Getting-a-thread-dump-when-IDE-hangs-and-doesn-t-respond) from that case, so that we can have a look what IDE is trying to do there and what’s is maybe missing.
Anastasia Kazakova says:
August 16, 2015By the way, which Xcode version do you use?
Fabian says:
August 12, 2015“This build introduces mostly bugs…” haha 🙂
Mark says:
August 16, 2015Will AppCode 3.2 support Swift 2.0 syntax? Currently constructs like “do..catch” and “try” are flagged as syntax errors. There may be others.
Is there a list anywhere of what’s supported and what’s not?
It’s confusing when valid constructs are marked as errors.
Anastasia Kazakova says:
August 16, 2015Swift 2.0 is not supported yet, and not going to be included into 3.2 version. You can follow this: https://youtrack.jetbrains.com/issue/OC-12029 to know about the progress and subtasks.
Chris says:
August 19, 2015No Swift 2.0 in Appcode 3.2?
Seems a little odd, this decision. Xcode 7 GM is just around the corner, and breaks compatibility with Swift 1.2 big time. So much effort on your part is put into releasing a major stable version (which brings serious improvements, like resolution of external frameworks), just to make it last for 1 month?
Don’t get me wrong, the work put into AppCode is phenomenal. It just seems a strange move to not support Swift 2.0 early. On the other part, I do understand, that Apple isn’t actually making it better for you, people, keeping things closed, and that you are waiting for things like Swift Open-Source and Xcode 7 to be finalised before making decisions.
In any case, keep up the good work.
Anastasia Kazakova says:
August 20, 2015Thanks for your support and understanding.
We know that Xcode 7 and especially Swift 2.0 will become crucial in a month or so and understand that AppCode should support them asap. However we’ve decided to finish our current work on Swift intellisense features in AppCode 3.2 based on more stable Swift 1.2 release and Xcode 6.4 (like quick documentation, override/implement, Swift debugger, a lot of resolve issues, etc.). And then to start further work and introduce Swift 2.0 (https://youtrack.jetbrains.com/issue/OC-12029) and Objective-C generics (https://youtrack.jetbrains.com/issue/OC-12086). In general the work on Xcode 7 has already started. We do hope to have new features support quite soon.
Tropper says:
August 17, 2015Should https://youtrack.jetbrains.com/issue/OC-12238 be fixed in this EAP? Because YouTack says so but it seems not be the case. It’s different now – but far from fixed… :-/
Anastasia Kazakova says:
August 17, 2015Should be. If it’s not for you, please, leave a comment with some sample in the corresponding issue.