New AppCode 2017.1 EAP, build 171.3019.2

8 Responses to New AppCode 2017.1 EAP, build 171.3019.2

1. 

   Sofiane says:

   February 8, 2017

   Not sure if it’s my environment but this patch release has broken “building symbols” for me in my objC/swift project. It just hangs not even starting any progress and bumps the cpu usage to 700%. I believe this was addressed in a previous EAP patch release, but might have regressed…I’ve reverted to the EAP released on Feb 1 and it works just fine.

   • 

     Tatiana Shabaeva says:

     February 9, 2017

     Hi, thanks for the report. The problem is known and we’re working on the fix at the moment: https://youtrack.jetbrains.com/issue/OC-14947.

2. 

   Alex says:

   February 9, 2017

   Hi team, would be good if you disabled the update while this isn’t fixed..

   • 

     Tatiana Shabaeva says:

     February 9, 2017

     Hi Alex. Our apologies for inconvenience, update was disabled.

3. 

   Alexander Marcenyuk says:

   February 9, 2017

   +++

4. 

   Valeriy says:

   February 12, 2017

   On my project previous AppCode build 171.2822.6 is much slower than Xcode too.
   сlean build: ~ 14min Xcode / ~ 22 min AppCode
   small changes: ~ 15sec to recompile on Xcode / ~ 30 sec on AppCode

   • 

     Stanislav Dombrovsky says:

     February 15, 2017

     The issue mentioned in this post is not related to the build time. It’s related to initial projects symbols’ caching. For building AppCode invokes xcodebuild, so the speed of the compilation is the speed of xcodebuild and we cannot make it faster.

5. 

   louis says:

   April 3, 2017

   Hello

   when installing version AppCode-171.2822.6 I get the message “This build of appcode has expired” …
   I’m having a license for the non-EAP version but I want to use the eap … how to i do this ?