Vague "Cannot Install Watch App" message at install time if Watch App info.plist contains errors

Originator:johnrhickey
Number:rdar://22058517 Date Originated:29-Jul-2015 4:54 PM
Status:Duplicate/21540158/Closed Resolved:
Product:Developer Tools Product Version:Xcode-beta (7A165t)
Classification:Other Bug Reproducible:Yes
 
Summary:
If there is an invalid plist key in a WatchOS 2 App target, the app will install but the developer will receive a vague UIAlertView on iOS stating "Cannot Install Watch App".

If "Build & Run" is clicked again, a second error will appear in Xcode:

     Error Launching 'TestApp WatchKit App Extension'
     Installation error. Check the iPhone console for more details."

(See attached screenshots)

Steps to Reproduce:
1. Create an Xcode project with a WatchKit app target
2. Add the following to the info.plist of the watchOS *app* target:

<key>NSAppTransportSecurity</key>
<dict>
	<key>NSAllowsArbitraryLoads</key>
	<true/>
</dict>

3. Build and run.


OR


1. Open attached sample project "FooProject"
2. Build and run

Expected Results:
Xcode should propagate "validateWatchKitApplicationInfoDictionary" errors up to the developer. They should not need to look into the console logs to find this error.

Actual Results:
User has to go into the app console logs to find the plist error and run their app. See the attached log.

Version:
Xcode-beta (7A165t)

Notes:
http://stackoverflow.com/q/31641162/5158230

Configuration:
Any Xcode project with a WatchOS 2 app target containing an invalid key it's info.plist. 

Attachments:
'FooProject.zip', 'Screen Shot 2015-07-26 at 2.56.07 PM.png', 'Simulator Screen Shot Jul 26, 2015, 2.56.55 PM.png', 'Simulator Screen Shot Jul 26, 2015, 2.55.41 PM.png' and 'WatchKit_2015_07_29_16_32_12-0400.log' were successfully uploaded.

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!