Skip to content
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

Not all warm start cases covered by SDK? #3899

Open
zhukic opened this issue Nov 18, 2024 · 0 comments
Open

Not all warm start cases covered by SDK? #3899

zhukic opened this issue Nov 18, 2024 · 0 comments

Comments

@zhukic
Copy link

zhukic commented Nov 18, 2024

Problem Statement

Hi!

Sentry SDK version - 7.14.0

Currently, SDK reports the warm start only in case when an application was launched from background state and activity is created with non-null bundle(how to reproduce it).

But, according to the documentation there are another cases like The user backs out of your app but then re-launches it. The process might continue to run, but the app must recreate the activity from scratch using a call to onCreate().

Image

For example, when an application receives a push notification, the process and application are initialized; if we launch the app after that, only activity is created, and it looks like a case for the warm start, but the SDK doesn't report it.

Another case(but I'm not sure if it's a really warm start) - the app goes to the background, the system kills all activities, and then we launch the app. In this case, the process still exists, and only activity is created(can be reproduced with "Don't keep activities" enabled).

We see that the number of warm starts reported by SDK is much less than the number of starts we see in Google Play Console, so covering all such possible cases should reduce the difference.

What do you think?

Solution Brainstorm

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting for: Product Owner
Status: Needs Discussion
Development

No branches or pull requests

2 participants