Xamarin-android: [Bug] android logs being spammed with type mapping message

[GZidar]

Description

I am seeing a huge number (thousands) of log entries with the below text appearing in the output window:

W/monodroid-assembly typemap: unable to find mapping to a Java type from managed type 'System.Int32, mscorlib'

or

W/monodroid-assembly typemap: unable to find mapping to a Java type from managed type 'System.Byte, mscorlib'

I don't recall seeing this before. The two examples above are the most common but the same message appears for other types as well

Basic Information

• Version with issue: 4.6.0.800 (but also happened in 4.6.0.726)
• Android Support Library Version: AndroidX

VS bug #1130963

[SittenSpynne]

Happening for me after installing the newest VS for Mac updates. Relevant info:

=== Visual Studio Enterprise 2019 for Mac ===

Version 8.6 (build 4520)
Installation UUID: f862528f-499a-4c4c-aa48-db003253d392
    GTK+ 2.24.23 (Raleigh theme)
    Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638)

    Package version: 610000104

=== Mono Framework MDK ===

Runtime:
    Mono 6.10.0.104 (2019-12/5d03a6fe116) (64-bit)
    Package version: 610000104

=== Roslyn (Language Service) ===

3.6.0-3.20210.9+4eafdcb1bcbd8d3573f2ba6065e56d9b9ce4f8a3

=== NuGet ===

Version: 5.6.0.6591

=== .NET Core SDK ===

SDK: /usr/local/share/dotnet/sdk/3.1.300/Sdks
SDK Versions:
    3.1.300
    3.1.202
    3.1.200
    3.1.102
    3.1.101
    3.1.100
    3.0.101
    3.0.100
    2.2.300
    2.2.106
    2.1.506
    2.1.505
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/6.10.0/lib/mono/msbuild/Current/bin/Sdks

=== .NET Core Runtime ===

Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
    3.1.4
    3.1.2
    3.1.1
    3.1.0
    3.0.1
    3.0.0
    2.2.5
    2.2.4
    2.1.18
    2.1.17
    2.1.16
    2.1.15
    2.1.14
    2.1.13
    2.1.10
    2.1.9

=== Xamarin.Profiler ===

Version: 1.6.12.26
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Updater ===

Version: 11

=== Apple Developer Tools ===

Xcode 11.4 (16134)
Build 11E146

=== Xamarin.Mac ===

Version: 6.18.1.31 (Visual Studio Enterprise)
Hash: b3eedfed9
Branch: d16-6
Build date: 2020-04-09 10:22:36-0400

=== Xamarin.iOS ===

Version: 13.18.1.31 (Visual Studio Enterprise)
Hash: b3eedfed9
Branch: d16-6
Build date: 2020-04-09 10:22:36-0400

=== Xamarin Designer ===

Version: 16.6.0.329
Hash: d4f8bcd13
Branch: remotes/origin/d16-6
Build date: 2020-04-24 02:16:02 UTC

=== Xamarin.Android ===

Version: 10.3.1.0 (Visual Studio Enterprise)
Commit: xamarin-android/d16-6/3fe860a
Android SDK: /Users/<username>/Library/Developer/Xamarin/android-sdk-macosx
    Supported Android versions:
        7.0 (API level 24)
        8.0 (API level 26)
        8.1 (API level 27)

SDK Tools Version: 26.1.1
SDK Platform Tools Version: 29.0.5
SDK Build Tools Version: 28.0.3

Build Information: 
Mono: 165f4b0
Java.Interop: xamarin/java.interop/d16-6@2cab35c
ProGuard: xamarin/proguard/master@905836d
SQLite: xamarin/sqlite/3.31.1@49232bc
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-6@bfb66f3

=== Microsoft Mobile OpenJDK ===

Java SDK: /Users/<username>/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25
1.8.0-25
Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

=== Android SDK Manager ===

Version: 16.6.0.50
Hash: 5901879
Branch: remotes/origin/d16-6
Build date: 2020-04-30 04:01:22 UTC

=== Android Device Manager ===

Version: 16.6.0.95
Hash: 45d17b5
Branch: remotes/origin/d16-6
Build date: 2020-04-30 04:01:42 UTC

=== Build Information ===

