-
Notifications
You must be signed in to change notification settings - Fork 585
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
iOS v10.20.0-beta.2 Flexible sync: subscriptions.update crashes after token expiry #4421
Labels
Comments
@Joelfrewy Thank you for reporting this issue. |
We're experiencing a similar issue on |
Hi @Joelfrewy. Thanks for filling the bug. We identified the problem and it will be fixed by #5343. |
Waiting on new core release to get this fix into Realm JS |
kneth
added a commit
that referenced
this issue
Apr 8, 2022
* Update core to v11.13.0 * Closes #4421 * Update podspec to include libcompression * Update CHANGELOG.md Co-authored-by: Kenneth Geisshirt <[email protected]>
sync-by-unito
bot
changed the title
iOS v10.20.0-beta.2 Flexible sync: subscriptions.update crashes after token expiry
iOS v10.20.0-beta.2 Flexible sync: subscriptions.update crashes after token expiry
Mar 15, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How frequently does the bug occur?
All the time
Description
Initialising realm subscriptions with flexible sync on iOS results in a crash. This crash only occurs roughly 30 mins after initially logging in (surely due to token expiration?). running
refreshCustomData()
before updating subscriptions fixes the issue, however this function requires internet access which could brick an offline app.Stacktrace & log output
Can you reproduce the bug?
Yes, always
Reproduction Steps
Version
v10.20.0-beta.2 Hermes
What SDK flavour are you using?
MongoDB Realm (i.e. Sync, auth, functions)
Are you using encryption?
No, not using encryption
Platform OS and version(s)
iOS 15.3.1
Build environment
Release Mode
Cocoapods version
1.11.2
The text was updated successfully, but these errors were encountered: