-
Notifications
You must be signed in to change notification settings - Fork 573
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TimeoutError thrown in NodeJS client #6306
Comments
github-actions
bot
added
Encryption:Off
Frequency:Always
Repro:Always
SDK-Use:Sync
labels
Dec 6, 2023
I've just witnessed the same issue happen when there is a service outage. We've recently switched from using the React Native client where we didn't have any of these issues, to NodeJS where they seem to have started appearing.
|
Did you guys found any solution |
We had the config in the wrong place.
^ This originally wasn't nested within the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How frequently does the bug occur?
Always
Description
I'm using RealmJS in a NodeJS App that will sometimes start offline. When the app starts with an internet connection (and then loses/regains connectectivity intermittently) realm works great. However, when booting with no internet connection, the
open()
method is throwing an error.TimeoutError: Timed out: Realm could not be downloaded in the allocated time: 30000 ms.
I've tried a combination of config changes (including adding timeout values) to prevent this timeout from being thrown, but all don't seem to affect this error being thrown.
And
Am I misinterpreting the
timeOutBehavior
property? Or is the Realm client ignoring the given value and usingOpenRealmTimeOutBehavior.ThrowException
?Stacktrace & log output
Can you reproduce the bug?
Always
Reproduction Steps
No response
Version
12.3.1
What services are you using?
Atlas Device Sync
Are you using encryption?
No
Platform OS and version(s)
OSX Arm64 & Linux Arm64
Build environment
Which debugger for React Native: ..
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: