-
Notifications
You must be signed in to change notification settings - Fork 82
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
Crash in background during onFlagSyncComplete #267
Comments
Hello @pandavid87, sorry for the delay. We are looking into this and I have a couple of questions. Does this happen frequently from your record? And does the device(s) that experienced this error have a good internet connection? Given the 5.4.5 change only updated the |
There are several bits of information that can contribute to upstream service cache hits. One of these is the shape of the context payload. By maintaining a stable encoding format, we can increase the likelihood of a cache hit.
There are several bits of information that can contribute to upstream service cache hits. One of these is the shape of the context payload. By maintaining a stable encoding format, we can increase the likelihood of a cache hit.
There are several bits of information that can contribute to upstream service cache hits. One of these is the shape of the context payload. By maintaining a stable encoding format, we can increase the likelihood of a cache hit.
🤖 I have created a release *beep* *boop* --- ## [8.4.0](8.3.1...8.4.0) (2023-12-29) ### Features * Store and use e-tag header between SDK initializations ([#268](#268)) ([701aaa8](701aaa8)) ### Bug Fixes * LDContext equality is no longer order dependent ([#265](#265)) ([683e0c3](683e0c3)) * Use stable encoding format to increase cache hits ([#267](#267)) ([40a5d01](40a5d01)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: LaunchDarklyReleaseBot <LaunchDarklyReleaseBot@launchdarkly.com>
🤖 I have created a release *beep* *boop* --- ## [9.3.0](9.2.1...9.3.0) (2024-01-02) ### Features * Store and use e-tag header between SDK initializations ([#268](#268)) ([701aaa8](701aaa8)) ### Bug Fixes * LDContext equality is no longer order dependent ([#265](#265)) ([683e0c3](683e0c3)) * Use stable encoding format to increase cache hits ([#267](#267)) ([40a5d01](40a5d01)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: LaunchDarklyReleaseBot <LaunchDarklyReleaseBot@launchdarkly.com> Co-authored-by: Matthew Keeler <mkeeler@launchdarkly.com>
This issue is marked as stale because it has been open for 30 days without activity. Remove the stale label or comment, or this will be closed in 7 days. |
Describe the bug
Seeing a crash come in via Xcode Organizer related to the FlagSynchronizer. Looks like there is some callback that is dispatched on the main queue, which triggers a lock and resulted in the app being terminated by Watchdog.
To reproduce
No clear reproductions steps.
Expected behavior
App should not crash in the backgrond
Logs
SDK version
5.4.5
OS/platform
iOS 14+
Additional context
Based on the crash logs I'm seeing, we only started seeing this crash after we updated from LaunchDarkly SDK version 5.4.4 -> 5.4.5
The text was updated successfully, but these errors were encountered: