Bug 37780 - Popover segue style casues build to fail with blank error message
Summary: Popover segue style casues build to fail with blank error message
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jose Gallardo
Depends on:
Reported: 2016-01-18 21:46 UTC by Matthew Orlando
Modified: 2016-12-23 00:12 UTC (History)
9 users (show)

Tags: BZCU
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 Matthew Orlando 2016-01-18 21:46:04 UTC
Create new Xamarin Portable (shared) project
Add a second ViewController to Main.storyboard
Create a segue between the two VCs and choose Popover Presentation style
Build the iOS project

The entire output of the build is as follows:

1>------ Build started: Project: App5.iOS, Configuration: Debug iPhone ------
1>  Generated session id: 22824a3fd65b76ad8c03fd7694e35be1
1>  Generated build app name: App5iOS
1>  Connecting to Mac server
1>C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(997,3): error : 
========== Build: 0 succeeded, 1 failed, 1 up-to-date, 0 skipped ==========

There is no indication of what the error is. Switching the presentation style to "Push" fixes the build.
Comment 1 John Nolan 2016-05-10 12:12:46 UTC
I have reproduced this error. 

Dev PC Environment 

Visual Studio Professional 2015 Version 14.0.25123.00 Update 2
Xamarin (0dd817c)
Xamarin.iOS (3a25bf1)

Macbook (Agent) Environment

OS X El Capitan Version 10.11.4
Simulator Version 9.3
Xcode Version 7.3 (7D175)

The issue occurs when one selects Popover Presentation style (two versions appear a deprecated and new) in the Segue "Widget" Properties. This causes an anonymous build error with not details!
Comment 2 Jose Gallardo 2016-05-11 15:00:25 UTC
Hi John and Matthew,

I couldn't repro this issue with latest 4.1.x build (which is currently in the Beta channel).

The only error I can see, is that no Anchor is set for the Segue. But once the anchor is set, the project builds successfully.

Can you please confirm if you're still seeing this issue with Beta builds?

Comment 3 John Nolan 2016-05-12 11:10:54 UTC
Hi Jose,

Many thanks for responding.

Unfortunately, internal processes mean that we can only use "stable" framework builds - so I cannot make use of the "beta" you refer to :( 

However, I added an Anchor using the anchor's LocalizationID and the project now builds and displays the popover correctly. Could you also remove the deprecated Popover from the "Segue" drop down as this will cause build errors also. 

Is there any way you could provide an appropriate exception message such as "null anchor specified for segue xxxxx" or perhaps "please select an anchor when using a Present As Popover segue" to stop that anonymous build message appearing?

In any case, thanks for your help Jose - you saved the day. 

All the best, 

Comment 4 John Nolan 2016-05-12 11:11:58 UTC
Also, please see my stack overflow post here for details:

Comment 5 Matthew Orlando 2016-05-16 23:22:32 UTC
Hi Jose,

I am now seeing the behavior you describe in the beta channel. This specific bug seems to have been fixed.
Comment 6 Jose Gallardo 2016-12-23 00:12:47 UTC
Resolving the bug as fixed, based on Comment 5.