Alex Coulcher

No stack trace, unfortunately. Pause/Resume seems to work before the initial sync has been completed. However, once it has (based on the `realm.syncSession.addConnectionNotification` event handler being called), calling pause/resume causes...

We were originally testing with `12.3.1` when we found the issue, but upgraded to `12.6.2` to check if it was resolved

We only have specific time windows on internet access, which is why we need some kind of 'force-sync' feature as we've found that the NodeJS Client doesn't seem to do...

@kneth I can replicate the SIGSEGV here... ``` import Realm from 'realm'; const ATLAS_APP_ID = ''; const ATLAS_API_KEY = ''; export const Point = { name: 'Point', embedded: true, properties:...

@danieltabacaru it was the documentation [here](https://www.mongodb.com/docs/realm/sdk/react-native/sync-data/manage-sync-session/#when-to-pause-a-sync-session) that lead me to believe that this might be possible

@nirinchev When I mention to 'initial sync', I am referring to when Realm uploads offline data for the first time the process starts. Based on my reproduction above, when you...

@danieltabacaru Nothing follows the `resume()`. As soon as its called we get the `SIGSEGV`

I couldn't find a documented way of using Embedded objects with the Class syntax. Updating the above example to just use JS schemas still results in the SIGSEGV.

I don't think it's in this repository. The action seems to just post a load of stuff to a specific API. The API is undocumented in Asana docs

Appreciated. I'll be back on this later in the week so I'll report back any findings.