Add structured app/device fields to BugsnagSession #546
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
Adds structured app/device fields to
BugsnagSession
and passes the structured session object intoOnSessionCallback
to allow users to modify/inspect the payload.Changeset
OnSessionCallback
to take aBugsnagSession
parameter rather than a dictionaryBugsnagSessionTracker
to generate a structuredBugsnagSession
objectsession.sessionId
tosession.id
session.app
andsession.device
session.user
conform to notifier spec with set method + getterBugsnagSession
to JSONBugsnagSession
from a cached payload[BSG_KSSystemInfo systemInfo]
to include memory information by default, to ensuredevice.totalMemory
is populated for sessionsSessionTrackingApiClient
logic to avoid batching of session payloads, as the app/device information can now differ between individual sessionsBugsnagSession
andBugsnagUser
headers publicly accessibleTests
BugsnagSession
object is populated during a callback in the example app