When sending a session update payload, some SDKs may be also adding a breadcrumb, such as "Session Started", "Session Finished", etc. Such breadcrumbs can create user confusion, because typically a session ends after an event is captured. For example, a "Session Finished" breadcrumb would only appear if a session was stopped and a new one was started - and in that case they would appear out of sequence.
SDKs should not add breadcrumbs corresponding to session updates.
If a particular SDK has a need to add breadcrumbs for application lifecycle events (such as app start, stop, pause, resume, etc. in a mobile app), it should do so independently of Sentry's session updates.
This issue is to verify that session breadcrumbs have been removed from the SDK, or were never present to begin with.
When sending a session update payload, some SDKs may be also adding a breadcrumb, such as "Session Started", "Session Finished", etc. Such breadcrumbs can create user confusion, because typically a session ends after an event is captured. For example, a "Session Finished" breadcrumb would only appear if a session was stopped and a new one was started - and in that case they would appear out of sequence.
SDKs should not add breadcrumbs corresponding to session updates.
If a particular SDK has a need to add breadcrumbs for application lifecycle events (such as app start, stop, pause, resume, etc. in a mobile app), it should do so independently of Sentry's session updates.
This issue is to verify that session breadcrumbs have been removed from the SDK, or were never present to begin with.