Release ID: 806004520
Git revision: 9c92c7baceef7771f8dcf5c86e1e1a66fdc26182
Build date: 2020-05-18 10:05:00-04
Build branch: release-8.6
Xamarin extensions: 9c92c7baceef7771f8dcf5c86e1e1a66fdc26182

=== Operating System ===

Mac OS X 10.15.4
Darwin 19.4.0 Darwin Kernel Version 19.4.0
    Wed Mar  4 22:28:40 PST 2020
    root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64

[sjorsmiltenburg]

I also encounter this problem in visual studio for windows after updating to the latest xamarin.forms.
This is quite a big problem because VS becomes almost inresponsive.

The situation in which it occurs on my end:

• I am running my XF app on my physical android phone
• I have a collectionview and a flexlayout with around 40 images.
• the heightrequest and widthrequest is bound to the viewmodel
• when I rotate the screen I manually recalculate the width/height and all images update their size.
  every rotate of my device, the log get's spammed and I can't touch my vs for about 20 seconds.

a downgrade to XF 4.6.0.772 did not fix my problem
a downgrade to XF 4.5.0.725 did not fix my problem
hmm.. a downgrade to XF 4.5.0.356 (where I came from) also did not fix my problem.
Maybe the cause is somewere else.

[dgenezini]

Happening to me too, VS does not respond until all messages are logged.

I am using VS 16.6.0, Xamarin Forms 4.6.0.772, and Android on Genymotion.

[nimbuster]

I downgraded VS to 16.5.4 and the errors go away. Seems like a VS 16.6 conflict with Xamarin.Forms.

[SoftArea-srl]

I downgraded VS to 16.5.4 and the errors go away. Seems like a VS 16.6 conflict with Xamarin.Forms.

Hello @nimbuster , could you please describe how you have been able to revert to VS 16.5.4? Whenever I try the installer takes me to the VS 16.6.

[bcaceiro]

I'm also noticing this issue. Huge dump in debug. It started happening with VS upgrade to 16.6

[nimbuster]

@SoftArea-srl Get the installer from here. If you're using the Community license, I just use the Professional installer. When you run it, close the Components dialog then click the 'Available' tab and select Community. You must first uninstall the current version of VS, so backup your config and extensions.

[agat366]

Yeah, same to me on 16.6. Seems this VS upgrade is kind of a Wooden Horse, lol!

[brendanzagaeski]

Cross-referencing note for the Xamarin team

Corresponding Developer Community item: https://developercommunity.visualstudio.com/content/problem/1021788/javainterop-assembly-not-found-for-xamarin-android.html

[apeivandi]

Hi
Why is this issue was closed? What's the solution? I still see all the outputs and it's really annoying as rest of debug logs are impossible to be seen or used as long as all the extra messages are displayed.

Best

[brendanzagaeski]

@apeivandi, thanks for the question.

Whoops. Accidentally submitted that comment before I was done writing it. I'll have another comment ready in a second.

[brendanzagaeski]

@apeivandi, thanks for the question.

By default, the Closed state of an issue on GitHub indicates that a fix for the issue has been merged to the development branch and will be published in a future Xamarin.Android version. That's because GitHub's automatic issue closing and linked pull request features promote a workflow where issues are Closed when the fix is committed to the repository. As a result, teams, including the Xamarin.Android team, typically use the Open vs. Closed states to help monitor which items on an active milestone do not yet have a fix committed.

Due to that workflow that the GitHub automation promotes, this xamarin-android repository instead uses "In Preview: " and "Published: " milestones combined with comments to indicate when fixes are _published_ (as opposed to _committed_). Here's an example of how that looks: https://github.com/xamarin/xamarin-android/issues/4409#issuecomment-615018927.

I will be updating this item with a similar comment as soon as the fix that is currently _committed_ to the development branch is _published_ in a publicly available version of Xamarin.Android.

At the moment there isn't a known workaround for this issue, but the team is working to publish the fix as soon as possible.

[brendanzagaeski]

Release status update

A new Release version of Xamarin.Android has now been published on Windows that includes the fix for this item.

The fix is not yet available on macOS. I will update this item again when a Release version with the fix is available on macOS. If there are no unexpected complications, it will be available later this week.

Fix included in Xamarin.Android SDK version 10.3.1.4.

