Bug 45613 - Selecting Segue in storyboard destroyes segue
Summary: Selecting Segue in storyboard destroyes segue
Status: VERIFIED DUPLICATE of bug 44401
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 4.2.0 (C8)
Hardware: PC Windows
: --- blocker
Target Milestone: 4.2.1 (C8SR1)
Assignee: Bugzilla
Depends on:
Reported: 2016-10-18 07:20 UTC by Robert van Hoornaar
Modified: 2016-10-18 22:00 UTC (History)
8 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 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 Robert van Hoornaar 2016-10-18 07:20:05 UTC
# Steps to reproduce
Open existing storyboard build with older version
select an existing push (show) segue

# Expected behavior
Expected to see the properties as defined in the past

# Actual behavior
The property editor shows the old properties and then removes segue type. Combobox is cleared and cannot be selected any more. Building gives error "No anchor for segue selected"

# Supplemental info (logs, images, videos)

# Test environment (full version information)
			  Latest Visual Studio integration
Comment 1 Alan McGovern 2016-10-18 17:03:46 UTC

*** This bug has been marked as a duplicate of bug 44401 ***