AppCode 2017.1.1 release candidate (build 171.4073.44) is out today. This build mostly addresses important issues found during the EAP period:
The critical problem when indexing project/building module maps (OC-14654). This issue was caused by the "$(PODS_ROOT)/" value in User Header Search Paths build setting, that was incorrectly resolved to the file system root by AppCode.
Frequent exceptions when resolving certain Swift code constructs in 2017.1.1 EAP (OC-15316)
Today we are starting the Early Access Program for AppCode 2017.1.1, a bug-fix update to the recently released AppCode 2017.1. Build 171.4073.29 is now available for download on our confluence page.
This build brings the following new features:
Support for swift and macOS arguments in @available(...)
Support for @inline(...) annotations in parser (OC-14331)
The following issues are fixed in this build:
Can’t autocomplete in map/filter/etc. functions (OC-15193)
Problem with the type inference of closures with inout parameters (OC-15243)
Method blank line settings don’t work for initializers (OC-15177)
Find Usages should find usages if tried on concrete implementation of Objective-C protocol method in Swift (OC-15127)
Freeze when running XCTest configuration (OC-14603)
Besides, we checked Xcode 8.3 integration and removed incompatibility warning. There are some issues left, such as OC-14952 and OC-15261, but we’re working on them at the moment. In case you find any problem, please report it to our tracker.
The full list of fixes and improvements can be found here.
AppCode 2017.1 EAP (build 171.3780.31) is available for download on our confluence page (if using previous 2017.1 EAP build, the patch update is also available).
The highlights of this update include:
SE-0062: Referencing Objective-C key-paths (OC-14598), which brings correct highlighting and completion for the #keyPath() expression together with the correct resolution and navigation for its arguments
SE-0060: Enforcing order of defaulted parameters (OC-14231)