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.
# Steps to reproduce
Just run the attached project
# Expected behavior
Must work just fine
# Actual behavior
Throws MissingMethodException or similar error
# Supplemental info (logs, images, videos)
This was working smoothly before the VS 2017 15.2 update. In this case, seems the problem is with ValueTuple types.
# Test environment (full version information)
Microsoft Visual Studio Enterprise 2017
Version 15.2 (26430.4) Release
Microsoft .NET Framework
Installed Version: Enterprise
Visual Basic 2017 00369-90000-00000-AA049
Microsoft Visual Basic 2017
Visual C# 2017 00369-90000-00000-AA049
Microsoft Visual C# 2017
Application Insights Tools for Visual Studio Package 8.6.00404.2
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 2017 15.0.30503.0
ASP.NET and Web Tools 2017
ASP.NET Web Frameworks and Tools 2017 5.2.50303.0
For additional information, visit https://www.asp.net/
Azure App Service Tools v3.0.0 15.0.30209.0
Azure App Service Tools v3.0.0
Common Azure Tools 1.9
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
JetBrains ReSharper Ultimate 2017.1.2 Build 108.0.20170428.75743
JetBrains ReSharper Ultimate package for Microsoft Visual Studio. For more information about ReSharper Ultimate, visit http://www.jetbrains.com/resharper. Copyright © 2017 JetBrains, Inc.
KofePackagePackage Extension 1.0
KofePackagePackage Visual Studio Extension Detailed Info
Merq 1.1.17-rc (cba4571)
Command Bus, Event Stream and Async Manager for Visual Studio extensions.
Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Mono Debugging for Visual Studio Mono.Debugging.VisualStudio
Support for debugging Mono processes with Visual Studio.
NuGet Package Manager 4.2.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
SQL Server Data Tools 15.1.61702.140
Microsoft SQL Server Data Tools
TypeScript tools for Visual Studio
Xamarin 18.104.22.1683 (c871575)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android SDK 22.214.171.124 (448f54f)
Xamarin.Android Reference Assemblies and MSBuild support.
Xamarin.iOS and Xamarin.Mac SDK 10.10.0.30 (30b6e87)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
Created attachment 22087 [details]
Test project to reproduce the issue
Could you elaborate the issue.
I am not able to reproduce this issue on my test machines. Detailed steps to reproduce and error would be very useful
There are two projects -- App3 and ClassLibrary1.
1. Open App3.
2. App3 references ClassLibrary1. If you don't see ClassLibrary1 in your solution, just add it.
3. Run App3, and you'll get a runtime error.
Any update on this? This bug turned my Android projects simply useless.
Unable to repro with Visual Studio 2017 15.2, Xamarin 126.96.36.1996, and Xamarin.Android 188.8.131.52. I did the following:
1. Opened the App3 .csproj file (creates a new solution).
2. Added the ClassLibrary1 project to the new solution.
3. Build > Build Solution.
4. Deploy to a Nexus 5 device running Android 6.0.1.
App3 runs without throwing an exception. I was able to leave it running on the device for several minutes.
Can you update to the latest version of Xamarin.Android and try it again? Also, are you getting this error on an emulator or on a device?
I am no longer able to reproduce this issue on following setup -
=== Visual Studio Enterprise 2017 for Mac ===
Version 7.0.1 (build 24)
Installation UUID: cbe44f28-b7cf-4fec-aed3-4f13bc08336d
Mono 184.108.40.206 (2017-02/5077205) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 500010001
=== NuGet ===
=== .NET Core ===
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.0.1/lib/mono/msbuild/15.0/bin/Sdks
=== Xamarin.Profiler ===
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler
=== Xamarin.Android ===
Version: 220.127.116.11 (Visual Studio Enterprise)
Android SDK: /Users/prashantvc/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
6.0 (API level 23)
7.0 (API level 24)
7.1 (API level 25)
SDK Tools Version: 26.0.1
SDK Platform Tools Version: 25.0.4
SDK Build Tools Version: 25.0.2
Java SDK: /usr
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
Android Designer EPL code available here:
=== Xamarin Inspector ===
Build date: Fri, 21 Apr 2017 17:57:12 GMT
=== Apple Developer Tools ===
Xcode 8.3.3 (12175.1)
=== Xamarin.Mac ===
Version: 18.104.22.168 (Visual Studio Enterprise)
=== Xamarin.iOS ===
Version: 10.10.0.36 (Visual Studio Enterprise)
Build date: 2017-05-22 16:30:53-0400
=== Build Information ===
Release ID: 700010024
Git revision: 7ab1ca2ced6f584e56b7a0d4d321d00775cd95c9
Build date: 2017-05-19 05:44:51-04
Xamarin addins: 08d17158f3365beee5e60f67999e607cce4b3f93
Build lane: monodevelop-lion-d15-2
=== Operating System ===
Mac OS X 10.12.5
Darwin 16.6.0 Darwin Kernel Version 16.6.0
Fri Apr 14 16:21:16 PDT 2017
=== Enabled user installed addins ===
I noticed this sample project is using project.json which was deprecated by the .NET team in favor for <PackageReference>. It has also been noted that multiple members were not able to reproduce this issue.
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.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.