-
Notifications
You must be signed in to change notification settings - Fork 86
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 when app goes to Background #231
Comments
Hi @TomCobo, thanks for reporting this. Is this happening in a development or production environment? Are there a large number of events that the SDK is trying to flush? Do the devices seeing crashes have poor internet connections? |
hi @torchhound, thanks for the quick response. Note: I've been debugging a bit our app using Network Link Conditioner and it seems stable. |
@torchhound - Should we also open a Support ticket with our TAM to help with this issue? Internal reference: NIR-15644 Thanks -Josh |
Hi all, this sounds similar to another customer reported bug that was fixed in version 5 of the iOS SDK. @jbrozen opening a ticket is fine, please try upgrading the SDK if possible. |
Hi all, we haven't heard back from you in a few months so I'm going to close this issue. Please feel free to comment if this is not resolved or reach out to [email protected]. |
**Requirements** - [ ] I have added test coverage for new or changed functionality (Skipping this, that seems like a silly test to add) - [x] I have followed the repository's [pull request submission guidelines](../blob/v6/CONTRIBUTING.md#submitting-pull-requests) - [x] I have validated my changes against all supported platform versions **Related issues** https://app.shortcut.com/launchdarkly/story/198156/fix-ios-builder-tryset-for-kind
Describe the bug
We are experiencing some of the sessions crash when the app goes to the background state.
To reproduce
Unable to reproduce. We got just the stack trace and some logs.
Stack trace
SDK version
4.7.0
Language version, developer tools
Swift 5.x
OS/platform
iOS 12, 13, 14
The text was updated successfully, but these errors were encountered: