Flush persisted sessions on launch and on connectivity changes #973
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goal
Session payloads are persisted on disk if a request to bugsnag was unsuccessful. Delivery of these is only attempted currently when a new session is captured. To increase the speed with which requests are received, delivery should also be attempted on
Client
initialization` and whenever connectivity changes.Changeset
Called
flushAsync()
in the client constructor and connectivity change callback. Access to this method is guarded by a Semaphore so concurrent calls will be ignored.Testing
Relied on existing E2E tests, and manually verified that an undelivered session is now delivered when the client is launched or the connectivity is regained.