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

Device Sync stoped working: could not decode next message: failed to get reader: WebSocket closed: failed to acquire lock: context deadline exceeded

      How frequently does the bug occur?

      Once

      Description

      Scenario is no READ or WRITE operations permitted and user is stuck. We should expect at least a client reset in this case to unblock user. Getting constant error on server logs:

      > could not decode next message: failed to get reader: WebSocket closed: failed to acquire lock: context deadline exceeded

      Stacktrace & log output

      Unable to find source-code formatter for language: shell. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
      Error:
      
      
      could not decode next message: failed to get reader: WebSocket closed: failed to acquire lock: context deadline exceeded
      
      Logs:
      
      [
        "Connection was active for: 1m4s"
      ]
      Function Call Location:
      
      DE-FF
      
      Remote IP Address:
      
      151.47.237.19
      
      SDK:
      
      JS v12.6.0
      
      Framework:
      
      react-native v0.71.8
      
      Platform:
      
      iOS v16.3
      

      Can you reproduce the bug?

      Sometimes

      Reproduction Steps

      No response

      Version

      12.6.0

      What services are you using?

      Atlas Device Sync

      Are you using encryption?

      No

      Platform OS and version(s)

      iOS v16.3

      Build environment

      Which debugger for React Native: ..

      Cocoapods version

      No response

            Assignee:
            nikola.irinchev@mongodb.com Nikola Irinchev
            Reporter:
            unitosyncbot Unito Sync Bot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: