Failed to start notifier on Realm Server 1.1.0 with Realm 3.0.0 installed


#1

It seems that Realm 3.0.0 is not compatible with Realm Server 1.1.0 on .Net platform (My ROS version is 3.1.8).
When Realm 3.0.0 and Realm Server 1.1.0 installed together, and a notifer is being started by calling Notifier.StartAsync it throws an exception:
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.

Please take a look.


#2

Which platform does that happen on? Linux/Windows/macOS?


#3

ROS is deployed on Ubuntu 16.04, and the Realm server development environment is Windows 10.
When I remove the reference of Realm 3.0.0 package, everything is ok.


#4

Can you share a project that reproduces this?


#5

All right. I deployed ROS to a public server. Please take a look at my source code
RealmServerTest.zip


#6

Thanks for submitting the project. I verified the crash. We’ll try to debug and fix whatever’s causing it soon.


#7

Getting same exception trying to run a test in xunit. After last assertion it throws:

System.Runtime.InteropServices.SEHException : External component has thrown an exception.
Exception doesn’t have a stacktrace

I tried calling dispose on the realm but no change.

Realm 3.0.0 with default local realm
basically

var realm = Realm.GetInstance();
realm.Write(() => realm.Add(newItem));
var actual = realm.All().First(d => d.Id == newItem.Id)
Assert.Equal(newItem.Id, actual.Id)

realm.Dispose() //Added as precaution