Bug 22526 - Warning concerning Mono.Android.Export.dll during Release build
Summary: Warning concerning Mono.Android.Export.dll during Release build
Status: RESOLVED NORESPONSE
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.16.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2014-08-30 09:55 UTC by Christophe Oosterlynck
Modified: 2017-06-27 19:31 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:
RESOLVED NORESPONSE

Description Christophe Oosterlynck 2014-08-30 09:55:51 UTC
I'm getting a warning when compiling in Release but not in Debug.

Target _GenerateJavaStubs:
		  ResolvedAssemblies:
		    obj/Release/android/assets/Axa.Mobile.Droid.dll
                    ...
		    obj/Release/android/assets/System.ServiceModel.dll
		  ResolvedUserAssemblies:
		    obj/Release/android/assets/Axa.Mobile.Droid.dll
		    ...
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets:  warning : Failed to read '/Users/christophe/src/axa-mobile/Axa.Mobile.Droid/Axa.Mobile.Droid/obj/Release/android/assets/Mono.Android.Export.dll' with debugging symbols. Retrying to load it without it. Error details are logged below.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets:  warning : Mono.CompilerServices.SymbolWriter.MonoSymbolFileException: Cannot read symbol file `/Users/christophe/src/axa-mobile/Axa.Mobile.Droid/Axa.Mobile.Droid/obj/Release/android/assets/Mono.Android.Export.dll.mdb'
  at Mono.CompilerServices.SymbolWriter.MonoSymbolFile..ctor (System.String filename) [0x00000] in <filename unknown>:0 
  at Mono.CompilerServices.SymbolWriter.MonoSymbolFile..ctor (System.String filename, Mono.Cecil.ModuleDefinition module) [0x00000] in <filename unknown>:0 
  at Mono.CompilerServices.SymbolWriter.MonoSymbolFile.ReadSymbolFile (Mono.Cecil.ModuleDefinition module, System.String filename) [0x00000] in <filename unknown>:0 
  at Mono.Cecil.Mdb.MdbReaderProvider.GetSymbolReader (Mono.Cecil.ModuleDefinition module, System.String fileName) [0x00000] in <filename unknown>:0 
  at Mono.Cecil.ModuleReader.ReadSymbols (Mono.Cecil.ModuleDefinition module, Mono.Cecil.ReaderParameters parameters) [0x00000] in <filename unknown>:0 
  at Mono.Cecil.ModuleReader.CreateModuleFrom (Mono.Cecil.PE.Image image, Mono.Cecil.ReaderParameters parameters) [0x00000] in <filename unknown>:0 
  at Mono.Cecil.ModuleDefinition.ReadModule (System.IO.Stream stream, Mono.Cecil.ReaderParameters parameters) [0x00000] in <filename unknown>:0 
  at Mono.Cecil.ModuleDefinition.ReadModule (System.String fileName, Mono.Cecil.ReaderParameters parameters) [0x00000] in <filename unknown>:0 
  at Mono.Cecil.AssemblyDefinition.ReadAssembly (System.String fileName, Mono.Cecil.ReaderParameters parameters) [0x00000] in <filename unknown>:0 
  at Xamarin.Android.Tuner.DirectoryAssemblyResolver.ReadAssembly (System.String file) [0x00000] in <filename unknown>:0

The Mono.Android.Export.dll.mdb file is available in that folder, so that is not the problem. However, both Mono.Android.Export.dll and Mono.Android.Export.dll.mdb have the same md5 checksum.
Comment 1 Saurabh 2014-09-01 10:28:28 UTC
I have checked this Issue but I am not able to reproduce this Issue. I have created Android template application and then run this application on both physical device and Emulator in Release mode but I am not seeing any warning. 

@Christophe, Could you please provide me test project for which you are getting error also please let me know which version of builds you are installed on your machine?

I have checked it on following builds:

=== Xamarin Studio ===

Version 5.3 (build 439)
Installation UUID: 2591d519-875d-4afe-a3d9-5fcf391bbd2d
Runtime:
	Mono 3.8.0 ((no/356dbc5)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 308000010

=== Apple Developer Tools ===

Xcode 4.6.3 (2068)
Build 4H1503

=== Xamarin.Mac ===

Version: 1.11.0.1 (Trial Edition)

=== Xamarin.iOS ===

Version: 7.4.0.108 (Trial Edition)
Hash: 77efa3f
Branch: 
Build date: 2014-08-26 07:59:55-0400

=== Xamarin.Android ===

Version: 4.16.0 (Trial Edition)
Android SDK: /Users/nischal/Desktop/android-sdk-macosx
	Supported Android versions:
		2.1    (API level 7)
		2.2    (API level 8)
		2.3    (API level 10)
		3.1    (API level 12)
		3.2    (API level 13)
		4.0    (API level 14)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		4.5    (API level 21)
Java SDK: /usr
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10-428-11M3811)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01-428, mixed mode)

=== Build Information ===

Release ID: 503000439
Git revision: cc6857ea9e1f0a9b73ae91ba2651bbd65bb025d2
Build date: 2014-08-28 04:44:10-04
Xamarin addins: 64abcc2ff237e90e590aee75625f60badbbdb2c1

=== Operating System ===

Mac OS X 10.7.4
Darwin nischals-Mac-mini.local 11.4.0 Darwin Kernel Version 11.4.0
    Mon Apr  9 19:32:15 PDT 2012
    root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64
Comment 2 Chris Hardy [MSFT] 2017-06-27 19:31:24 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!