You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're having issues getting anything out of realmRef.current
it appears to always be either null, an empty object, or {"syncSession": undefined} when logging the results.
Previously using const realm = useRealm(); realm.syncSession.addProgressNotification(...) within the Realm Provider worked well.
Now we'd like to use the values from this progress notification to display within the fallback component to display a loading update to users for longer syncs.
However, when trying to use the realmRef as described in #4571, the value provided is either empty, or doesn't trigger a useEffect when needed.
@carbopilot The upcoming realm update will fix the progress notification functionality for flexible sync, so we are also now looking into improving the experience of using progress notifications with @realm/react. See #5459 and #6797
How frequently does the bug occur?
All the time
Description
We're having issues getting anything out of
realmRef.current
null
, an empty object, or{"syncSession": undefined
} when logging the results.Previously using
const realm = useRealm(); realm.syncSession.addProgressNotification(...)
within the Realm Provider worked well.Now we'd like to use the values from this progress notification to display within the
fallback
component to display a loading update to users for longer syncs.However, when trying to use the
realmRef
as described in #4571, the value provided is either empty, or doesn't trigger auseEffect
when needed.Stacktrace & log output
No response
Can you reproduce the bug?
Yes, always
Reproduction Steps
Here is a reduced reproduction:
On app load, sync occurs, but the only console output is:
Version
0.4.1
What SDK flavour are you using?
Atlas Device Sync
Are you using encryption?
Yes, using encryption
Platform OS and version(s)
MacOs 13.0
Build environment
No response
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: