[CSHARP-3277] MongoDB.Driver latest version 2.11.4 breaks compiling Xamarin iOS Created: 01/Dec/20  Updated: 27/Oct/23  Resolved: 23/Mar/21

Status: Closed
Project: C# Driver
Component/s: Build
Affects Version/s: 2.11.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Sasan Pasha Assignee: Dmitry Lukyanov (Inactive)
Resolution: Works as Designed Votes: 0
Labels: buildfest
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Visual Studio Windows 16.8.2 and Visual Studio for Mac 8.8.2
Xamarin.iOS 14.0.15, Xamarin 16.8.000.255


Attachments: Text File build.txt    
Issue Links:
Backports
backported by CSHARP-3178 MongoDB.Driver latest version 2.11 br... Closed
Epic Link: Support Xamarin

 Description   

create a xamarin forms app, targeting iOS and Androud. as soon as the nuget is updated to the latest version 2.11.4, xamarin ios app won't compile with the following error 

MTOUCH : error MT0009: Error while loading assemblies: nuget/packages/mongodb.driver.core/2.11.0/runtimes/win/native/libzstd.dll

the stable working version is 2.10.4

 

@dmitry.lukyanov@mongodb.com this issue was not addressed nor tested with the original link 

  1. CSHARP-3178

created.



 Comments   
Comment by Dmitry Lukyanov (Inactive) [ 23/Mar/21 ]

sasan.pasha@gmail.com please reopen this ticket if you still have any question.

Comment by Dmitry Lukyanov (Inactive) [ 23/Mar/21 ]

The issue was related to the mono msbuild bug that has a workaround. The consumer xamarin app on iOS should add these lines to his csproj:

<RuntimeIdentifiers>osx;osx-x86;osx-x64</RuntimeIdentifiers>
<NuGetRuntimeIdentifier>osx</NuGetRuntimeIdentifier>

This allows me to build the test app.

Comment by Dmitry Lukyanov (Inactive) [ 30/Dec/20 ]

Hello sasan.pasha@gmail.com , for now, this looks like a xamarin issue. I filed an issue https://github.com/xamarin/xamarin-macios/issues/10337 I will let you know asap when I will have new details.

Comment by Sasan Pasha [ 30/Dec/20 ]

hello  @ Dmitry Lukyanov

happy new  year - i am following up on the progress of the update to the driver. Does it mean you will have your testing also includes xamarin framework from now on? can you perhaps get in touch with xamarin.forms team to get to the solution faster. I reported this issue August 2020 - 5 months now. 

when do you anticipate to have a tested and workable fix that doesn't break the future releases?

thanks

sasan

Comment by Dmitry Lukyanov (Inactive) [ 22/Dec/20 ]

Hello sasan.pasha@gmail.com ,

thank you for your report, unfortunately, we don't test the driver on xamarin, so we've missed the time when xamarin build was broken. We see that it's related to ".target" file that was added recently, but it's unclear how we can use this file without triggering this issue, we're working on this issue now and will let you know about the results

Comment by Sasan Pasha [ 17/Dec/20 ]

Hello @dmitry.lukyanov , any update on this issue ?

Comment by Sasan Pasha [ 07/Dec/20 ]

hello @dmitry.lukyanov - last time I waited for 3 months - this is a production issue for us and we can't update our iOS app because of this. can you please 

1- give me some estimates on when this will be fixed?

2- what will you do to ensure this never happens in the future? as you know both xamarin.ios and xamarin frameworks get updates on a regular basis. I hope you are also testing your driver against these updates on a regular basis. can you please confirm?

Comment by Dmitry Lukyanov (Inactive) [ 07/Dec/20 ]

Hello sasan.pasha@gmail.com , sorry to hear that this is the issue for you again, we will investigate it further and will let you know about the results.

Comment by Sasan Pasha [ 02/Dec/20 ]

hi @dmitry.lukyanov@mongodb.com this is confirmed on 2.11.4  - i forgot tot change that in the the comments section.

Comment by Dmitry Lukyanov (Inactive) [ 01/Dec/20 ]

Hello sasan.pasha@gmail.com . Are you sure that you updated the driver on 2.11.4 version? As I see, your error tells about `2.11.0`

Comment by Sasan Pasha [ 01/Dec/20 ]

the original issue that was closed wasn't tested at all. i still see the issue.

Generated at Wed Feb 07 21:44:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.