MTouch Assembly Loading Warnings

[Renewals]

Hello,

In our solution we have a .NET Standard project which references Syncfusion.Pdf.Net.Core and a Xamarin.iOS project which references Syncfusion.Xamarin.SfPdfViewer.IOS (using PackageReference).

When I build the application I receive the following 3 warnings:

MTOUCH : warning MT0109: The assembly 'Syncfusion.Compression.Portable.dll' was loaded from a different path than the provided path (provided path: /Users/vsts/.nuget/packages/syncfusion.xamarin.compression/17.2.0.34/lib/netstandard2.0/Syncfusion.Compression.Portable.dll, actual path: /Users/vsts/.nuget/packages/syncfusion.compression.net.core/17.2.0.34/lib/netstandard2.0/Syncfusion.Compression.Portable.dll). [/Users/vsts/agent/2.155.1/work/1/s/***.MyApp.iOS/***.MyApp.iOS.csproj] MTOUCH : warning MT0109: The assembly 'Syncfusion.Pdf.Portable.dll' was loaded from a different path than the provided path (provided path: /Users/vsts/.nuget/packages/syncfusion.xamarin.pdf/17.2.0.34/lib/netstandard2.0/Syncfusion.Pdf.Portable.dll, actual path: /Users/vsts/.nuget/packages/syncfusion.pdf.net.core/17.2.0.34/lib/netstandard2.0/Syncfusion.Pdf.Portable.dll). [/Users/vsts/agent/2.155.1/work/1/s/***.MyApp.iOS/***.MyApp.iOS.csproj] MTOUCH : warning MT0109: The assembly 'System.Text.Encoding.CodePages.dll' was loaded from a different path than the provided path (provided path: /Users/vsts/.nuget/packages/system.text.encoding.codepages/4.4.0/runtimes/win/lib/netstandard2.0/System.Text.Encoding.CodePages.dll, actual path: /Library/Frameworks/Xamarin.iOS.framework/Versions/12.2.1.11/lib/mono/Xamarin.iOS/Facades/System.Text.Encoding.CodePages.dll). [/Users/vsts/agent/2.155.1/work/1/s/***.MyApp.iOS/***.MyApp.iOS.csproj]

Is there a difference between the conflicting assemblies in these warnings, is this something that I should be worried about? Also, can you fix the Nuget packages so these warnings are not displayed at all?

I've also attached a sample project and linked a Github issue that I've logged https://github.com/xamarin/xamarin-macios/issues/6758, not knowing if this is a Xamarin.iOS issue or a Syncfusion issue.

Thank you,

Cosmin

Attachment: PackageReference_d0b9308e.zip

[Gayathri Ramalingam]

Hi Cosmin, 

 

We were able to reproduce the warning of “System.Text.Encoding.CodePages.dll' was loaded from a different path than the provided path” with sample shared by you in v17.2.0.34.  

 

We created a video for illustrating the same and it can be downloaded from the below links, 

https://www.syncfusion.com/downloads/support/forum/146698/ze/PackageIssue21597814 

 

We have forwarded this issue to our development team for further analysis and we will update further details by 20-August-2019. 

 

 

With Regards, 

Gayathri R 

 

[Renewals]

As a result we actually run into this crash:

SIGABRT: Method `Syncfusion.Pdf.PdfPageBase.ObtainAnnotations()' is inaccessible from method `Syncfusion.SfPdfViewer.iOS.ScrollViewEx+<LoadDocument>d__258.MoveNext()'

• (wrapper managed-to-native) System.Object.__icall_wrapper_mono_throw_method_access(intptr,intptr)
• ScrollViewEx+<LoadDocument>d__258.MoveNext ()
• AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_0 (System.Object state)
• NSAsyncSynchronizationContextDispatcher.Apply ()
• (wrapper managed-to-native) UIKit.UIApplication.UIApplicationMain(int,string[],intptr,intptr)
• UIApplication.Main (System.String[] args, System.IntPtr principal, System.IntPtr delegate)
• UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName)
• Application.Main (System.String[] args)

[Renewals]

In the end the solution was Syncfusion.Xamarin.Pdf in the .NET Standard project instead of Syncfusion.Pdf.Net.Core

[Gayathri Ramalingam]

Hi Cosmin,  

 

Thank you for your update. 

 

Yes. The warning of “System.Text.Encoding.CodePages.dll' was loaded from a different path than the provided path” does not occur while using Syncfusion.Xamarin.Pdf in the .NET Standard project instead of Syncfusion.Pdf.Net.Core. 

 

Please let us know if you need any assistance. 

 

With Regards, 

Gayathri R