Bug 37650 - Xamarin Studio options all greyed out after sumbitting to app store
Summary: Xamarin Studio options all greyed out after sumbitting to app store
Status: RESOLVED DUPLICATE of bug 34250
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 5.10 (C6SR3)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2016-01-13 16:22 UTC by David
Modified: 2016-01-14 16:54 UTC (History)
1 user (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 David 2016-01-13 16:22:46 UTC
Description of Problem:

OS EL Capitan 10.11.2

Most Xamarin studio menu options are greyed out including the quit menu option and all build options after signing and distributing a archive to apple using application loader. You have to force quit the application to get the options back.

Steps to reproduce the problem:
1. create a archive
2. click sign and distribute and when prompted use application loader to send to apple.

How often does this happen? 

Additional Information:

application loader version is 3.0
Comment 1 Lluis Sanchez 2016-01-14 16:54:33 UTC

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