Bug 34205 - Changes to Watch app storyboards are not present when re-deploying
Summary: Changes to Watch app storyboards are not present when re-deploying
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 9.0 (iOS9)
Hardware: PC Mac OS
: Normal normal
Target Milestone: C6SR1
Assignee: Bugzilla
Depends on:
Reported: 2015-09-23 09:16 UTC by Adam Hartley [MSFT]
Modified: 2015-12-02 11:43 UTC (History)
6 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 Adam Hartley [MSFT] 2015-09-23 09:16:16 UTC
## Steps to reproduce

1. Create a new iOS project (e.g., single view app).
2. Add a new WatchKit App extension
3. Build and run the WatchKit Extension in the iOS Simulator (iPhone 6 iOS 9.0)
4. Observe the default interface is present
5. Open Interface.storyboard in the WatchKit App and make some changes (e.g., add a button)
6. Re-run the WatchKit Extension 

## Expected result

Changes made to the storyboard should be present (e.g., the button added should be visible)

## Actual result

No changes are present - the interface remains the same

## Notes

Cleaning the solution has no effect.

A possible workaround is to change the Bundle Identifier each time the storyboard has been edited.

=== Xamarin Studio ===

Version 5.9.7 (build 9)
Installation UUID: 9932d50e-3095-4eb8-a4d2-d3b271c86a02
	Mono 4.0.4 ((detached/cb6d6b2)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400040002

=== Apple Developer Tools ===

Xcode 7.0 (8227)
Build 7A220

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: d8e9592
Branch: master
Build date: 2015-09-18 23:22:05-0400

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/Adam/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.4   (API level 19)
		5.0   (API level 21)
		5.1   (API level 22)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: (Business Edition)

=== Build Information ===

Release ID: 509070009
Git revision: 31fa64709030b3edb971237780a452a4c69943c4
Build date: 2015-09-17 11:44:37-04
Xamarin addins: b105d33d8cd72911ff2cf3ee0b7715d37e5f19a6

=== Operating System ===

Mac OS X 10.10.5
Darwin Adams-Retina-MacBook-Pro.local 14.5.0 Darwin Kernel Version 14.5.0
    Wed Jul 29 02:26:53 PDT 2015
    root:xnu-2782.40.9~1/RELEASE_X86_64 x86_64
Comment 3 Mohit Kheterpal 2015-09-24 07:10:02 UTC
I have checked this issue and observed that this issue is occurring with stable iOS 9 builds i.e. with XS + X.iOS only when we use Xcode 7, but when I switch Xcode 7 to xcode 6.4 and deploy application on simulator iOS 8.4 then it start working fine. 

So as per my understanding this issue is due to Xcode 7, as its working fine with Xcode 6.4 with same builds.

Comment 5 Rolf Bjarne Kvinge [MSFT] 2015-11-04 12:57:06 UTC

maccore/master: 5798376ef176f3cd448441dafc51fd78f22c0e7e
Comment 6 Mohit Kheterpal 2015-12-02 11:43:26 UTC
I have checked this issue with master monotouch- and observed that this issue has been resolved with the same build with Xcode 7.1

Hence closing this issue.