Fix included on Windows in Visual Studio 2019 version 16.6.1. To get the new version that includes the fix, check for the latest updates or install the most recent release from https://visualstudio.microsoft.com/downloads/.

Fix not yet available on macOS.

Fix not yet available in the Preview version. I will update this item again when a Preview version is available that includes the fix.

[brendanzagaeski]

Release status update

A new Release version of Xamarin.Android has now been published on macOS that includes the fix for this item to match yesterday's new version on Windows. Thanks again for submitting this issue that has helped improve the product!

Fix included in Xamarin.Android SDK version 10.3.1.4.

Fix included on macOS in Visual Studio 2019 for Mac version 8.6.2. To get the new version that includes the fix, check for the latest updates on the Stable updater channel.

(Fix also included on Windows in Visual Studio 2019 version 16.6.1. To get the new version that includes the fix, check for the latest updates or install the most recent release from https://visualstudio.microsoft.com/downloads/.)

Fix not yet available in the Preview versions. I will update this item again when Preview versions are available that include the fix.

[kuramochia]

Release build using Xamarin Android SDK v10.3.1.4, I will see a large number of logs below.

monodroid-assembly typemap: module matching MVID [49B5F91A-2F8E-439E-AD20-F837EB41AFF4] not found.

The following command was executed.

> adb shell setprop mono.debug.log all

And when you view the log, it became the following log.

monodroid-assembly typemap: module matching MVID [49B5F91A-2F8E-439E-AD20-F837EB41AFF4] not found.
monodroid typemap: failed to map managed type to Java type: System.Byte, mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cecToken=7cec85d7bea7798e (Module: ID: Module: 49b5f91a-2f8e-439e-ad20-f837eb41aff4; Type token: 33554569)

I think its same issue. I want you to fix this, too.

[brendanzagaeski]

@kuramochia, thanks for the idea. Right now, that would be considered the intended corrrect logging behavior. When mono.debug.log is set to the all verbosity level, additional diagnostic information is logged about the typemap lookups. To discuss potential changes to this behavior and your desired usage scenario, when you get a chance, please submit a new issue about it so the team can take a look and discuss. Thanks!

[kuramochia]

@brendanzagaeski Thanks!, I submitted new issue (#4791).

[roninstar]

I have version Visual Studio 16.6.2 and since this upgrade I get spammed with these errors from my Xamarin Android Release build which I have not seen these errors before. It looks like I have Xamarin 16.6.000 though.

 W/monodroid-assembly(5608): typemap: module matching MVID [96E78666-3B05-47DD-A3A2-B357695888AB] not found.

Microsoft Visual Studio Professional 2019
Version 16.6.2
VisualStudio.16.Release/16.6.2+30204.135
Microsoft .NET Framework
Version 4.8.03761

Installed Version: Professional

Visual C++ 2019 00435-60000-00000-AA417
Microsoft Visual C++ 2019

ADL Tools Service Provider 1.0
This package contains services used by Data Lake tools

ASA Service Provider 1.0

ASP.NET and Web Tools 2019 16.6.948.25768
ASP.NET and Web Tools 2019

ASP.NET Core Razor Language Services 16.1.0.2020603+b3ac44798c16fff5b95dbcfe62dea84aa9a1bd72
Provides languages services for ASP.NET Core Razor.

ASP.NET Web Frameworks and Tools 2019 16.6.948.25768
For additional information, visit https://www.asp.net/

Azure App Service Tools v3.0.0 16.6.948.25768
Azure App Service Tools v3.0.0

Azure Data Lake Node 1.0
This package contains the Data Lake integration nodes for Server Explorer.

Azure Data Lake Tools for Visual Studio 2.4.6000.0
Microsoft Azure Data Lake Tools for Visual Studio

Azure Functions and Web Jobs Tools 16.6.948.25768
Azure Functions and Web Jobs Tools

Azure Stream Analytics Tools for Visual Studio 2.4.6000.0
Microsoft Azure Stream Analytics Tools for Visual Studio

C# Tools 3.6.0-4.20251.5+910223b64f108fcf039012e0849befb46ace6e66
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Common Azure Tools 1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

Extensibility Message Bus 1.2.0 (d16-2@8b56e20)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.

Fabric.DiagnosticEvents 1.0
Fabric Diagnostic Events

IntelliCode Extension 1.0
IntelliCode Visual Studio Extension Detailed Info

Microsoft Azure HDInsight Azure Node 2.4.6000.0
HDInsight Node under Azure Node

Microsoft Azure Hive Query Language Service 2.4.6000.0
Language service for Hive query

Microsoft Azure Service Fabric Tools for Visual Studio 16.0
Microsoft Azure Service Fabric Tools for Visual Studio

Microsoft Azure Stream Analytics Language Service 2.4.6000.0
Language service for Azure Stream Analytics

Microsoft Azure Stream Analytics Node 1.0
Azure Stream Analytics Node under Azure Node

Microsoft Azure Tools 2.9
Microsoft Azure Tools for Microsoft Visual Studio 2019 - v2.9.30212.1

Microsoft Continuous Delivery Tools for Visual Studio 0.4
Simplifying the configuration of Azure DevOps pipelines from within the Visual Studio IDE.

Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft Library Manager 2.1.50+g25aae5a24a.R
Install client-side libraries easily to any web project

Microsoft MI-Based Debugger 1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual C++ Wizards 1.0
Microsoft Visual C++ Wizards

Microsoft Visual Studio Tools for Containers 1.1
Develop, run, validate your ASP.NET Core applications in the target environment. F5 your application directly into a container with debugging, or CTRL + F5 to edit & refresh your app without having to rebuild the container.

Microsoft Visual Studio VC Package 1.0
Microsoft Visual Studio VC Package

Mono Debugging for Visual Studio 16.6.17 (9692114)
Support for debugging Mono processes with Visual Studio.

NuGet Package Manager 5.6.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/

ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

SQL Server Data Tools 16.0.62006.03190
Microsoft SQL Server Data Tools

ToolWindowHostedEditor 1.0
Hosting json editor into a tool window

TypeScript Tools 16.0.20417.2002
TypeScript Tools for Microsoft Visual Studio

Visual Basic Tools 3.6.0-4.20251.5+910223b64f108fcf039012e0849befb46ace6e66
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual F# Tools 10.9.1.0 for F# 4.7 16.6.0-beta.20217.4+1c969cac25e2d38d71872efe6c8226029e42bb59
Microsoft Visual F# Tools 10.9.1.0 for F# 4.7

Visual Studio Code Debug Adapter Host Package 1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

Visual Studio Container Tools Extensions (Preview) 1.0
View, manage, and diagnose containers within Visual Studio.

Visual Studio Tools for Containers 1.0
Visual Studio Tools for Containers

Visual Studio Tools for Kubernetes 1.0
Visual Studio Tools for Kubernetes

VisualStudio.DeviceLog 1.0
Information about my package

VisualStudio.Foo 1.0
Information about my package

VisualStudio.Mac 1.0
Mac Extension for Visual Studio

Xamarin 16.6.000.1061 (d16-6@8e68aa8)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin Designer 16.6.0.318 (remotes/origin/d16-6@66afc5421)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.

Xamarin Templates 16.6.40 (1f1466f)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.

Xamarin.Android SDK 10.3.1.4 (d16-6/3a10de9)
Xamarin.Android Reference Assemblies and MSBuild support.
Mono: 165f4b0
Java.Interop: xamarin/java.interop/d16-6@2cab35c
ProGuard: xamarin/proguard/master@905836d
SQLite: xamarin/sqlite/3.31.1@49232bc
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-6@bfb66f3

Xamarin.iOS and Xamarin.Mac SDK 13.18.2.1 (29c4ea7)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

[brendanzagaeski]

@roninstar, thanks for the question. I've reopened kuramochia's new issue https://github.com/xamarin/xamarin-android/issues/4791 to track adjustments for those other typemap messages. You can continue to follow that issue for the latest info.

[brendanzagaeski]

_Release status update_

The fix for this issue that was previously published in the Release versions has now been published in the latest Preview versions as well.

Fix included in Xamarin.Android SDK version 10.4.0.0.

Fix included on Windows in Visual Studio 2019 version 16.7 Preview 3. To try the Preview version that includes the fix, check for the latest updates in Visual Studio Preview.

Fix included on macOS in Visual Studio 2019 for Mac version 8.7 Preview 3. To try the Preview version that includes the fix, check for the latest updates on the Preview updater channel.