Uploaded image for project: 'Realm JavaScript SDK'
  1. Realm JavaScript SDK
  2. RJS-1773

Collection Change Listener stops listening until next event emits and then proceeds to stop listening

      How frequently does the bug occur?

      Sometimes

      Description

      Our application starts initializing realm when mounting the main screen.
      It starts listening to ~5 different collections.
      Initially everything seems to be working fine.
      However, after for example, refreshing/reloading the app (debug mode), only the initial callbacks are called for the collection listeners but they don't react to any changes.
      If I make emit any event (a realm.write transaction or net-info) the change listeners are reacting again but proceed to stop listening.

      If I call the initialization of realm two times - directly after mount & then couple of seconds later again (closing the previously initialized realm instance) - the problem occures less often.
      I tried different devices and with mobiles on better hardware the problem occurs more often.
      This happens also in PRODUCTION.
      Maybe it has something to do with react-native itself, but maybe you can lead me to the root of the problem as I experience this bug only when using realm.

      Stacktrace & log output

      No response

      Can you reproduce the bug?

      Yes, sometimes

      Reproduction Steps

      No response

      Version

      10.20.0-beta.3, 10.20.0-beta.5

      What SDK flavour are you using?

      Atlas App Services (auth, functions, etc.)

      Are you using encryption?

      No, not using encryption

      Platform OS and version(s)

      ANDROID

      Build environment

      "react-native": "0.67.4"
      "realm": "^10.20.0-beta.5"

      Cocoapods version

      No response

            Assignee:
            Unassigned Unassigned
            Reporter:
            unitosyncbot Unito Sync Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: