Bug 11829 - Alpha bits debug build won't launch
Summary: Alpha bits debug build won't launch
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.8.x
Hardware: PC Mac OS
: High normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2013-04-17 12:25 UTC by Chris Hamons
Modified: 2014-01-14 14:24 UTC (History)
5 users (show)

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

Project that failed (12.68 KB, application/zip)
2013-04-17 12:25 UTC, Chris Hamons

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 Chris Hamons 2013-04-17 12:25:36 UTC
Release works however.

(From Debug Launch)

Forwarding debugger port 8969
Forwarding console port 8970
Detecting existing process
[Trace] error opening trace file: No such file or directory (2)
[libc] WARNING: generic atexit() called from legacy shared library
[monodroid-gc] GREF GC Threshold: 1800
Loaded assembly: /data/data/x15Minutes.x15Minutes/files/.__override__/15Minutes.dll
Loaded assembly: Mono.Android.dll [External]
[MonoDroid] Xamarin/Android Trial Mode Active
[AndroidRuntime] VM exiting with result code -1, cleanup skipped.

Testing with Craig at Evolve
Comment 1 Chris Hamons 2013-04-17 12:25:56 UTC
Created attachment 3823 [details]
Project that failed
Comment 2 Miguel de Icaza [MSFT] 2013-07-26 14:13:45 UTC
Jon, can you take a look at this and see if it is still there?
Comment 3 Jonathan Pryor 2013-07-26 14:52:35 UTC
Which IDE is this with? Which emulator is this with? Are any breakpoints set? Is there any other setup required?

I'm unable to reproduce this using Xamarin.Android 4.8.0-13, Xamarin Studio 4.0.10 (Build 7), and a Samsung Nexus 10, with no breakpoints set.
Comment 4 PJ 2013-11-19 17:06:06 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 5 Chris Hamons 2013-11-20 10:28:19 UTC
You can close this. It was with Xam Studio \ Android during the conference. I don't have the machine anymore to attempt to reproduce.

Sorry for the delay.
Comment 6 Chris Hamons 2014-01-14 14:24:59 UTC
Closing my own issue. Full circle.