Bug 13471 - Xamarin Studio does not open after failed update
Summary: Xamarin Studio does not open after failed update
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 6.0.0 (C7)
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-07-25 09:43 UTC by Prashant Cholachagudda
Modified: 2017-07-21 14:10 UTC (History)
7 users (show)

Tags:
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:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Prashant Cholachagudda 2013-07-25 09:43:33 UTC
Xamarin studio does not launch on Mac OS after update fails. XS log https://gist.github.com/chrisntr/7eea7d5e0d0813e2a6c7
Comment 2 Diviner 2013-07-26 02:38:33 UTC
Today I start Xamarin Studio and it prompts me that update. I go on but it prompts me that the update is failed in a few seconds.

So I close the error dialog, and re-launch the existing Xamarin Studio, but it can't start anymore.

And then I download the new install package from official site and try to install it, but the installation progress also has problem. 
( XamarinInstaller.dmg version: 
  Install Xamarin 3.0.0 
  Last modify date: 2013-07-25 08:00:22am )

After double click on the installation button in the screen screen,
http://docs.xamarin.com/static/guides/ios/getting_started/installation/mac/index/Images/installer.png

It doesn't navigate to the next screen:
http://docs.xamarin.com/static/guides/ios/getting_started/installation/mac/index/Images/required_components.png

Finally I uninstall the existing Xamarin Studio and install it from scretch. The installation problem is still there. I find that the old folders of Xamarin and XamarinStudio-4.0 are leaving on hard disk. I delete it manually and start install again, but no luck.

This bug stuck my coding work at all.
Comment 3 Mikayla Hutchinson [MSFT] 2013-07-26 17:53:10 UTC
Is there anything in the Console.app system messages.log when it fails to launch?
Comment 4 Howard Fore 2016-07-21 01:22:46 UTC
I know this is old (and maybe this Bugzilla is abandoned) but I've had the same experience. After the new version failed to open I looked at it in Terminal. I noticed the file permissions on the replaced .old versions had my user name as the user and were set to 755. The new broken version was set to be owned by root and was 700. After chmoding and chowning the new one, it opened and seems to be operational as expected.

One wrinkle in my setup is that my user account isn't admin, by the rule of the corporate infosec people. I have to enter my admin user account in order to install Studio.
Comment 5 iain 2016-10-18 15:30:18 UTC
Setting this back to new because of c#4 so we can attempt to confirm it
Comment 6 Amy Burns 2017-07-21 14:10:36 UTC
I've been going through older, outstanding bugs and attempted to reproduce this issue based on the bug description with the latest Visual Studio 2017 for Mac Preview version 7.1, and I was unable to hit the problem. I've chatted to Iain about this and he has also not been able to reproduce this issue.

If this issue is still occurring, please reopen this report and attach the following, if possible:

-Detailed reproduction steps 
-Version information (Visual Studio → About Visual Studio menu) 
-Logs (Help → Open Log Directory, zip logs for the last 10 days) 
-Optional: project to reproduce your issue