[TIMOB-25180] iOS: App fails to compile on any version of macOS using case sensitive journalling

GitHub Issue	n/a
Type	Bug
Priority	Critical
Status	Closed
Resolution	Fixed
Resolution Date	2017-08-21T07:06:12.000+0000
Affected Version/s	n/a
Fix Version/s	Release 6.2.0
Components	iOS
Labels	n/a
Reporter	Peter Lancaster
Assignee	Hans Knöchel
Created	2017-08-18T12:31:17.000+0000
Updated	2017-08-21T07:06:24.000+0000

Description

When building for iOS (on simulator or device), on a Mac running a Case-sensitive journalling file format, Ti SDK 6.1.2.GA will fail to compile 100% of the time. An example error can be seen below:

[ERROR]         CompileC build/Intermediates/APPNAME.build/Debug-iphonesimulator/APPNAME.build/Objects-normal/i386/WatchSessionModule.o Classes/WatchSessionModule.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler

After losing almost an entire morning to this issue (*which _completely_ blocked one developer*), we have now got to the bottom of the issue, based on the solution [in this StackOverflow article](https://stackoverflow.com/questions/32797138/xcode-7-error-on-appcelerator-appc-5-0-2-titanium-sdk-5-0-0-ga-or-5-0-1-ga-or-3). For clarity, within the */iPhone/Classes* folder, the *WatchSessionModule.h* file needs to be changed as follows:

#from this
#import <WatchConnectivity/watchConnectivity.h>

#to this
#import <WatchConnectivity/WatchConnectivity.h>

Without this change, a developer using a file format like this is completely unable to build with the latest Titanium SDKs for iOS.

Comments

Hans Knöchel 2017-08-18

Hey Peter, thank you for raising this! I am sorry one of your developers has been blocked because of this. If something related ever happens again, feel free to always reach out to our Slack community for some quick troubleshooting - our engineering team is also looking for issues there, so you will have good chances to receive feedback much quicker. You can also reach out to me directly (Username: hans) and we will figure something out. Also, it is always good to file a JIRA ticket first, our team is scanning JIRA for new issues many times a day. Hopefully that helps you for the next time! Regarding your issue, I just pushed the fix for master (7.0.0) and 6_2_X (6.2.0). If you want a custom 6.1.2 that also includes the fix, please let me know! I will wait to push the PR to ensure this is not happening in any other places as well. Sorry again for the inconvenience caused by this!

JSON Source