Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-23518] iOS: Cannot build with Xcode 8.0

GitHub Issuen/a
TypeBug
PriorityCritical
StatusClosed
ResolutionFixed
Resolution Date2016-09-20T14:28:59.000+0000
Affected Version/sRelease 6.0.0, Release 5.4.0, Release 5.3.1
Fix Version/sRelease 5.5.0
ComponentsiOS, Tooling
Labelsqe-5.3.1, qe-5.4.0, qe-5.5.0
ReporterEric Wieber
AssigneeChee Kiat Ng
Created2016-06-14T16:49:24.000+0000
Updated2016-10-10T16:29:29.000+0000

Description

I receive errors when trying to build when using Xcode 8.0. Building for simulators (iOS 8.4, 9.0, and 10), I get this: 
[INFO] :   Launching iOS Simulator
[ERROR] :  Failed to parse app's Info.plist: /Users/Eric/Documents/Appcelerator_Studio_Workspace/xcodeagain/build/iphone/build/Products/Debug-iphonesimulator/xcodeagain.app/Info.plist
And building to device, I see this: 
[ERROR] :  Error details: Bundle identifier is missing. newxcodetest doesn't have a bundle identifier for the Debug build configuration. Add a value for PRODUCT_BUNDLE_IDENTIFIER in the build settings editor.
[ERROR] :  Error details: Code signing is required for product type 'Application' in SDK 'iOS 10.0'
*Steps to reproduce issue* 1. Create a new project: appc new 2. Run the project: cd <project_path>, appc run *Expected Results* The project builds and runs without issue *Actual Results* The above errors are encountered and the project will not run

Attachments

FileDateSize
ErrorLog_new.rtf2016-09-19T08:50:58.000+0000111933
Info.plist2016-06-14T16:57:41.000+00001287
Screen Shot 2016-06-14 at 12.20.06 PM.png2016-06-14T19:21:31.000+0000255829
Screen Shot 2016-06-14 at 12.20.41 PM.png2016-06-14T19:21:31.000+0000488974

Comments

  1. Eric Wieber 2016-06-14

    Attaching an Info.plist from an afflicted project.
  2. Chee Kiat Ng 2016-06-14

    I"m only able to reproduce this on studio. But my appc cli is working fine though. [~kkolipaka] probably should start investigating too.
  3. Wilson Luu 2016-06-14

    I can also reproduce this issue from CLI with Xcode 8.0 beta (8S128d) with: Appc CLI NPM: 4.2.7-2 Appc CLI Core: 5.4.0-15 Arrow: 1.7.31 SDK: 5.4.0.v20160608165242 Node: v4.4.5 OS: El Capitan (10.11.5)
  4. Chee Kiat Ng 2016-06-14

    Weird! Appc CLI NPM: 4.2.7-2 Appc CLI Core: 5.3.1-2 Arrow: 1.7.31 SDK: 5.4.0.v20160519143319 Node: v4.2.2 OS: El Capitan (10.11.5) i can't reproduce on CLI with Xcode 8.0
  5. Chee Kiat Ng 2016-06-14

    Attached 2 screenshots of the difference between a studio built Xcode project, and a cli built Xcode project. Key differences here include: - info.plist is much less than the correct one - Automatically enable provisioning is disabled / enabled - Identity fields are missing This is not necessarily a studio issue since wilson and eric can reproduce in CLI. [~cbarber] thoughts on what may have possibly gone wrong?
  6. Chris Barber 2016-06-14

    In Xcode 7, Apple started moving certain settings to environment variables such as ${PRODUCT_NAME}, but these are not necessary. We should be able to continue to inline settings. Secondly, I also see the Failed to parse app's Info.plist error when building from the CLI using Xcode 8 beta + Titanium CLI (master) + Titanium SDK (master). In the past this we've seen this error, but it was because the file was completely missing. On my machine, the file is indeed there, has the correct permissions, and not malformed. The file looks correct and opens fine in Xcode. One thing I noticed is the coding signing part of the output: 
       [TRACE] Signing Identity:     "-"
   [TRACE]     /usr/bin/codesign --force --sign - --timestamp=none /Users/chris/appc/workspace/testapp/build/iphone/build/Products/Debug-iphonesimulator/testapp.app
    The signing identity is basically empty, so I suspect we just need to add this and things will work.
  7. Chee Kiat Ng 2016-06-14

    [~cbarber] how do we add this?
  8. Hans Knöchel 2016-06-14

    Note from Xcode 8: There is "Provisioning Profiles (Deprecated)" and "Provisioning Profiles" [(Screen)](https://abload.de/img/bildschirmfoto2016-06vokyl.png). If we check the raw values, it shows the following keys that differ: 
       PROVISIONING_PROFILE = ""; // Old key
   "PROVISIONING_PROFILE[sdk=iphoneos*]" = ""; // New key
    as well as 
       PROVISIONING_PROFILE = ""; // Old key
   PROVISIONING_PROFILE_SPECIFIER = ""; // New key
  9. Chris Barber 2016-06-14

    Adding PRODUCT_BUNDLE_IDENTIFIER doesn't fix it for sim builds. Furthermore, I can't get PRODUCT_BUNDLE_IDENTIFIER to stick. When the Titanium iOS build injects it, Xcode doesn't read it when opening the project file. However, if I set it via Xcode, it will stick. No idea. No typos. It's weird. For the provisioning profiles, there is no PROVISIONING_PROFILE\[sdk=iphoneos*\]. Adding it causes the Xcode project to be invalid. I added PROVISIONING_PROFILE_SPECIFIER and now device builds finish successfully, however the output ipa app is invalid. Need to do more investigating. Despite PROVISIONING_PROFILE being deprecated, we still need to set it for older Xcode versions. It's harmless to have both the old PROVISIONING_PROFILE and new PROVISIONING_PROFILE_SPECIFIER. Another change which is rather big is PROVISIONING_PROFILE_SPECIFIER must be in the format <TEAM_ID>/<PROVISIONING PROFILE UUID>. We already have code for handling team IDs, but it's only for App Groups to be allow iOS apps and WatchOS apps to talk to each other. Now we will REQUIRE the team ID to be specified in the tiapp.xml or prompted by the CLI. This will be a bit of work and Studio will probably have to provide a dropdown in the tiapp.xml editor to make it easier to specify the team ID since the team ID is not easy to remember.
  10. Ingo Muschenetz 2016-06-14

    [~cb1kenobi] I know this is a break from your daemon work, but I think it would be worthwhile taking a small break to fix this and unblock iOS development/testing.
  11. Chee Kiat Ng 2016-06-16

    [~cbarber] I solved the mystery (sort of). After much investigation, i came to the conclusion that our xcodebuild command is behaving differently from building from Xcode itself, on the same titanium generated project (with the right info plist). The info.plist only got mutated when we run xcodebuild cli. Therefore, i continued to think it may be something to do with the flag arguments we pass into xcodebuild. Lo and Behold, if you comment this out: https://github.com/appcelerator/titanium_mobile/blob/master/iphone/cli/commands/_build.js#L5938 The titanium app will build and launch successfully (with no mutated info.plist). And also, i tried changing the derived data path in Xcode->preferences, it still works no matter if it's relative or absolute. So either the behavior of -derivedDataPath changed, or it's something else I'm not sure. I'll bring it up to the Apple Xcode team on friday during their lab session.
  12. Chris Barber 2016-06-16

    [~cng] I figured out the mystery of the simulator not launching. When launching the simulator and installing an app, we need the app id to be able to launch the app. During the huge refactor when watch support was added, we also needed to support the watch app's id. Instead of passing this in, ioslib detects the app id and watch app id from the Info.plist in the app directory that is passed in. This means it's looking for a key called CFBundleIdentifier in the Info.plist. If this value is missing, it errors out. The problem is when Xcode 8 compiles the Info.plist, it strips the CFBundleIdentifier from the final Info.plist in the build/iphone/build/Products/Debug-iphonesimulator/<appname>.app/. Why did Apple do this? Is this a bug? Security issue? ---- The modified Info.plist in the build/iphone directory does not impact clean builds, but it will impact subsequent builds. We need to find out why the Info.plist is being modified. Why did -derivedDataPath change? Is there a bug?
  13. Chee Kiat Ng 2016-06-16

    [~cbarber] They told me to file a bug for -derivedDataPath. They it's most likely a bug on their end. I have filed bug.
  14. Chris Barber 2016-06-16

    [~cng] Can you also ask why CFBundleIdentifier is no longer in the Info.plist?
  15. Chee Kiat Ng 2016-06-16

    [~cbarber] well. they are saying since that flag corrupts the info.plist to ground zero, so that maybe why that key is missing (together with the others). Because in a new Xcode 8 project, the CFBundleIdentifier is there. If i mis-interpreted what you are saying, can you give me a reproducible case to show them?
  16. Chris Barber 2016-06-16

    [~cng] The iOS build writes the correct build/iphone/Info.plist, then xcodebuild compiles it and outputs the compiled Info.plist into build/iphone/build/Products/Debug-iphonesimulator/<appname>.app/ while also rewriting the correct build/iphone/Info.plist with a bad Info.plist. The problem is the compiled Info.plist build/iphone/build/Products/Debug-iphonesimulator/<appname>.app/Info.plist has everything except the CFBundleIndentifier. If you can reproduce that Info.plist error for sim builds, then just go open the compiled Info.plist and you'll see the CFBundleIdentifier is missing.
  17. Chee Kiat Ng 2016-06-16

    Woa. it's worse than just a missing CFBundleIdentifier. the info.plist is completely different. 
        bplist00ß	
    
    69:<=>?@AB_DTPlatformVersionZDTCompiler]CFBundleIcons\DTXcodeBuild_DTPlatformBuild_LastAccessedDate^UILaunchImages_CFBundleIcons~ipadWDTXcode_CFBundleSupportedPlatforms]WorkspacePath_MinimumOSVersion_BuildMachineOSBuild^DTPlatformNameYDTSDKNameZDTSDKBuild^UIDeviceFamilyT10.0_"com.apple.compilers.llvm.clang.1_0Ñ_CFBundlePrimaryIconÑ_CFBundleIconFiles£\AppIcon29x29\AppIcon40x40\AppIcon60x60V8S128dP3A½Hb
  18. Chris Barber 2016-06-16

    Compiled plists are binary. Open it in Xcode or convert it back to ascii using plutil. Also you should be able to view the view in Finder using QuickLook (spacebar).
  19. Chee Kiat Ng 2016-06-16

        <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    	<key>DTPlatformVersion</key>
    	<string>10.0</string>
    	<key>DTCompiler</key>
    	<string>com.apple.compilers.llvm.clang.1_0</string>
    	<key>CFBundleIcons</key>
    	<dict>
    		<key>CFBundlePrimaryIcon</key>
    		<dict>
    			<key>CFBundleIconFiles</key>
    			<array>
    				<string>AppIcon29x29</string>
    				<string>AppIcon40x40</string>
    				<string>AppIcon60x60</string>
    			</array>
    		</dict>
    	</dict>
    	<key>DTXcodeBuild</key>
    	<string>8S128d</string>
    	<key>DTPlatformBuild</key>
    	<string></string>
    	<key>LastAccessedDate</key>
    	<date>2016-06-16T20:49:38Z</date>
    	<key>UILaunchImages</key>
    	<array>
    		<dict>
    			<key>UILaunchImageSize</key>
    			<string>{414, 736}</string>
    			<key>UILaunchImageName</key>
    			<string>LaunchImage-800-Portrait-736h</string>
    			<key>UILaunchImageMinimumOSVersion</key>
    			<string>8.0</string>
    			<key>UILaunchImageOrientation</key>
    			<string>Portrait</string>
    		</dict>
    		<dict>
    			<key>UILaunchImageSize</key>
    			<string>{414, 736}</string>
    			<key>UILaunchImageName</key>
    			<string>LaunchImage-800-Landscape-736h</string>
    			<key>UILaunchImageMinimumOSVersion</key>
    			<string>8.0</string>
    			<key>UILaunchImageOrientation</key>
    			<string>Landscape</string>
    		</dict>
    		<dict>
    			<key>UILaunchImageSize</key>
    			<string>{375, 667}</string>
    			<key>UILaunchImageName</key>
    			<string>LaunchImage-800-667h</string>
    			<key>UILaunchImageMinimumOSVersion</key>
    			<string>8.0</string>
    			<key>UILaunchImageOrientation</key>
    			<string>Portrait</string>
    		</dict>
    		<dict>
    			<key>UILaunchImageSize</key>
    			<string>{320, 480}</string>
    			<key>UILaunchImageName</key>
    			<string>LaunchImage-700</string>
    			<key>UILaunchImageMinimumOSVersion</key>
    			<string>7.0</string>
    			<key>UILaunchImageOrientation</key>
    			<string>Portrait</string>
    		</dict>
    		<dict>
    			<key>UILaunchImageSize</key>
    			<string>{320, 568}</string>
    			<key>UILaunchImageName</key>
    			<string>LaunchImage-700-568h</string>
    			<key>UILaunchImageMinimumOSVersion</key>
    			<string>7.0</string>
    			<key>UILaunchImageOrientation</key>
    			<string>Portrait</string>
    		</dict>
    	</array>
    	<key>CFBundleIcons~ipad</key>
    	<dict>
    		<key>CFBundlePrimaryIcon</key>
    		<dict>
    			<key>CFBundleIconFiles</key>
    			<array>
    				<string>AppIcon29x29</string>
    				<string>AppIcon40x40</string>
    				<string>AppIcon60x60</string>
    			</array>
    		</dict>
    	</dict>
    	<key>DTXcode</key>
    	<string>0800</string>
    	<key>CFBundleSupportedPlatforms</key>
    	<array>
    		<string>iPhoneSimulator</string>
    	</array>
    	<key>WorkspacePath</key>
    	<string>/Users/kiat/titaniumTestWatch/SGTestDerived/build/iphone/SGTestDerived.xcodeproj</string>
    	<key>MinimumOSVersion</key>
    	<string>7.1</string>
    	<key>BuildMachineOSBuild</key>
    	<string>15F34</string>
    	<key>DTPlatformName</key>
    	<string>iphonesimulator</string>
    	<key>DTSDKName</key>
    	<string>iphonesimulator10.0</string>
    	<key>DTSDKBuild</key>
    	<string>14A5261u</string>
    	<key>UIDeviceFamily</key>
    	<array>
    		<integer>1</integer>
    	</array>
    </dict>
    </plist>
  20. Chris Barber 2016-06-16

    No CFBundleIdentifier. :(
  21. Chee Kiat Ng 2016-06-16

    i have updated the bug reporter in apple accordingly. Shouldn't it worry you that the other keys are like...wierd
  22. Chris Barber 2016-06-16

    Um, weird in what way? Looks like an Info.plist to me.
  23. Chee Kiat Ng 2016-06-17

    so i guess we have to wait for apple to respond or their next beta release? Is it an issue if we remove -derivedDataPath entirely? i tried that, the build and everything seem pretty ok. [~cbarber]
  24. Chris Barber 2016-06-17

    [~cng] Yep, we have to wait. I don't think we should remove -derivedDataPath. We need to override the global Xcode settings. As for the team and provisioning profile handling, I like the idea of moving away from provisioning profile uuids, but I'm not entire sure yet how we should handle things, especially with maintaining backwards compatibility with Xcode 7. Here's the PR with what I've got so far which includes all the team id changes: https://github.com/appcelerator/titanium_mobile/pull/8072.
  25. Chee Kiat Ng 2016-07-07

    [~cbarber] So I tried this again with Xcode 8 beta 2, but it still fails. HOWEVER, I discovered that, it's not entirely Xcode 8's fault for over-writing the info.plist. because I can sort of reproduce this using Xcode 7.3.1. Basically, https://github.com/appcelerator/titanium_mobile/blob/master/iphone/cli/commands/_build.js#L5938 the arg -derivedDataPath *IS* supposed to produce an info.plist and a ModuleCache folder. So in our cli we specified -derivedDataPath to be the buildDir, where an info.plist already exist. We were lucky in Xcode 7.3.1 Apple was smart enough to say, hey your flag tells me to put an info.plist here, but you already have one, so i'll skip doing that. Whereas in Xcode 8, Apple decided hey your flag tells me to put an info.plist here, so I'm just doing as I'm told and i'll overwrite anything you have here. SO, we just need to change the derivedDataPath to somewhere else and all will work, in Xcode 7.3.1 and in Xcode 8. But I think something else need to change so that it still does incremental builds.
  26. Chee Kiat Ng 2016-07-07

    PR HERE: https://github.com/appcelerator/titanium_mobile/pull/8111

    Steps to Test

    1. *appc new* 2. *appc run -p ios -I 10.0*

    Expected Result

    Builds and runs normally Additional Tests 1. Repeat *appc run -p ios -I 10.0 -l trace*, it should be incrementally built (you can tell from the speed it builds, as well as looking in the trace) 2. Test on device 3. Test on both Xcode 7.3.1 and on Xcode 8
  27. Henry David Spells III 2016-08-08

    I am experiencing this problem with the XCode 7.3.1 build tools and the XCode 8 build tools with TItanium SDK 5.2.2.GA, 5.3.1.GA and 5.4.0v20160804185318. I tried using Titanium SDK 6.0.0.v20160807124019 and appc locks up when I run from the studio and from the command line using appc run -p ios -I 10.0 When I run from the command line this is all I see Appcelerator Command-Line Interface, version 5.3.1 Copyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved. When I run from the Titanium Studio this is what I see Appcelerator Command-Line Interface, version 5.3.1 Copyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved. 2016-08-08T05:21:52.107Z | TRACE | set environment to {"registry":"https://software.appcelerator.com","security":"https://security.appcelerator.com","baseurl":"https://platform.appcelerator.com"} 2016-08-08T05:21:52.109Z | TRACE | checking credentials for existing session 2016-08-08T05:21:52.397Z | TRACE | Attempting to load session info from config file 2016-08-08T05:21:52.405Z | TRACE | check if session is invalidated 2016-08-08T05:21:52.763Z | TRACE | session expiry 1471213858937 false 2016-08-08T05:21:52.765Z | TRACE | Arrow Cloud config file: /Users/dspells/.acs 2016-08-08T05:21:52.783Z | TRACE | found Arrow Cloud login { mid: 'd95de55289e4bae98cf93bf7068cd8b85009e54c', publishPort: 443, publishHost: 'https://admin.cloudapp-enterprise.appcelerator.com', username: 'dspells@me.com', cookie: [ 'connect.sid=s%3AaMHygSmZ6HbnwF9YrB3zwaSk.bo1shejTnlnOfnjARXp8RyFwBMndHA3SFyAShY4GqoI; Path=/; Expires=Sun, 21 Aug 2016 22:31:00 GMT; HttpOnly' ], defaultEP: { publishHost: 'https://admin.cloudapp-enterprise.appcelerator.com', publishPort: 443 } } , checking nodeACSEndpoint= https://admin.cloudapp-enterprise.appcelerator.com 2016-08-08T05:21:52.785Z | TRACE | Arrow Cloud cookie expiry [ 1471818660000 ] 2016-08-08T05:21:52.785Z | TRACE | session already loaded in opts.session 2016-08-08T05:21:52.787Z | TRACE | getCredentials() session: { "ipaddress": "192.168.2.64", "username": "dspells@me.com", "password": "", "session": "", "nonce": "", "environment": { "name": "production", "isProduction": true, "acsBaseUrl": "https://api.cloud.appcelerator.com", "acsAuthBaseUrl": "https://secure-identity.cloud.appcelerator.com", "nodeACSEndpoint": "https://admin.cloudapp-enterprise.appcelerator.com" }, "token": "", "fingerprint": "d95de55289e4bae98cf93bf7068cd8b85009e54c", "fingerprint_description": "Mac OSX Serial Number: H00420ZHEUH", "org_id": 100001535, "expiry": 1471213858937 } 2016-08-08T05:21:52.788Z | TRACE | loading plugins for command "run" 2016-08-08T05:21:52.953Z | TRACE | run search paths: [ "/Users/dspells/.appcelerator/install/5.3.1/package", "/Users/dspells/.appcelerator/install/5.3.1/package/node_modules", "/Applications/Appcelerator Studio/AppceleratorStudio.app/Contents/MacOS/node_modules", "/Applications/Appcelerator Studio/AppceleratorStudio.app/Contents/node_modules", "/Applications/Appcelerator Studio/AppceleratorStudio.app/node_modules", "/Applications/Appcelerator Studio/node_modules", "/Applications/node_modules", "/node_modules", "/Users/dspells/.appcelerator/.npm/lib/node_modules" ] 2016-08-08T05:21:52.954Z | DEBUG | [PLUGIN-LOAD] 0ms /Users/dspells/.appcelerator/install/5.3.1/package/appc.js 2016-08-08T05:21:53.212Z | DEBUG | [PLUGIN-LOAD] 257ms /Users/dspells/.appcelerator/install/5.3.1/package/node_modules/appc-cli-titanium/appc.js 2016-08-08T05:21:53.212Z | DEBUG | run plugin: /Users/dspells/.appcelerator/install/5.3.1/package/node_modules/appc-cli-titanium 2016-08-08T05:21:53.215Z | DEBUG | [PLUGIN-LOAD] 1ms /Users/dspells/.appcelerator/install/5.3.1/package/node_modules/arrow/appc.js 2016-08-08T05:21:53.253Z | DEBUG | run plugin: /Users/dspells/.appcelerator/install/5.3.1/package/node_modules/arrow 2016-08-08T05:21:53.281Z | TRACE | plugin "arrow" failed its "when" function check, skipping... 2016-08-08T05:21:53.282Z | TRACE | loading plugin "titanium" for command "run" CLI options via function 2016-08-08T05:21:53.284Z | TRACE | loading plugin "titanium" for command "run" CLI options via array 2016-08-08T05:21:53.288Z | TRACE | executing command "run" with the following plugins: ["titanium"] 2016-08-08T05:21:53.290Z | TRACE | Attempting to load session info from config file 2016-08-08T05:21:53.291Z | TRACE | check if session is invalidated 2016-08-08T05:21:53.487Z | TRACE | session expiry 1471213858937 false 2016-08-08T05:21:53.488Z | TRACE | session already loaded in opts.session 2016-08-08T05:21:53.490Z | DEBUG | Titanium Downloads Last Checked: 1470609836457 So this does not seem to be fixed for me in the latest master branch build. Any help/advice would be appreciated and if I can submit any more information to help please tell me.
  28. Chee Kiat Ng 2016-08-08

    I can't seem to reproduce your issue. I tried appc cli 5.3.1 and Ti SDK latest master. Can you try *appc use 5.4.0-37* and try again.
  29. Henry David Spells III 2016-08-08

    Appcelerator Command-Line Interface, version 5.4.0-37 Copyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved. ---- it stops here indefinitely In Studio Appcelerator Command-Line Interface, version 5.4.0-37 Copyright (c) 2014-2016, Appcelerator, Inc. All Rights Reserved. 2016-08-08T06:40:35.466Z | TRACE | set environment to {"registry":"https://software.appcelerator.com","security":"https://security.appcelerator.com","baseurl":"https://platform.appcelerator.com"} 2016-08-08T06:40:35.469Z | TRACE | checking credentials for existing session 2016-08-08T06:40:35.758Z | TRACE | Attempting to load session info from config file 2016-08-08T06:40:35.767Z | TRACE | check if session is invalidated 2016-08-08T06:40:36.114Z | TRACE | registry result 200 application/json undefined undefined false undefined 2016-08-08T06:40:36.130Z | TRACE | registry returned { expiry: 1471243236056 } 2016-08-08T06:40:36.131Z | TRACE | refresh session expiry to: 1471243236056 2016-08-08T06:40:36.133Z | TRACE | session expiry 1471243236056 false 2016-08-08T06:40:36.134Z | TRACE | Arrow Cloud config file: /Users/dspells/.acs 2016-08-08T06:40:36.136Z | TRACE | found Arrow Cloud login { mid: 'd95de55289e4bae98cf93bf7068cd8b85009e54c', publishPort: 443, publishHost: 'https://admin.cloudapp-enterprise.appcelerator.com', username: 'dspells@me.com', cookie: [ 'connect.sid=s%3AaMHygSmZ6HbnwF9YrB3zwaSk.bo1shejTnlnOfnjARXp8RyFwBMndHA3SFyAShY4GqoI; Path=/; Expires=Sun, 21 Aug 2016 22:31:00 GMT; HttpOnly' ], defaultEP: { publishHost: 'https://admin.cloudapp-enterprise.appcelerator.com', publishPort: 443 } } , checking nodeACSEndpoint= https://admin.cloudapp-enterprise.appcelerator.com 2016-08-08T06:40:36.138Z | TRACE | Arrow Cloud cookie expiry [ 1471818660000 ] 2016-08-08T06:40:36.138Z | TRACE | session already loaded in opts.session 2016-08-08T06:40:36.140Z | TRACE | getCredentials() session: { "ipaddress": "192.168.2.64", "username": "dspells@me.com", "password": "", "session": "", "nonce": "", "environment": { "name": "production", "isProduction": true, "acsBaseUrl": "https://api.cloud.appcelerator.com", "acsAuthBaseUrl": "https://secure-identity.cloud.appcelerator.com", "nodeACSEndpoint": "https://admin.cloudapp-enterprise.appcelerator.com" }, "token": "", "fingerprint": "d95de55289e4bae98cf93bf7068cd8b85009e54c", "fingerprint_description": "Mac OSX Serial Number: H00420ZHEUH", "org_id": 100001535, "expiry": 1471243236056 } 2016-08-08T06:40:36.141Z | TRACE | loading plugins for command "run" 2016-08-08T06:40:36.204Z | TRACE | run search paths: [ "/Users/dspells/.appcelerator/install/5.4.0-37/package", "/Users/dspells/.appcelerator/install/5.4.0-37/package/node_modules", "/Applications/Appcelerator Studio/AppceleratorStudio.app/Contents/MacOS/node_modules", "/Applications/Appcelerator Studio/AppceleratorStudio.app/Contents/node_modules", "/Applications/Appcelerator Studio/AppceleratorStudio.app/node_modules", "/Applications/Appcelerator Studio/node_modules", "/Applications/node_modules", "/node_modules", "/Users/dspells/.appcelerator/.npm/lib/node_modules" ] 2016-08-08T06:40:36.206Z | DEBUG | [PLUGIN-LOAD] 0ms /Users/dspells/.appcelerator/install/5.4.0-37/package/appc.js 2016-08-08T06:40:36.580Z | DEBUG | [PLUGIN-LOAD] 369ms /Users/dspells/.appcelerator/install/5.4.0-37/package/node_modules/appc-cli-titanium/appc.js 2016-08-08T06:40:36.580Z | DEBUG | run plugin: /Users/dspells/.appcelerator/install/5.4.0-37/package/node_modules/appc-cli-titanium 2016-08-08T06:40:36.584Z | DEBUG | [PLUGIN-LOAD] 1ms /Users/dspells/.appcelerator/install/5.4.0-37/package/node_modules/arrow/appc.js 2016-08-08T06:40:36.587Z | DEBUG | run plugin: /Users/dspells/.appcelerator/install/5.4.0-37/package/node_modules/arrow 2016-08-08T06:40:36.652Z | TRACE | plugin "arrow" failed its "when" function check, skipping... 2016-08-08T06:40:36.653Z | TRACE | loading plugin "titanium" for command "run" CLI options via function 2016-08-08T06:40:36.656Z | TRACE | loading plugin "titanium" for command "run" CLI options via array 2016-08-08T06:40:36.660Z | TRACE | executing command "run" with the following plugins: ["titanium"] 2016-08-08T06:40:36.662Z | TRACE | Attempting to load session info from config file 2016-08-08T06:40:36.663Z | TRACE | check if session is invalidated 2016-08-08T06:40:36.884Z | TRACE | registry result 200 application/json undefined undefined false undefined 2016-08-08T06:40:36.885Z | TRACE | registry returned { expiry: 1471243236844 } 2016-08-08T06:40:36.885Z | TRACE | refresh session expiry to: 1471243236844 2016-08-08T06:40:36.886Z | TRACE | session expiry 1471243236844 false 2016-08-08T06:40:36.887Z | TRACE | session already loaded in opts.session 2016-08-08T06:40:36.919Z | DEBUG | Titanium Downloads Last Checked: 1470609836457 Is there something else I need to check/upgrade
  30. Chee Kiat Ng 2016-08-08

    I am not quite sure. So you are saying it works if you do *-I 9.3* instead of *-I 10.0*?
  31. Henry David Spells III 2016-08-08

    Actually I get the same result with -I 9.3
  32. Chee Kiat Ng 2016-08-08

    [~dspells]If that's the case you might want to create a new ticket for your particular problem , which i suspect is appc cli related.
  33. Henry David Spells III 2016-08-08

    Creating a new project and running that works. After I created a new project and then came back to my existing project, it seems to work now also with 5.4.0-37/6.0.0.v20160807124019. Thank you.
  34. Hans Knöchel 2016-08-08

    Closing ticket, thanks!
  35. Harry Bryant 2016-08-25

    Verified as fixed, Using Xcode 8.0 beta 6 (8S201h) I am able to build to iOS10/9 simulators & devices, and watchOS3/2 simulators & devices. Tested On: iPhone 6S (10.0, 9.3.4) Device & Simulator Apple Watch (OS 2.2.2, 3.0) Device & Simulator Mac OSX El Capitan 10.11.6 Ti SDK: 5.5.0.v20160822000355 Appc Studio: 4.7.1.201608190732 Appc NPM: 4.2.7 App CLI: 5.5.0-5 Xcode 8.0 beta 6 (8S201h) Node v4.4.7 *Closing ticket.*
  36. Joe Falcone 2016-09-14

    I know this is "closed" and "fixed" (famous last words) but just updated to 5.50 GA SDK and 4.7.1 Studio and building a very simple old project that had no problems before upgrading to Xcode 8.. [INFO] : Invoking xcodebuild [INFO] : Finished building the application in 40s 999ms [INFO] : Launching iOS Simulator *[ERROR] : Failed to parse app's Info.plist: /Users/jrf/Studio/Jobs4Youth/build/iphone/build/Products/Debug-iphonesimulator/Jobs4Youth.app/Info.plist* I'm running *Xcode Version 8.0 (8A218a)* which it appears that you haven't tested with since it only became available today.
  37. Joe Falcone 2016-09-14

    Please disregard my comment - it does work with 8A218a.
  38. Chris Barber 2016-09-14

    [~jfalcone] We've seen this happen intermittently with Xcode 8 GM seed, however we can't reproduce it consistently. Usually cleaning the project and building again fixes it. Are you just building with iOS 10 and Xcode 8 or are you switching between iOS 9 and 10? The CoreSimulator services for Xcode 7 and Xcode 8 are different and they get swapped automatically, however it's possible for the swap to be flaky. Usually rebuilding solves it. Another possible cause, which is related to the above, happens when we clean the derived data. Sometimes the xcodebuild clean command crashes. I suspect it's an Xcode bug. I'll continue to keep an eye on this and hopefully fix it. Please let me know if you stumble across any additional information. Thanks!
  39. Joe Falcone 2016-09-14

    It may have been intermittent but it works now (several times in a row) so I'm satisfied that it is OK.
  40. Amanda 2016-09-16

    I am encountering this error as well. Can someone please help me fix this? how do i get the fix?
  41. Chee Kiat Ng 2016-09-16

    Hi, you have to use titanium sdk 5.5.0 and preferably app cli
  42. Ianko Leite 2016-09-16

    I am also getting the same error. It's not a new project (not created using appc new using CLI 5.5), but it is a version that works fine with APPC CLI 5.4 and Xcode 7. I did followed the instructions on this post: http://www.appcelerator.com/blog/2016/09/ga-release-for-titanium-sdk-5-5-0-appcelerator-cli-5-5-0-appcelerator-studio-4-7-1/ {noformat} Appcelerator CLI Installer = 4.2.7 Core Package = 5.5.0 5.5.0.GA Version = 5.5.0 Platforms = android, mobileweb, iphone git Hash = 44a2e3f git Timestamp = 09/13/16 12:38 node-appc Version = 0.2.36 Mac OS X Command Line Tools = installed 8.0 (build 8A218a) - Xcode default Install Location = /Applications/Xcode.app/Contents/Developer iOS SDKs = 10.0 iOS Simulators = 10.0 Watch SDKs = 3.0 Watch Simulators = 3.0 Supported by TiSDK 5.5.0.GA = yes EULA Accepted = yes Connected iOS Devices Ianko iPhone UDID = ################ Type = iPhone (#e4e7e8) iOS Version = 10.0.1 CPU Architecture = arm64 {noformat} Compiling using: 
        appc run -p ios -I 10.0 -T device
    Error: 
        [ERROR] Error details: Bundle identifier is missing. FanHero Dev doesn't have a bundle identifier for the Debug build configuration. Add a value for PRODUCT_BUNDLE_IDENTIFIER in the build settings editor.
    [ERROR] Error details: Code signing is required for product type 'Application' in SDK 'iOS 10.0'
  43. Chee Kiat Ng 2016-09-16

    [~ianko] I am assuming you did a clean project before this? And is it working on simulator?
  44. Ianko Leite 2016-09-17

    I did clean my project before everything. My project has a particular module that does not include the necessary libraries targeted to run on simulator. Just devices.
  45. Chee Kiat Ng 2016-09-17

    It'll help if you could 1. run *appc run -p ios -I 10.0 -T device -l trace* and let us take a look at the trace for more error information. 2. Try to run a new project on simulator and device with this exact environment just to make sure there's nothing wrong.
  46. Ianko Leite 2016-09-17

    1. Where can I send this log without exposing my data here? 2. Created a new project using appc new and it ran on simulator but not on device. Same kind of error: {noformat} [ERROR] Error details: Provisioning profile "iOS Team Provisioning Profile: *" is Xcode managed, but signing settings require a manually managed profile. [ERROR] Error details: Code signing is required for product type 'Application' in SDK 'iOS 10.0' {noformat}
  47. eric harms 2016-09-19

    Hi, Has this one been resolved and closed? I just updated to XCode8 and Ti SDK 5.5.0, and Im getting the following. .... .... .... [INFO] Writing app properties [INFO] Encrypting JavaScript files [INFO] Writing i18n files [INFO] Processing Titanium symbols [INFO] Removing files [INFO] Optimizing .plist and .png files [INFO] Invoking xcodebuild [ERROR] Error details: Bundle identifier is missing. XXXXX doesn't have a bundle identifier for the Debug build configuration. Add a value for PRODUCT_BUNDLE_IDENTIFIER in the build settings editor. [ERROR] Error details: Code signing is required for product type 'Application' in SDK 'iOS 10.0' Verified that the bundle id is not in the xcode project after it fails. Thanks!
  48. Chris Barber 2016-09-20

    [~eric.harms@gmail.com] That error is unrelated to this ticket. Please create a new ticket with your environment and steps to reproduce. We can then take a look and keep track of it. Thank you.
  49. eric harms 2016-09-20

    Chris -- Im a bit confused, as my error is exactly what the error is that started this thread, but I will open another ticket. Thanks!
  50. Chris Barber 2016-09-20

    [~eric.harms@gmail.com] Doh! I was thinking the Info.plist missing issue. Sorry! My bad. Can you confirm that you are getting the missing bundle identifier for device builds, sim builds, or both?
  51. eric harms 2016-09-20

    no worries :) i can confirm missing bundle id on device builds, info.plist error on sim builds. My project was created well before 5.5.0.GA if that matters, but if I create a new project I get the same errors. Heres my environment details, let me know if you need any more info Mac OS X 10.11.5 Node.js Version 0.12.7 npm Version 2.11.3 Titanium CLI Version 5.0.9 node-appc Version 0.2.31 5.5.0.GA 8.0 (build 8A218a) - Xcode default iOS SDKs = 10.0 iOS Simulators = 10.0 Watch SDKs = 3.0 Watch Simulators = 3.0 Thanks Eric
  52. Chee Kiat Ng 2016-09-21

    [~capsizeno4] What appc-cli version are you using? Are you seeing this error on both simulator and device? If you don't mind, having a copy of the full trace log and maybe your tiapp.xml (without the guid or sensitive information) may help us help you.
  53. Jonas Tornqvist 2016-09-21

    I just updated to xcode 8 and have the same problem
  54. eric harms 2016-09-21

    Chee -- My note before your comment has my environment specs, but my CLI version is Titanium CLI CLI Version = 5.0.9 node-appc Version = 0.2.31 when I Ti info I dont mind sending you a log including my ti info -- ill email you Thanks Eric
  55. eric harms 2016-09-21

    Chee -- send you my log and my tiapp.xml via email. Also -- im getting this error when i build to an ios10 device. when i build to the sim i get the info.plist error that is talked about through this thread. Thanks Eric
  56. eric harms 2016-09-21

    Chee -- Just wanted to make sure you got all my log files I sent this morning, and if so if you had any thoughts on what might be causing the issue. Thanks! Eric
  57. Chris Barber 2016-09-21

    [~eric.harms@gmail.com], [~Pandan] I cannot for the life of me reproduce either the Simulator build error with the Info.plist or the device build error with the bundle identifier. I've tried many different things and no luck. Everything works as expected. Please give me precise steps to reproduce.
  58. eric harms 2016-09-21

    Chris, I wish I was having your luck! For me, Im running my project that Ive been running for the past 9 months to get the bundle id error on the device -- and i just created a new project to get the plist.info error. Did Chee share my logs and tiapp.xml with you? I emailed them to him early this morning. It has my ti info in it as well, maybe something in there will shed a light Thanks Eric
  59. Chee Kiat Ng 2016-09-21

    [~capsizeno4] I have received your logs and tiapp.xml. Basically, you didn't set the titanium sdk to 5.5.0.GA, but instead you are still using 5.3.1.GA..... 5.5.0.GA is the only SDK that supports Xcode 8 currently. Looking at your trace file, this sentence indicates that you are using the wrong sdk. [INFO] tiapp.xml <sdk-version> set to 5.3.1.GA, but current Titanium SDK set to 5.4.0.GA And looking at your tiapp.xml, i believe if you change this: 5.3.1.GA to 5.5.0.GA And probably clean the project before building, your problem will be solved.
  60. Mike Neill 2016-09-25

    The solution provided for Chee worked for me. However, I do want to say it's very unclear that the SDK is the issue here. I would recommend adding a better error message that tells the user to update their SDK version. Also, you all should have a way to automatically update these settings. If you see a developer is building with the latest iOS SDK, then perhaps you should prompt them to update their SDK as well. Small annoyances such as these is what drive people away from a platform.
  61. Hans Knöchel 2016-09-25

    [~miken01] I agree, but how could we add an error-warning to a previously releases version that does not know about releases that may effect it in the future? :-) So again: Upgrading the SDK and CLI using appc setup or checking updates in Studio is the safest way to receive product- and compatibility-updates.
  62. Mike Neill 2016-09-25

    Hans, I completely understand what you're saying. However, in this case the error message could have been bundled within the Appcelerator Studio update, which I did install via "Check for Updates". You could also build a framework within the Android Studio to check for release notes and provide detailed information based on that. I'm not suggesting you modify the SDK as much as the tool that people are consuming to utilize the SDK. Such how Xcode has it's own built-in warnings and converters to ensure developers are marching their code forward. Thanks for the reply :)
  63. eric harms 2016-09-26

    Chee, Hans, Chris Setting the correct SDK 5.5.0.GA for XCode8 in my tiapp.xml was the correct answer. I swear that was the first thing I tried, but obviously I did not. Thanks for the help! Eric
  64. Dan Wilson 2016-10-08

    I'm experiencing a similar issue and assume it is the same thing. I've checked my SDK though and it's correct. I've created a completely fresh app with appc new. 
        [ERROR] Error details: Provisioning profile "iOS Team Provisioning Profile: *" is Xcode managed, but signing settings require a manually managed profile.
    [ERROR] Error details: Code signing is required for product type 'Application' in SDK 'iOS 10.0'
    
        Appcelerator Command-Line Interface, version 5.5.1
    Copyright (c) 2014-2016, Appcelerator, Inc.  All Rights Reserved.
    
    Operating System
      Name                        = Mac OS X
      Version                     = 10.12
      Architecture                = 64bit
      # CPUs                      = 8
      Memory                      = 16.0GB
    
    Node.js
      Node.js Version             = 4.2.2
      npm Version                 = 3.10.3
    
    Appcelerator CLI
      Installer                   = 4.2.7
      Core Package                = 5.5.1
    
    Titanium CLI
      CLI Version                 = 5.0.9
      node-appc Version           = 0.2.31
    What am I doing wrong? Do I need to include the build logs? Thanks, -=Dan
  65. Chee Kiat Ng 2016-10-09

    [~killroyboy] it's a different problem what you are facing. The error log is different. yours is talking about some provisioning profile. Can you check on that? Or provide more details than this? what flags did you use when calling appc run? did you select the correct provisioning profiles?
  66. Dan Wilson 2016-10-10

    @cng The provisioning profile is managed by Xcode. It was working fine before I upgraded to Xcode8. Here's my appc run command: 
    appc run -p ios -T device -s 5.5.1.GA
     I've tried to use different SDK versions with no luck. I also reinstalled Xcode8. Is there no way for us to control the signing settings? Everything I've seen dealing with this (using native iOS/swift development) involves changing the signing settings to resolve the problem.
  67. Chris Barber 2016-10-10

    [~killroyboy] Specifying the SDK (\-s, \-\-sdk) at the command line has no effect. You must put the SDK version you want to use in the tiapp.xml. Secondly, if you have multiple Xcode versions installed, you should explicitly specify \-\-ios\-version 10.0.
  68. Dan Wilson 2016-10-10

    Chris, it is indicated in the tiapp.xml. I was just trying to pass it on the command line as well to see if that changed anything. I don't have multiple Xcode's installed, but I tried your suggestion with the same result.
  69. Chris Barber 2016-10-10

    [~killroyboy] Well, apparently you can't use the Xcode generated provisioning profiles. Try creating a new provisioning profile in the Apple Developer website, then use that one. I'll have to investigate why we can't use the generated provisioning profiles.
  70. Chris Barber 2016-10-10

    [~killroyboy] And here's the ticket: TIMOB-24008. Please continue any discussion related to your problem on that ticket and be sure to watch it for updates. Thanks!

JSON Source