Bug 58825

Summary: Build Fails with "Unexpected Error - please file a bug report" in file Xamarin.iOS.Common.targets line 747
Product: iOS Reporter: Robert Vaselaar <bob.vaselaar>
Component: MSBuildAssignee: Bugzilla <bugzilla>
Severity: normal CC: alex.soto, mono-bugs+monotouch
Priority: ---    
Version: unspecified   
Target Milestone: Untriaged   
Hardware: PC   
OS: Windows   
Tags: Is this bug a regression?: ---
Last known good build:
Attachments: line 747 throws the exception above when building to a device

Description Robert Vaselaar 2017-08-16 21:37:03 UTC
Created attachment 24255 [details]
line 747 throws the exception above when building to a device

this happens when trying to build to a physical device, whether in debug, release, or ad-hoc. It also occurs whether or not I have the linker turned on in the iOS build settings.

Here's the build output:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(747,3): error : Unexpected error - Please file a bug report at http://bugzilla.xamarin.com
1>  System.NullReferenceException: Object reference not set to an instance of an object
1>    at MonoTouch.Tuner.Linker.Process (MonoTouch.Tuner.LinkerOptions options, MonoTouch.Tuner.MonoTouchLinkContext& context, System.Collections.Generic.List`1[Mono.Cecil.AssemblyDefinition]& assemblies) [0x00145] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/Tuning.cs:94 
1>    at Xamarin.Bundler.Target.LinkAssemblies (System.Collections.Generic.List`1[Mono.Cecil.AssemblyDefinition]& assemblies, System.String output_dir, System.Collections.Generic.IEnumerable`1[T] sharedCodeTargets) [0x0029a] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/Target.cs:491 
1>    at Xamarin.Bundler.Target.ManagedLink () [0x005c5] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/Target.cs:614 
1>    at Xamarin.Bundler.Target.ProcessAssemblies () [0x000bb] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/Target.cs:800 
1>    at Xamarin.Bundler.Application.ProcessAssemblies () [0x0002f] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/Application.cs:1396 
1>    at Xamarin.Bundler.Application.BuildManaged () [0x00001] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/Application.cs:827 
1>    at Xamarin.Bundler.Application+<>c.<BuildAll>b__134_1 (Xamarin.Bundler.Application v) [0x00000] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/Application.cs:775 
1>    at System.Collections.Generic.List`1[T].ForEach (System.Action`1[T] action) [0x00024] in <c9f8153c41de4f8cbafd0e32f9bf6b28>:0 
1>    at Xamarin.Bundler.Application.BuildAll () [0x00050] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/Application.cs:775 
1>    at Xamarin.Bundler.Driver.Main2 (System.String[] args) [0x00481] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/mtouch.cs:1420 
1>    at Xamarin.Bundler.Driver.Main (System.String[] args) [0x0000f] in /Users/builder/data/lanes/4991/4a279c9a/source/xamarin-macios/tools/mtouch/mtouch.cs:945 
1>Build FAILED.
1>Time Elapsed 00:00:13.68

Xamarin.iOS.Common.targets is attached
Comment 1 Alex Soto [MSFT] 2017-08-16 22:04:00 UTC
Thanks for the report.  There is a workaround download available in Bug 58789, Comment 4 that will give the intended error.

After you complete the steps in that comment to install the workaround `mtouch` version on your connected Mac, you should get a more useful linker error message that will better indicate how to resolve the issue.  As mentioned on Bug 58789, if you suspect that the more precise linker error indicates an issue that will need to be resolved the Xamarin.iOS source code (rather than by adjusting your project), please do reopen this bug with your new build logs (that include the new linker error message).  Thanks in advance!

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

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