error MT0099 : Internal error : Not all assemblies for Xamarin.Sdk have link tasks. #4235

kdubau · 2018-06-12T20:11:58Z

Description

Not all apps are affected, I'm not sure what is special about this one in particular. Unfortunately we did not catch this sooner because of a mixup with the SeeingAI teams app repo (it moved and we didn't know so we were still testing their old source). Not sure if it's relevant but it seems a similar issue has cropped up (but resolved) in the community: #4101

Steps to Reproduce

Install XI 11.10.1.177 or later (15.7 RTW)
Clone the SeeingAI app (internal)
Build it in Release config

Expected Behavior

Successful build

Actual Behavior

2018-06-04T20:16:28.9530910Z (_CompileToNative target) -> 
2018-06-04T20:16:28.9553430Z   error MT0099 : Internal error : Not all assemblies for Xamarin.Sdk have link tasks. Please file a bug report with a test case (http://bugzilla.xamarin.com). [/Users/vsts/agent/2.134.2/work/1/s/iOS/App/SeeingAI.iOS.csproj]
2018-06-04T20:16:28.9562760Z

Environment

Xcode | 9.4.0 | Xcode_9.4.xip
Xamarin.iOS | 11.10.1.177 | xamarin.ios-11.10.1.177.pkg
Xamarin.Mac | 4.4.1.176 | xamarin.mac-4.4.1.176.pkg
Visual Studio for Mac | 7.5.0.1254 | VisualStudioForMac-7.5.0.1254.dmg
Mono | 5.10.1.47 | MonoFramework-MDK-5.10.1.47.macos10.xamarin.universal.pkg

Build Logs

Failed 15.7 RTW (11.10.1.177): http://build.devdiv.io/1745621

This is also reproducible with 15.7 SR3 and Master. (Master -> build.devdiv.io/1764931 - see Release config).

Successful 15.6 (11.9.1.24) : http://build.devdiv.io/1746181 - please ignore the failed Windows build (it's failed due to this bug, only the Mac build in this job is truly using 15.6)

Example Project (If Possible)

Contact me on Slack and we can work out getting you access to SeeingAI app.

The text was updated successfully, but these errors were encountered:

spouliot · 2018-06-12T20:13:41Z

@rolfbjarne can you have a look ? thanks!

kdubau · 2018-06-12T20:17:48Z

I'll update with 15.8 results as soon as I have them (in progress).

kdubau · 2018-06-13T12:55:34Z

This issue also exists in 15.8 (11.14.0.4) http://build.devdiv.io/1768483 (see Release config build).

rolfbjarne · 2018-06-13T16:56:56Z

I can reproduce.

rolfbjarne · 2018-06-14T12:52:37Z

This is related to issue #4237.

This is the sequence of events more or less:

When initially walking the root assemblies, loading every referenced assembly, mtouch fails to find Newtonsoft.Json.
At this point mtouch decides how to group assemblies into frameworks. mtouch doesn't think the extension needs Microsoft.CSharp.dll, since it's only referenced by Newtonsoft.Json.dll, which it couldn't find, so the Xamarin.Sdk.framework doesn't include Microsoft.CSharp.dll.
At a later point, mtouch successfully finds Newtonsoft.Json.dll
The linker runs, and when determining which assemblies goes into the app and app extension, we walk the assembly references again. Now we do find that the extension references Microsoft.CSharp.dll (through Newtonsoft.Json.dll, which has been loaded successfully).
Close to the very end, this conflict triggers the MT0099 internal error, because some code thinks the extension needs Microsoft.CSharp.dll, and some other code doesn't.

It seems to me that the problem would disappear if mtouch would find Newtonsoft.Json.dll from the very beginning, but I'm keeping this open for verification once issue #4237 is solved.

This would have helped track down dotnet#4235.

…ixes dotnet#4235 and dotnet#4237. In Xamarin.iOS.Common.targets, just before the _CompileToNative target, we modify the mtouch references to ensure that we get the lib assemblies for nugets, and not the ref references: https://github.com/xamarin/xamarin-macios/blob/9e31d07ecc08a64372dd562e843c3d8950d24985/msbuild/Xamarin.iOS.Tasks.Core/Xamarin.iOS.Common.targets#L784-L791 This logic removes nuget references, and then re-adds any copy-local dll references. This works fine in executable projects, but not in library projects (aka extensions), because nugets aren't copied for library projects: https://github.com/NuGet/NuGet.BuildTasks/blob/cf4b0a12cf1f75e0654f28c2a9020251c41d126a/src/Microsoft.NuGet.Build.Tasks/Microsoft.NuGet.targets#L86 So we need to set the CopyNuGetImplementations variable to 'true' for our library projects. Fixes dotnet#4235. Fixes dotnet#4237.

* [mtouch] Show warnings when we can't find referenced assemblies. This would have helped track down #4235. * Improve MT0137 warning to indicate the type of the attribute causing the warning.

…ixes #4235 and #4237. (#4512) * [msbuild] Set 'CopyNuGetImplementations' to true for app extensions. Fixes #4235 and #4237. In Xamarin.iOS.Common.targets, just before the _CompileToNative target, we modify the mtouch references to ensure that we get the lib assemblies for nugets, and not the ref references: https://github.com/xamarin/xamarin-macios/blob/9e31d07ecc08a64372dd562e843c3d8950d24985/msbuild/Xamarin.iOS.Tasks.Core/Xamarin.iOS.Common.targets#L784-L791 This logic removes nuget references, and then re-adds any copy-local dll references. This works fine in executable projects, but not in library projects (aka extensions), because nugets aren't copied for library projects: https://github.com/NuGet/NuGet.BuildTasks/blob/cf4b0a12cf1f75e0654f28c2a9020251c41d126a/src/Microsoft.NuGet.Build.Tasks/Microsoft.NuGet.targets#L86 So we need to set the CopyNuGetImplementations variable to 'true' for our library projects. Fixes #4235. Fixes #4237. * [tests] Redirect MSBuildExtensionsPath to MSBuildExtensionsPathFallbackPathsOverride when running msbuild for package reference tests. This fixes a problem where nuget restore would fail for projects with PackageReferences, because a variable would be empty and msbould would try to write to /: nuget restore ../MyAppWithPackageReference/MyAppWithPackageReference.csproj MSBuild auto-detection: using msbuild version '15.0' from '/Library/Frameworks/Mono.framework/Versions/Current/lib/mono/msbuild/15.0/bin/'. Restoring packages for /Users/builder/jenkins/workspace/xamarin-macios-pr-builder/msbuild/tests/MyAppWithPackageReference/MyAppWithPackageReference.csproj... Committing restore... Generating MSBuild file /MyAppWithPackageReference.csproj.nuget.g.props. Path / is a directory This will become unnecessary when PR #4111 is merged. * Add Xamarin.Mac test showing that fix is not needed (?!?) * Add AppExtension test with packagereference * Make extension actually have json code generated * Fix ProjectTypeGuids of checked in extension projects, as they were not openable in VSfM * XM extension test now correctly fails * Now that we have a failing test, fix XM same as rest of platforms * Disable XM tests due to msbuild redirect sadness * Disable iOS tests as well due to #4110 * Disable iOS tests by using the Ignore attribute. Disable tests by using the Ignore attribute, because just commenting out the TestCase attributes makes the test fail: 1) NotRunnable : Xamarin.iOS.Tasks.ProjectReferenceTests.BasicTest No suitable constructor was found

…ixes dotnet#4235 and dotnet#4237. (dotnet#4512) * [msbuild] Set 'CopyNuGetImplementations' to true for app extensions. Fixes dotnet#4235 and dotnet#4237. In Xamarin.iOS.Common.targets, just before the _CompileToNative target, we modify the mtouch references to ensure that we get the lib assemblies for nugets, and not the ref references: https://github.com/xamarin/xamarin-macios/blob/9e31d07ecc08a64372dd562e843c3d8950d24985/msbuild/Xamarin.iOS.Tasks.Core/Xamarin.iOS.Common.targets#L784-L791 This logic removes nuget references, and then re-adds any copy-local dll references. This works fine in executable projects, but not in library projects (aka extensions), because nugets aren't copied for library projects: https://github.com/NuGet/NuGet.BuildTasks/blob/cf4b0a12cf1f75e0654f28c2a9020251c41d126a/src/Microsoft.NuGet.Build.Tasks/Microsoft.NuGet.targets#L86 So we need to set the CopyNuGetImplementations variable to 'true' for our library projects. Fixes dotnet#4235. Fixes dotnet#4237. * [tests] Redirect MSBuildExtensionsPath to MSBuildExtensionsPathFallbackPathsOverride when running msbuild for package reference tests. This fixes a problem where nuget restore would fail for projects with PackageReferences, because a variable would be empty and msbould would try to write to /: nuget restore ../MyAppWithPackageReference/MyAppWithPackageReference.csproj MSBuild auto-detection: using msbuild version '15.0' from '/Library/Frameworks/Mono.framework/Versions/Current/lib/mono/msbuild/15.0/bin/'. Restoring packages for /Users/builder/jenkins/workspace/xamarin-macios-pr-builder/msbuild/tests/MyAppWithPackageReference/MyAppWithPackageReference.csproj... Committing restore... Generating MSBuild file /MyAppWithPackageReference.csproj.nuget.g.props. Path / is a directory This will become unnecessary when PR dotnet#4111 is merged. * Add Xamarin.Mac test showing that fix is not needed (?!?) * Add AppExtension test with packagereference * Make extension actually have json code generated * Fix ProjectTypeGuids of checked in extension projects, as they were not openable in VSfM * XM extension test now correctly fails * Now that we have a failing test, fix XM same as rest of platforms * Disable XM tests due to msbuild redirect sadness * Disable iOS tests as well due to dotnet#4110 * Disable iOS tests by using the Ignore attribute. Disable tests by using the Ignore attribute, because just commenting out the TestCase attributes makes the test fail: 1) NotRunnable : Xamarin.iOS.Tasks.ProjectReferenceTests.BasicTest No suitable constructor was found

…ixes #4235 and #4237. (#4512) (#4648) * [msbuild] Set 'CopyNuGetImplementations' to true for app extensions. Fixes #4235 and #4237. In Xamarin.iOS.Common.targets, just before the _CompileToNative target, we modify the mtouch references to ensure that we get the lib assemblies for nugets, and not the ref references: https://github.com/xamarin/xamarin-macios/blob/9e31d07ecc08a64372dd562e843c3d8950d24985/msbuild/Xamarin.iOS.Tasks.Core/Xamarin.iOS.Common.targets#L784-L791 This logic removes nuget references, and then re-adds any copy-local dll references. This works fine in executable projects, but not in library projects (aka extensions), because nugets aren't copied for library projects: https://github.com/NuGet/NuGet.BuildTasks/blob/cf4b0a12cf1f75e0654f28c2a9020251c41d126a/src/Microsoft.NuGet.Build.Tasks/Microsoft.NuGet.targets#L86 So we need to set the CopyNuGetImplementations variable to 'true' for our library projects. Fixes #4235. Fixes #4237. * [tests] Redirect MSBuildExtensionsPath to MSBuildExtensionsPathFallbackPathsOverride when running msbuild for package reference tests. This fixes a problem where nuget restore would fail for projects with PackageReferences, because a variable would be empty and msbould would try to write to /: nuget restore ../MyAppWithPackageReference/MyAppWithPackageReference.csproj MSBuild auto-detection: using msbuild version '15.0' from '/Library/Frameworks/Mono.framework/Versions/Current/lib/mono/msbuild/15.0/bin/'. Restoring packages for /Users/builder/jenkins/workspace/xamarin-macios-pr-builder/msbuild/tests/MyAppWithPackageReference/MyAppWithPackageReference.csproj... Committing restore... Generating MSBuild file /MyAppWithPackageReference.csproj.nuget.g.props. Path / is a directory This will become unnecessary when PR #4111 is merged. * Add Xamarin.Mac test showing that fix is not needed (?!?) * Add AppExtension test with packagereference * Make extension actually have json code generated * Fix ProjectTypeGuids of checked in extension projects, as they were not openable in VSfM * XM extension test now correctly fails * Now that we have a failing test, fix XM same as rest of platforms * Disable XM tests due to msbuild redirect sadness * Disable iOS tests as well due to #4110 * Disable iOS tests by using the Ignore attribute. Disable tests by using the Ignore attribute, because just commenting out the TestCase attributes makes the test fail: 1) NotRunnable : Xamarin.iOS.Tasks.ProjectReferenceTests.BasicTest No suitable constructor was found

…ixes dotnet#4235 and dotnet#4237. (dotnet#4512) (dotnet#4648) * [msbuild] Set 'CopyNuGetImplementations' to true for app extensions. Fixes dotnet#4235 and dotnet#4237. In Xamarin.iOS.Common.targets, just before the _CompileToNative target, we modify the mtouch references to ensure that we get the lib assemblies for nugets, and not the ref references: https://github.com/xamarin/xamarin-macios/blob/9e31d07ecc08a64372dd562e843c3d8950d24985/msbuild/Xamarin.iOS.Tasks.Core/Xamarin.iOS.Common.targets#L784-L791 This logic removes nuget references, and then re-adds any copy-local dll references. This works fine in executable projects, but not in library projects (aka extensions), because nugets aren't copied for library projects: https://github.com/NuGet/NuGet.BuildTasks/blob/cf4b0a12cf1f75e0654f28c2a9020251c41d126a/src/Microsoft.NuGet.Build.Tasks/Microsoft.NuGet.targets#L86 So we need to set the CopyNuGetImplementations variable to 'true' for our library projects. Fixes dotnet#4235. Fixes dotnet#4237. * [tests] Redirect MSBuildExtensionsPath to MSBuildExtensionsPathFallbackPathsOverride when running msbuild for package reference tests. This fixes a problem where nuget restore would fail for projects with PackageReferences, because a variable would be empty and msbould would try to write to /: nuget restore ../MyAppWithPackageReference/MyAppWithPackageReference.csproj MSBuild auto-detection: using msbuild version '15.0' from '/Library/Frameworks/Mono.framework/Versions/Current/lib/mono/msbuild/15.0/bin/'. Restoring packages for /Users/builder/jenkins/workspace/xamarin-macios-pr-builder/msbuild/tests/MyAppWithPackageReference/MyAppWithPackageReference.csproj... Committing restore... Generating MSBuild file /MyAppWithPackageReference.csproj.nuget.g.props. Path / is a directory This will become unnecessary when PR dotnet#4111 is merged. * Add Xamarin.Mac test showing that fix is not needed (?!?) * Add AppExtension test with packagereference * Make extension actually have json code generated * Fix ProjectTypeGuids of checked in extension projects, as they were not openable in VSfM * XM extension test now correctly fails * Now that we have a failing test, fix XM same as rest of platforms * Disable XM tests due to msbuild redirect sadness * Disable iOS tests as well due to dotnet#4110 * Disable iOS tests by using the Ignore attribute. Disable tests by using the Ignore attribute, because just commenting out the TestCase attributes makes the test fail: 1) NotRunnable : Xamarin.iOS.Tasks.ProjectReferenceTests.BasicTest No suitable constructor was found

…ixes #4235 and #4237. (#4512) (#4648) (#4773) In Xamarin.iOS.Common.targets, just before the _CompileToNative target, we modify the mtouch references to ensure that we get the lib assemblies for nugets, and not the ref references: https://github.com/xamarin/xamarin-macios/blob/9e31d07ecc08a64372dd562e843c3d8950d24985/msbuild/Xamarin.iOS.Tasks.Core/Xamarin.iOS.Common.targets#L784-L791 This logic removes nuget references, and then re-adds any copy-local dll references. This works fine in executable projects, but not in library projects (aka extensions), because nugets aren't copied for library projects: https://github.com/NuGet/NuGet.BuildTasks/blob/cf4b0a12cf1f75e0654f28c2a9020251c41d126a/src/Microsoft.NuGet.Build.Tasks/Microsoft.NuGet.targets#L86 So we need to set the CopyNuGetImplementations variable to 'true' for our library projects. Fixes #4235. Fixes #4237. * [tests] Redirect MSBuildExtensionsPath to MSBuildExtensionsPathFallbackPathsOverride when running msbuild for package reference tests. This fixes a problem where nuget restore would fail for projects with PackageReferences, because a variable would be empty and msbould would try to write to /: nuget restore ../MyAppWithPackageReference/MyAppWithPackageReference.csproj MSBuild auto-detection: using msbuild version '15.0' from '/Library/Frameworks/Mono.framework/Versions/Current/lib/mono/msbuild/15.0/bin/'. Restoring packages for /Users/builder/jenkins/workspace/xamarin-macios-pr-builder/msbuild/tests/MyAppWithPackageReference/MyAppWithPackageReference.csproj... Committing restore... Generating MSBuild file /MyAppWithPackageReference.csproj.nuget.g.props. Path / is a directory This will become unnecessary when PR #4111 is merged. * Add Xamarin.Mac test showing that fix is not needed (?!?) * Add AppExtension test with packagereference * Make extension actually have json code generated * Fix ProjectTypeGuids of checked in extension projects, as they were not openable in VSfM * XM extension test now correctly fails * Now that we have a failing test, fix XM same as rest of platforms * Disable XM tests due to msbuild redirect sadness * Disable iOS tests as well due to #4110 * Disable iOS tests by using the Ignore attribute. Disable tests by using the Ignore attribute, because just commenting out the TestCase attributes makes the test fail: 1) NotRunnable : Xamarin.iOS.Tasks.ProjectReferenceTests.BasicTest No suitable constructor was found

SaqibS · 2018-11-05T18:21:17Z

Hi, we temporarily got around this by forcing the system to use Mono 5.8.1, as recommended by the team. However, it would be good to get rid of this, yet the problem persists with Mono 5.12.0 and Xamarin.iOS 12.0. Appreciate any assistance.

rolfbjarne · 2018-11-06T06:44:45Z

@SaqibS this issue is fixed in Xamarin.iOS 12.0, so you might be running into something else. Could you file a new issue and include a test project we can use to reproduce your problem?

yevgeniy-seleznev · 2019-01-18T13:48:50Z

This still reproes with Mono 5.16, xamarin.ios 12.2.1.11, using Seeing AI app as the test. The ultimate mtouch error looks suspiciously like the original issue:

error MT0099 : Internal error : Not all assemblies for Xamarin.Sdk have link tasks. Please file a bug report with a test case (http://bugzilla.xamarin.com). [/Users/vsts/agent/2.144.0/work/1/s/iOS/App/SeeingAI.iOS.csproj

Still, I am going to go ahead and create a new bug and attach the full build log as you requested. Just a heads up. Thanks

spouliot assigned rolfbjarne Jun 12, 2018

kdubau mentioned this issue Jun 12, 2018

MTOUCH : error MT2002: Failed to resolve assembly: 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' #4237

Closed

mandel-macaque added this to the Future milestone Jun 13, 2018

rolfbjarne modified the milestones: Future, d15-8 Jun 14, 2018

rolfbjarne added bug If an issue is a bug or a pull request a bug fix macOS Issues affecting macOS iOS Issues affecting iOS labels Jun 14, 2018

rolfbjarne added a commit to rolfbjarne/xamarin-macios that referenced this issue Jul 26, 2018

[mtouch] Show warnings when we can't find referenced assemblies.

02f4395

This would have helped track down dotnet#4235.

rolfbjarne mentioned this issue Jul 26, 2018

[mtouch] Show warnings when we can't find referenced assemblies. #4511

Merged

rolfbjarne mentioned this issue Jul 26, 2018

[msbuild] Set 'CopyNuGetImplementations' to true for app extensions. Fixes #4235 and #4237. #4512

Merged

rolfbjarne closed this as completed in #4512 Aug 20, 2018

rolfbjarne mentioned this issue Aug 20, 2018

[msbuild] Set 'CopyNuGetImplementations' to true for app extensions. Fixes #4235 and #4237. (#4512) #4648

Merged

rolfbjarne modified the milestones: d15-8, d15-9 Aug 20, 2018

spouliot mentioned this issue Aug 24, 2018

[msbuild] Set 'CopyNuGetImplementations' to true for app extensions. Fixes #4235 and #4237. (#4512) (#4648) #4696

Closed

spouliot mentioned this issue Sep 7, 2018

[msbuild] Set 'CopyNuGetImplementations' to true for app extensions. Fixes #4235 and #4237. (#4512) (#4648) #4773

Merged

yevgeniy-seleznev mentioned this issue Jan 18, 2019

error MT0099 : Internal error persists in Release build with latest Mono #5437

Closed

ghost locked as resolved and limited conversation to collaborators May 5, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

error MT0099 : Internal error : Not all assemblies for Xamarin.Sdk have link tasks. #4235

error MT0099 : Internal error : Not all assemblies for Xamarin.Sdk have link tasks. #4235

kdubau commented Jun 12, 2018 •

edited

Loading

spouliot commented Jun 12, 2018

kdubau commented Jun 12, 2018

kdubau commented Jun 13, 2018

rolfbjarne commented Jun 13, 2018

rolfbjarne commented Jun 14, 2018

SaqibS commented Nov 5, 2018

rolfbjarne commented Nov 6, 2018

yevgeniy-seleznev commented Jan 18, 2019

error MT0099 : Internal error : Not all assemblies for Xamarin.Sdk have link tasks. #4235

error MT0099 : Internal error : Not all assemblies for Xamarin.Sdk have link tasks. #4235

Comments

kdubau commented Jun 12, 2018 • edited Loading

Description

Steps to Reproduce

Expected Behavior

Actual Behavior

Environment

Build Logs

Example Project (If Possible)

spouliot commented Jun 12, 2018

kdubau commented Jun 12, 2018

kdubau commented Jun 13, 2018

rolfbjarne commented Jun 13, 2018

rolfbjarne commented Jun 14, 2018

SaqibS commented Nov 5, 2018

rolfbjarne commented Nov 6, 2018

yevgeniy-seleznev commented Jan 18, 2019

kdubau commented Jun 12, 2018 •

edited

Loading