René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Distribution build for watch target fails","articleBody":"**Environment**\r\nProvide version numbers for the following components (information can be retrieved by running `tns info` in your project folder or by inspecting the `package.json` of the project):\r\n - CLI: 6.4.1\r\n - Cross-platform modules: 6.4.2\r\n - iOS Runtime: 6.4.2\r\n\r\n**Describe the bug**\r\n\u003c!-- A clear and concise description of what the bug is. Please, explain whether it's a build time error or a runtime error. More detailed logs can be easily obtained by following the instructions in this guide: https://docs.nativescript.org/get-support#how-to-obtain-diagnostic-reports. --\u003e\r\nI have added a watch project to my Nativescript project by following the instructions from here #4589 . I can successfully run `tns prepare ios` and the watch project is included in the xcode project afterwards. \r\nI am using manual code signing to sign the iOS app as well as the watchOS app. Which both works perfectly fine as long as I do a development build. \r\n\r\nBut once I try to run the distribution build by providing the distribution profile via the `--provision` option I get the following error:\r\n\r\nerror: Provisioning profile \"Generic Profile for Internal Deployment\" doesn't include signing certificate \"Apple Development: John Doe (XXXXX)\". (in target 'watchapp Extension' from project '...')\r\n\r\nSo it looks like Provisioning Profile is updated but the wrong signing certificate is used. So looking into the autogenerated project.pbxproj reveals the following build setting for the watchapp and watchextension:\r\n`\"CODE_SIGN_IDENTITY[sdk=iphoneos*]\" = \"iPhone Distribution\";`\r\n\r\nThis will apply the code settings only to iOS SDK targets. And hence the signing certificates for the watch project don't get updated. Changing the build setting for the watch targets to \r\n`\"CODE_SIGN_IDENTITY\" = \"iPhone Distribution\";`\r\nfixes the problem. \r\n\r\nI assume the fix could be done simply by checking for the target in here:\r\n[pbxproj-dom](https://github.com/NativeScript/pbxproj-dom/blob/master/xcode.ts#L182)\r\n\r\nUnfortunately the code signing still fails for the distribution build after this fix. The `--provision` option makes sure that the correct provisioning profile is used when exporting the archive and building the ipa. \r\nThis is done by passing an exportOptions.plist file to xcodebuild. \r\n\r\nThis file is autogenerated by Nativescript during the tns build and it needs to state the correct provisioning profile for each target. But unfortunately the [export-options-plist-service.ts](https://github.com/NativeScript/nativescript-cli/blob/master/lib/services/ios/export-options-plist-service.ts#L66) provides only the profile for the iOS target. And therefore the archive export fails with the follwoing error:\r\n\r\nError Domain=IDEProvisioningErrorDomain Code=9 \"\"watchapp.app\" requires a provisioning profile.\" UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription=\"watchapp.app\" requires a provisioning profile., NSLocalizedRecoverySuggestion=Add a profile to the \"provisioningProfiles\" dictionary in your Export Options property list.}\r\n\r\nAdding the following lines in export-options-plist-service.ts fixes the issue \r\n``\u003ckey\u003e${projectData.projectIdentifiers.ios}.watchkitapp\u003c/key\u003e\r\n   \u003cstring\u003e${provision}\u003c/string\u003e\r\n   \u003ckey\u003e${projectData.projectIdentifiers.ios}.watchkitapp.watchkitextension\u003c/key\u003e\r\n   \u003cstring\u003e${provision}\u003c/string\u003e``\r\n\r\n\r\n\r\n**To Reproduce**\r\nRun Nativescript project with watch extension and provide distribution profile via the `--provision` option\r\n\r\n**Expected behavior**\r\nipa should be successfully created and signed \r\n\r\n","author":{"url":"https://github.com/siewedu","@type":"Person","name":"siewedu"},"datePublished":"2020-04-06T15:00:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/5291/nativescript-cli/issues/5291"}