Bug 24166 - crash when selecting popover segue
Summary: crash when selecting popover segue
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS Designer ()
Version: 5.5
Hardware: PC Mac OS
: Normal normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2014-10-30 12:29 UTC by violet_blue
Modified: 2014-11-06 06:09 UTC (History)
5 users (show)

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

segue popover xamarin ide crash (201.35 KB, image/jpeg)
2014-10-30 12:29 UTC, violet_blue

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 violet_blue 2014-10-30 12:29:06 UTC
Created attachment 8564 [details]
segue popover xamarin ide crash

when i select popover for the green background view, xamarin crashes.
Comment 1 Alan McGovern 2014-10-30 12:41:02 UTC
Can you share the storyboard with us that triggers the problem?

We have fixed a bug which sounds very similar to this, so I think I can just mark this as 'resolved -> fixed', but i want to be sure your specific case is working before I do that.
Comment 2 Alan McGovern 2014-11-06 06:09:50 UTC
I'll assume that the bug we fixed is the same as the one you were reporting. If Xamarin Studio 5.7+ does not fix this issue for you, do let us know. In the meantime, if you do have a way to reproduce the issue and can share it with us, please reopen the bug. Then we will be able to double check that they are definitely the same issue.