1

I'm trying to send my iOS app to the App Store right now. It compiles fine and installs onto my test device without a single error or even warning. I have an Apple Watch App that is going to go along with it but it seems to be giving me problems. When I create the Archive of the app, I get the following 5 warnings: 

[App Name] WatchKit Extension

warning: skipping copy phase strip, binary is code signed: /Users/***/Library/Developer/Xcode/DerivedData/***/Build/Intermediates/ArchiveIntermediates/***/IntermediateBuildFilesPath/UninstalledProducts/*** Watch App.app/_WatchKitStub/WK

warning: skipping copy phase strip, binary is code signed: /Users/***/Library/Developer/Xcode/DerivedData/***/Build/Intermediates/ArchiveIntermediates/***/IntermediateBuildFilesPath/UninstalledProducts/*** Watch App.app/*** Watch App


[App Name]

warning: skipping copy phase strip, binary is code signed: /Users/***/Library/Developer/Xcode/DerivedData/***/Build/Intermediates/ArchiveIntermediates/***/IntermediateBuildFilesPath/UninstalledProducts/*** WatchKit Extension.appex/*** Watch App.app/_WatchKitStub/WK

warning: skipping copy phase strip, binary is code signed: /Users/***/Library/Developer/Xcode/DerivedData/***/Build/Intermediates/ArchiveIntermediates/***/IntermediateBuildFilesPath/UninstalledProducts/*** WatchKit Extension.appex/*** Watch App.app/*** Watch App

warning: skipping copy phase strip, binary is code signed: /Users/***/Library/Developer/Xcode/DerivedData/***/Build/Intermediates/ArchiveIntermediates/***/IntermediateBuildFilesPath/UninstalledProducts/*** WatchKit Extension.appex/*** WatchKit Extension

And then it's proceeded with this error:

From Xcode v6.3

Anyone else having these issues? Any help would be very appreciated!

Jay Mehta
  • 1,431
  • 19
  • 40
Mario A Guzman
  • 3,483
  • 4
  • 27
  • 36
  • FYI - I put asterisks to cover up any personal information above and cropped out any names. Thanks for your understanding! – Mario A Guzman Apr 10 '15 at 05:04
  • Have you setup an appstore provisioning profile for the watch extension? – Rhythmic Fistman Apr 10 '15 at 06:09
  • @RhythmicFistman I have one for the app (obviously :] ) and I set one up for the WatchKit App. I thought I needed one for the Extension but when I copy the Bundle ID for the extension from Xcode and I paste it into a new prov. profile in the developer portal, it says it's an invalid name. I thought it probably wouldn't take anything ending in .watchkitextension. Am I wrong on this? If this is the case, then I have to contact Apple because as far as Im concerned, the bundle IDs have to be similar to the App Bundle ID (Same Prefix). – Mario A Guzman Apr 10 '15 at 06:31
  • See [this answer](http://stackoverflow.com/a/29529019/2210682) I wrote yesterday – songchenwen Apr 10 '15 at 07:05
  • possible duplicate of [Watchkit Extension - No matchin provisioning profiles found](http://stackoverflow.com/questions/28816339/watchkit-extension-no-matchin-provisioning-profiles-found) – dogsgod Apr 10 '15 at 18:43

2 Answers2

4

I had both of these problems when I created my WatchKit app.

(1) For your first problem: warning: skipping copy phase strip.

I found the solutions here:

Warning during archive App with iOS 8 Extension in Xcode 6

and here:

Xcode 6 Archiving and get a warning "Skipping copy phase strip ,binary is code signed" when add "share extension" to target

Specifically, here are the steps I used to fix the problem:

  1. Start Xcode and open your project.

  2. Select the blue project icon in the upper-left-hand corner.

  3. In second column that contains sections: PROJECT and TARGETS, select your main target under the TARGETS section.

  4. Select the “Build Settings” tab.

  5. Scroll down to the “Deployment” section.

  6. Find and expand the section called “Strip Debug Symbols During Copy”

  7. Find the row called "Release".

  8. Change the value from "Yes" to "No".

Build Settings > Deployment > Strip Debug Symbols

(2) For your second problem: Failed to locate or generate matching signing assets The solutions are here:

No matching provisioning profiles found for WatchKit extension when submitting to App Store

and here:

Submit WatchKit Provisioning Error

I had to regenerate the "Distribution" Provisioning Profile that I was using to submit my entire app, before I included the WatchKit extension. Specifically, these steps fixed my problem:

I logged onto developer.apple.com, selected "Certificates, Identifiers & Profiles".

  1. On the Certs IDs & Profiles website > Provisioning Profiles page, click the App Store profile.
  2. Click 'Edit'
  3. Click 'Generate'
Community
  • 1
  • 1
Alex D
  • 301
  • 1
  • 4
  • So for the first step you listed about "Strip Debug Symbols During Copy" didn't work until I got your second step to work. I'm not sure why, they seem somewhat unrelated. The second step was that Xcode had generated a provisioning profile for me without me knowing (my fault) and gave it some unusual name (which is why I would miss it every time I would go into the dev portal). When I looked carefully, I saw it and recreated it with a name I wanted. It worked and it caused the first step to work too! Thanks! – Mario A Guzman Apr 17 '15 at 14:46
  • You are welcome! I did not expect that the second step would help resolve the first step, but I am glad it is working for you now. – Alex D Apr 17 '15 at 17:21
3

I have a solution that worked (for me)

First: Just make sure that you enabled all services that you used on your app on your (Watch Kit App) and (Watch Kit Extension),

For example if you used iCloud on your native app, you should enable iCloud on your (Watch Kit App) and (Watch Kit Extension) even if you didn't use iCloud on your watch app.

Same goes for app groups..

Second: Make sure the bundle identifier on (Watch Kit App) and (Watch Kit Extension) has to extend the native app,

For example if the app com.company.myapp the (Watch Kit App) identifier should be: com.company.myapp.watchkitapp and on (Watch Kit Extension) should be: com.company.myapp.watchkitextension

Hope this helps.

Jouhar
  • 288
  • 4
  • 9