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.
System.InvalidOperationException: The underlying Task is already in one of the three final states: RanToCompletion, Faulted, or Canceled.
at System.Threading.Tasks.TaskCompletionSource`1[System.Int32].SetException (IEnumerable`1 exceptions) [0x00000] in <filename unknown>:0 (code.cs:1)
at System.Threading.Tasks.TaskCompletionSource`1[System.Int32].SetException (System.Exception exception) [0x00000] in <filename unknown>:0 (code.cs:1)
at System.Threading.Tasks.TaskFactory`1[System.Int32].InnerInvoke (System.Threading.Tasks.TaskCompletionSource`1 tcs, System.Func`2 endMethod, IAsyncResult l) [0x00000] in <filename unknown>:0 (code.cs:1)
at System.Threading.Tasks.TaskFactory`1+<FromAsyncBeginEnd>c__AnonStorey5`3[System.Int32,System.Byte,System.Int32,System.Int32].<>m__0 (IAsyncResult l) [0x00000] in <filename unknown>:0 (code.cs:1)
at System.Net.WebAsyncResult.CB (System.Object unused) [0x00000] in <filename unknown>:0 (code.cs:1)
This is a 100% new crash (didn't exist in 4.10.1).
I don't have a repro (should be obvious from last changes in mono i hope).
> should be obvious from last changes in mono i hope
Xamarin.Android 4.10.1 uses Mono commit 433017c0. Xamarin.Android 4.11.0 uses Mono commit 17867123. There are 808 commits between the two.
It won't be obvious. :-)
A repro case is always useful.
mareks tells me that this was _probably_ fixed by: https://github.com/mono/mono/commit/8f1a0ccc
Fixed in monodroid-4.12-series/01786544.
A repro would still be handy so we can verify the fix.
Today we have tried to verify this issue, but we are not sure about the steps.
Could you please provide some steps or test sample so that we can verify this issue?
Looks like we don't have an exact repro (and neither does the reporter. See:
> I don't have a repro
from comment 0.
I have checked this issue with following builds:
X.S 4.2.3(build 54)
I am not seeing this issue even I am having some threads in my class and I have debug the application after setting breakpoint.
Hence, closing this issue
@ Grigory, Please feel free to reopen this issue if you still seeing this issue