Bug 38548 - After upgrading to XF 2.0.1.6505, debugging Android build results in unhandled exceptions
Summary: After upgrading to XF 2.0.1.6505, debugging Android build results in unhandle...
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.0.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-02-08 18:28 UTC by John Hardman
Modified: 2016-12-20 23:23 UTC (History)
2 users (show)

Tags: Android VS2015 nullreferenceexception
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 FIXED

Description John Hardman 2016-02-08 18:28:56 UTC
After upgrading to use Xamarin.Forms 2.0.1.6505, debugging the Android build of my app from Visual Studio results in unhandled null reference exceptions with the following stack trace. Running the debug build but without using the debugger does not have any problems. Similarly, running and debugging on platforms other than Android seems to be fine.

System.NullReferenceExceptionObject reference not set to an instance of an object
Raw
System.Threading.WaitHandle.WaitOne(int millisecondsTimeout, bool exitContext)WaitHandle.cs:381
System.Threading.WaitHandle.WaitOne(int millisecondsTimeout)WaitHandle.cs:388
System.Threading.Timer.Scheduler.SchedulerThread()Timer.cs:395
System.Threading.ThreadHelper.ThreadStart_Context(object state)thread.cs:68
System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, object state, bool preserveSyncCtx)executioncontext.cs:581
System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, object state, bool preserveSyncCtx)executioncontext.cs:530
System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, object state)executioncontext.cs:519
System.Threading.ThreadHelper.ThreadStart()thread.cs:105
Properties & Custom Values
HResult	
-2147467261
TargetSite	
WaitOne
Comment 1 John Hardman 2016-02-08 18:29:36 UTC
Should have mentioned, I am using Visual Studio 2015 Enterprise.
Comment 2 Rui Marinho 2016-12-20 23:23:22 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction. 

For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d 

Warm regards, 
Xamarin Forms Team