Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Install OS X 10.9 from Apple on a Mac (tried on a retina Macbook Pro)
Then install from alpha or beta channel of Xamarin Studio.
Launch Xamarin Studio.
After it starts all you have to do is select "Quit" from the Xamarin Studio menu.
XS will never exit. Open Activity Monitor. Note that the process will typically consume 50% of the CPU with 13-15 threads, etc.
Can confirm, I believe Rodrigo is already working on it.
Ok, thanks. I appreciate the update.
Please switch to the stable channel in the meanwhile.
We're working as fast as we can to release new versions of the betas that work with Mavericks.
I unfortunately cannot switch to the stable channel since I'm using the new async/await stuff and thus need Mono 3.0.
Any kind of ETA on a fix for this?
Can someone at least comment if this fix is days or weeks out?
For now I'm running Xamarin Studio (alpha) on my Surface Pro until a fix comes out.
We have internal builds of our stack for Mavericks that are under testing. We're trying to release them next week.
Thanks-that would be great if there is a release any down now.
The fact that I can Xamarin Studio on multiple platforms is great and my backup for now but nevertheless I look forward to running this again on my rMBP.
Please use the alpha channel for now as we release support for Mavericks on it.
We'll promote the many components of our stack there to beta over the coming week.
Thanks--I just updated via the alpha channel. (I had gone back to the stable channel for some of my project work that didn't require Mono 3.)
So now that I'm back on the alpha channel I'm bit by this issue: http://forums.xamarin.com/discussion/3010/deployment-failed-because-of-an-internal-error-failure-install-failed-update-incompatible
The same app/code works fine from non-OSX Mavericks (e.g. Windows 8 or OSX 10.8.4). And the app has been removed from the phone as well before trying to deploy.
I can open another bug unless this is a known issue. Or try some other debugging to figure out if it is an issue on my side somehow.
Reopening for further investigation by the Android team.
@Gerry: Please see the troubleshooting page:
It's possible that your Debug signing key changed, and/or you didn't fully uninstall the app from the target.
(I have seen circumstances where uninstalling the app didn't fully uninstall the app, as `adb shell pm list packages` would still show the app. Don't ask me how. If/when this happens, you need to use `adb uninstall` to remove the package.)
Furthermore, I don't think that Xamarin.Android 4.7.8 will work properly on Mavericks. You will need the forthcoming 4.7.10 alpha.
Ok, I was able to get it to install. What I did (whether this makes a difference or not I don't know):
1. After getting the deploy issue from Mavericks I went back to my Surface Pro and rebuilt and installed on device (XS 4.0.8 Build 2, Xamarin.Android 4.7.8)
2. Used settings/apps to remove my app
3. Went back to mavericks and did a clean all/rebuild all, and install.
This time it worked.
As far as any issues with 4.7.8 on Mavericks, are there known issues that are documented somewhere?
For now I'm going to try using it on Mavericks.
> As far as any issues with 4.7.8 on Mavericks, are there known issues that are
> documented somewhere?
Many Xamarin.Android tools embed the Mono runtime, so all "older Mono 3.0"+Maverick issues will also potentially appear when using an anything prior to 4.7.10, e.g. the hang that this bug reports.
The Mono 2.10-based Xamarin.Android 4.6.x is reportedly fine on Maverick.
We have checked this issue and we are able to use XS 4.2.4 (build 266) on Maverick OSx 10.9.3.
And as per comment 13 this issue is working fine.
Hence closing this issue.