[AC-1854] Compiling for iOS5.1
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | n/a |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-09-27T16:38:08.000+0000 |
Affected Version/s | n/a |
Fix Version/s | n/a |
Components | Titanium SDK & CLI |
Labels | ios, xcode |
Reporter | Nikhil N |
Assignee | Mauro Parra-Miranda |
Created | 2012-09-25T13:06:02.000+0000 |
Updated | 2016-03-08T07:40:46.000+0000 |
Description
When doing a clean build, an error is encountered at line 627 of TiApp.mm for iOS 5.1
This works fine for iOS6 however.
Issue can be fixed for iOS 5.1 by changing
- (NSUInteger)application:(UIApplication *)....
to
- (NSObject*)application:(UIApplication *)....
on line 625
Once changed, it doesn't compile for iOS6.
So one has to switch when switching between iOS versions.
Hmm, need some more info... What error is it? Can you post your build log? I doubt I'd be able to reproduce this, so could you try compiling against the latest 2.1.3 and 3.0.0 (master) builds? http://builds.appcelerator.com.s3.amazonaws.com/index.html You can drop them into ~/Library/Application Support/Titanium/mobilesdk/osx Thanks.
This is the error from the build log: [ERROR] /Users/dezinezync/Sites/Timesense/build/iphone/Classes/TiApp.mm:627:12: error: cannot initialize return object of type 'NSUInteger' (aka 'unsigned int') with an rvalue of type 'id' [ERROR] [ERROR] Error: Traceback (most recent call last): File "/Users/dezinezync/Library/Application Support/Titanium/mobilesdk/osx/2.1.3.v20120921190208/iphone/builder.py" line 1467 in main execute_xcode("iphoneos%s" % iphone_version args False) File "/Users/dezinezync/Library/Application Support/Titanium/mobilesdk/osx/2.1.3.v20120921190208/iphone/builder.py" line 1221 in execute_xcode output = run.run(args False False o) File "/Users/dezinezync/Library/Application Support/Titanium/mobilesdk/osx/2.1.3.v20120921190208/iphone/run.py" line 41 in run sys.exit(rc) SystemExit: 65
I've reproduced the bug using your TiSDK: 2.1.3.v20120921190208. I tested it with the latest 2.1.3 build (v20120926141610) and the error no longer occurs.
Closing per Daniel's comment.