Bug 28967 - Watch extension versions do not automatically update to match parent app
Summary: Watch extension versions do not automatically update to match parent app
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 5.9
Hardware: PC Mac OS
: Normal normal
Target Milestone: 5.9
Assignee: Vincent Dondain [MSFT]
Depends on:
Reported: 2015-04-10 04:57 UTC by James Clancey
Modified: 2015-04-21 10:58 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description James Clancey 2015-04-10 04:57:01 UTC
Apple forces you to have matching bundle versions on your App and your extension and your watch app.

Our default template makes the Extension and Watch app have a version of "1" where the default for apps is "1.0".  We need to fix the template.

But further more we should auto set the extension/watch app to match the parent app during build since it is a requirement. Further more we hide the versions in the plist editor for watches/extensions. You have to view the source to edit it.
Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-04-10 05:29:43 UTC
CC Vincent for the template and plist editor issues.

The MSBuild tasks should probably copy the containing app's CFBundleVersion to the extensions/watch app (possibly only if the extensions/watch app don't already specify a CFBundleVersion).
Comment 2 Vincent Dondain [MSFT] 2015-04-10 12:09:13 UTC
Hey James, I was aware of this by reading the app submission doc and testing everything with Chris Hardy, when he tried to submit his app. 

"Make sure the version and build numbers for your iPhone app, WatchKit extension, and WatchKit app are the same in the binary you upload."

This has been implemented last week (before the XS freeze).

We now show the build and version numbers in the WatchKit extension and WatchKit app plist and automatically use the parent's app info.

So I'm happy to say that all of that has been fixed template wide and has been merged to the XS 5.9 branch. 

It will be available on the alpha channel soon.