search

realm / realm-dotnet

Realm is a mobile database: a replacement for SQLite & ORMs
https://realm.io
Apache License 2.0
1.26k stars 165 forks source link

Update 12.3.0 [MDBClass]_generated.cs Errors #3658

Open CharlesDavidEly opened 3 months ago

CharlesDavidEly commented 3 months ago

What happened?

Ever since updating the Realm package from version 12.2.0 to 12.3.0 (and the other needed MongoDB packages similarly), I'm experiencing the same 8 errors on build for every MDB class in our application. These errors are occuring for both IRealmObject and IEmbeddedObject classes.

Screenshot 2567-08-09 at 13 11 13

Is there something about our class implementation that was just recently made archaic by this latest update? Or is there now some bug in the current package code that something about our implementation is triggering? Please see the repro steps section for class screenshots.

In the off chance that it's relevant and the Realm package isn't the issue, the other concurrent MongoDB package updates are: MongoDB.Bson: 2.27.0 => 2.28.0 MongoDB.Driver: 2.27.0 => 2.28.0 MongoDB.Driver.GridFS: 2.27.0 => 2.28.0

Thank you in advance!

Repro steps

Screenshot 2567-08-09 at 13 13 22 Screenshot 2567-08-09 at 13 12 08

Version

8.0.302

What Atlas Services are you using?

Atlas Device Sync

What type of application is this?

Xamarin

Client OS and version

All iOS and Android emulators; not relevant to the issue

Code snippets

No response

Stacktrace of the exception/crash you're getting

No response

Relevant log output

No response

sync-by-unito[bot] commented 3 months ago

➤ PM Bot commented:

Jira ticket: RNET-1172

papafe commented 3 months ago

I just managed to reproduce this. The realm update did not cause any issue, but the MongoDB.Bson library did and this seems to be related to their new strongly-named assembly. For now, I'd suggest to downgrade the MongoDB.Bson library.

CharlesDavidEly commented 3 months ago

Interesting, thank you for looking into this @papafe. After downgrading our application's MongoDB.Bson library things are indeed working as normal again. Please let me know of any updates!