Bug 44401 - iOS Segue always defaults to popoverSegue
Summary: iOS Segue always defaults to popoverSegue
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 4.2.0 (C8)
Hardware: PC Windows
: Normal major
Target Milestone: ---
Assignee: Bugzilla
: 45613 45940 46562 50714 ()
Depends on:
Reported: 2016-09-16 00:51 UTC by Jon Douglas [MSFT]
Modified: 2017-01-06 14:59 UTC (History)
12 users (show)

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

IDE Logs (135.43 KB, application/zip)
2016-10-18 18:40 UTC, Mohit Kheterpal

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 Jon Douglas [MSFT] 2016-09-16 00:51:43 UTC

It seems that when creating a segue from one UITableViewController to another UITableViewController, the segue option never actually saves the user's choice. I have confirmed that this behavior does indeed work correctly in XS, but not in VS. Actually in VS, I have also noticed that initially creating a segue will also default to the same behavior. However the user will not notice it until they run into an error of having no anchor for the popoverSegue.

Here's a video demonstrating what I'm seeing:


*Expected Behavior:

The segue should save the selection that was picked and not iterate through them all and default to popoverSegue.

*Version Information:

Microsoft Visual Studio Professional 2015
Version 14.0.25421.03 Update 3
Microsoft .NET Framework
Version 4.6.01038

Installed Version: Professional

Xamarin (c4382f5)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android (0e59c36)
Visual Studio extension to enable development for Xamarin.Android.

Xamarin.iOS (6c3fee4)
Visual Studio extension to enable development for Xamarin.iOS.
Comment 1 Anthony Rouneau 2016-09-28 07:00:19 UTC
Same problem here.
Started right after the Xamarin.iOS 10 big update.


Microsoft Visual Studio Community 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.6.01055

Installed Version : Community

Xamarin (7603786).
Xamarin.Android (c1d1c79)
Xamarin.iOS (29910bb)
Comment 2 Anthony Rouneau 2016-09-28 07:05:42 UTC
I'd like to add that the problem seems to appear only when I click on a segue and try to modify its properties.

So if I modify the XML manually and don't touch the segues in the designer, the segues keep their kind. Otherwise, the segues lose their kind and gain the kind "popoverSegue" without any anchor.
Comment 3 Robert van Hoornaar 2016-10-18 07:25:04 UTC
I have the same problem since last update.
This is such a showstopper. I am not able to add segues to the storyboard now anymore. Hacking the XML by hand is something I try to avoid. That got me into trouble once before
Comment 4 Alan McGovern 2016-10-18 17:03:46 UTC
*** Bug 45613 has been marked as a duplicate of this bug. ***
Comment 5 Mohit Kheterpal 2016-10-18 18:40:27 UTC
Created attachment 18107 [details]
IDE Logs

I am able to reproduce this issue and getting same error i.e. 

"Severity	Code	Description	Project	File	Line	Suppression State
Error		Popover segue with no anchor	App89	C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets	1148	"

Build output : https://gist.github.com/Mohit-Kheterpal/9b406b9b71e4005dff81525ebfd69495
Comment 6 Alan McGovern 2016-10-26 18:39:35 UTC
*** Bug 45940 has been marked as a duplicate of this bug. ***
Comment 7 Alan McGovern 2016-10-26 18:40:09 UTC
This was actually fixed with https://github.com/xamarin/md-addins/commit/c1e6b07f20e4d1a7b90b51273c21a8904b06c35a but i used the other bug number in the commit message. This was reported multiple times.
Comment 8 Alan McGovern 2016-11-09 14:02:58 UTC
*** Bug 46562 has been marked as a duplicate of this bug. ***
Comment 9 iammehdi 2016-12-21 14:23:52 UTC
Hi Alan, 

I have the same issue, i have the latest updates, when i try to click the link to fix you provided i get a "404 page" can you please point me to the correct link for this fix?

Comment 10 Alan McGovern 2016-12-21 14:48:50 UTC
You'll need to get one of the Cycle9 builds which are currently in the alpha channel.
Comment 11 Alan McGovern 2017-01-06 14:59:07 UTC
*** Bug 50714 has been marked as a duplicate of this bug. ***