Bug 55229 - System.ValueTuple isn't deployed
Summary: System.ValueTuple isn't deployed
Status: VERIFIED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 5.1
Hardware: PC Mac OS
: Highest critical
Target Milestone: 15.2
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2017-04-14 19:03 UTC by Jonathan Pryor
Modified: 2017-05-17 20:36 UTC (History)
4 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:
VERIFIED FIXED

Description Jonathan Pryor 2017-04-14 19:03:31 UTC
We have reports of an app deployed with the current Xamarin.Android 7.3 alpha crashing on startup:

> [Mono] Assembly Loader probing location: 'System.ValueTuple'.
> [monodroid-assembly] Could not load assembly 'System.ValueTuple' during startup registration.
> [monodroid-assembly] This might be due to an invalid debug installation.
> [monodroid-assembly] A common cause is to 'adb install' the app directly instead of doing from the IDE.

The same project doesn't have these problems with the current 7.2 stable.
Comment 3 Jonathan Pryor 2017-04-14 20:36:24 UTC
@akoeplinger believes that the issue in Comment #0 might be because System.ValueTuple.dll is now a facade assembly...which we're not shipping.

There is now a PR to add System.ValueTuple.dll to the mono bundle:

https://github.com/xamarin/xamarin-android/pull/559
Comment 4 Peter Collins 2017-04-19 16:56:32 UTC
This has since been merged into 15.2, marking as resolved.
Comment 5 Peter Collins 2017-04-19 17:43:08 UTC
I was able to reproduce this using msbuild on macOS from command line w/ monodroid/d15-2/40f69c3e000dbf31720337a02022ac2c3923801e installed:

> 04-19 12:50:39.353   752   752 D Mono    : Assembly Loader probing location: 'System.ValueTuple'.
> 04-19 12:50:39.354   752   752 F monodroid-assembly: Could not load assembly 'System.ValueTuple' during startup registration.
> 04-19 12:50:39.354   752   752 F monodroid-assembly: This might be due to an invalid debug installation.
> 04-19 12:50:39.355   752   752 F monodroid-assembly: A common cause is to 'adb install' the app directly instead of doing from the IDE.
And I can no longer reproduce in the same manner after installing monodroid/d15-2/1dcadca26816cc19eca8d3fa08b702cfcb4e68be, the app starts up and displays a qr code scanner without any fatal error.
Comment 6 thomas 2017-05-13 12:35:14 UTC
Just run into this today with VS 2017 Preview and have no idea what to do against it.

05-13 12:29:34.251 F/monodroid-assembly( 3919): Could not load assembly 'System.ValueTuple' during startup registration.
05-13 12:29:34.251 F/monodroid-assembly( 3919): This might be due to an invalid debug installation.
05-13 12:29:34.251 F/monodroid-assembly( 3919): A common cause is to 'adb install' the app directly instead of doing from the IDE.
Comment 7 Giorgos Papadakis 2017-05-16 13:28:26 UTC
Also in vs2017 same error on Xamarin.Android 7.3.0.13, appa crashes on launch

05-16 16:20:13.896 F/monodroid-assembly( 2820): Could not load assembly 'System.ValueTuple' during startup registration.
05-16 16:20:13.896 F/monodroid-assembly( 2820): This might be due to an invalid debug installation.
05-16 16:20:13.896 F/monodroid-assembly( 2820): A common cause is to 'adb install' the app directly instead of doing from the IDE.
Comment 8 Giorgos Papadakis 2017-05-17 20:36:37 UTC
Hey guys i am really stuck i do not know what to do. Is there a workaround.