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

Release adoption chart/numbers are zero, except for some antient releases #3862

Closed
gdanov opened this issue Jun 3, 2024 · 3 comments
Closed

Comments

@gdanov
Copy link

gdanov commented Jun 3, 2024

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

I'm using react-native + expo sdk on the FE and nodejs SDK on the BE.
Since many releases, my "release adoption" charts are useless as they started show zero.
The only place where user/session profile (identity) is established is the FE, if this is relevant.
I don't have idea where to start debugging this.

Expected Result

release adoption numbers are realistic

Actual Result

release adoption numbers are zero

Product Area

Stats

Link

No response

DSN

No response

Version

24.1 — 24.5

@getsantry
Copy link

getsantry bot commented Jun 3, 2024

Assigning to @getsentry/support for routing ⏲️

@InterstellarStella InterstellarStella transferred this issue from getsentry/sentry Jun 4, 2024
@azaslavsky azaslavsky transferred this issue from getsentry/self-hosted Jun 5, 2024
@krystofwoldrich
Copy link
Member

Hi @gdanov,
thank you for the message,

could you share a bit more details about your self hosted setup?

Are all the releases using the same version of the Sentry RN SDK?

What was the last version of the SDK that reported adoption/sessions?

Do you have auto session tracking enabled, could you share your Sentry.init?

What version of the self hosted Sentry are you using now and were you using the same version in the past when the previous app releases were reporting adoption/sessions?

@krystofwoldrich
Copy link
Member

Closing this due to inactivity. If this is still an issue feel free to comment here or open a new issue if the context changed.

@krystofwoldrich krystofwoldrich closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Archived in project
Archived in project
Development

No branches or pull requests

2 participants