Bug 37685 - error MT0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com
Summary: error MT0000: Unexpected error - Please file a bug report at http://bugzilla....
Status: RESOLVED DUPLICATE of bug 36505
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-01-14 10:07 UTC by yann.gefflot
Modified: 2016-04-12 18:10 UTC (History)
3 users (show)

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:

Description yann.gefflot 2016-01-14 10:07:38 UTC

I have a xamarin.ios project that include an own library ".a" itself include the "FastPdfKit.framework".

When I compile my project, I've got one error:

Xamarin.iOS 9.4.0 Business Edition using framework: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.2.sdk
MTOUCH: error MT0000: Unexpected error - Please file a bug report at http://bugzilla.xamarin.com
		System.IO.EndOfStreamException: Unable to read beyond the end of the stream.
		  at System.IO.BinaryReader.FillBuffer (Int32 numBytes) <0x1131d3bd0 + 0x0015e> in <filename unknown>:0 
		  at System.IO.BinaryReader.ReadUInt32 () <0x1131f2ca0 + 0x00015> in <filename unknown>:0 
		  at Xamarin.MachOFile.Read (System.IO.BinaryReader reader) <0x11b78e8d0 + 0x00113> in <filename unknown>:0 
		  at Xamarin.FatEntry.ReadEntry (System.IO.BinaryReader reader) <0x11b78f8d0 + 0x000a3> in <filename unknown>:0 
		  at Xamarin.FatFile.Read (System.IO.BinaryReader reader) <0x11b78f470 + 0x001a4> in <filename unknown>:0 
		  at Xamarin.MachO.ReadFile (System.IO.BinaryReader reader, System.String filename) <0x11b78e700 + 0x000f6> in <filename unknown>:0 
		  at Xamarin.MachO.ReadFile (System.String filename) <0x11b78e5b0 + 0x000bf> in <filename unknown>:0 
		  at Xamarin.MachO.SelectArchitectures (System.String filename, ICollection`1 abis) <0x11b7924d0 + 0x0017e> in <filename unknown>:0 
		  at MonoTouch.Application.BuildFinalExecutable () <0x11b790430 + 0x00610> in <filename unknown>:0 
		  at MonoTouch.Application.Build () <0x1131ddbd0 + 0x00121> in <filename unknown>:0 
		  at MTouch.Main2 (System.String[] args) <0x110fc52d0 + 0x074c7> in <filename unknown>:0 
		  at MTouch.Main (System.String[] args) <0x110f86e60 + 0x00069> in <filename unknown>:0 
	Task "MTouch" execution -- FAILED
Can you help me??

Comment 1 Rolf Bjarne Kvinge [MSFT] 2016-01-14 10:29:18 UTC
This is probably a duplicate of a bug we've already fixed (bug #36505), but if you share your project with us so that I can reproduce it myself I can confirm (and probably be able to come up with a workaround).
Comment 2 yann.gefflot 2016-01-14 10:37:32 UTC
how to check bug #36505 ?
Comment 3 yann.gefflot 2016-01-14 10:46:56 UTC
My xcode version: 7.2
My Xamarin.ios version: 5.10.1
Comment 4 Rolf Bjarne Kvinge [MSFT] 2016-01-14 10:55:00 UTC
Bug #36505 is private, so you can't see it (I can though, so if you share your project with us I can confirm if it's really the same bug or not).
Comment 5 Sebastien Pouliot 2016-04-12 16:00:16 UTC
We have no other reports for that exception that were not related to #36505. Please try the latest XI 9.8.x beta to see if this fixed the issue.

*** This bug has been marked as a duplicate of bug 36505 ***