-
-
Notifications
You must be signed in to change notification settings - Fork 435
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
attach screenshots only when crash happens #2665
Comments
My question is similar Can the screenshot function be reported based on custom scenarios?Not necessarily |
For the moment, you can drop screenshots for non-crashed events via SentryAndroid.init(context) { options ->
options.beforeSend = SentryOptions.BeforeSendCallback { event, hint ->
if (!event.isCrashed) {
hint.screenshot = null
}
event
}
} We're discussing internally whether we want to introduce a new option for capturing screenshots for handled events, but no decision yet. @hu441444238xin what custom scenarios do you have in mind? Would like to better understand them before suggesting anything. |
Hi @kasogg @hu441444238xin I have good news for you: We've added support for customizing the capture behavior with the upcoming |
Happy
发自我的iPhone
…------------------ Original ------------------
From: Markus Hintersteiner ***@***.***>
Date: Thu,Jun 22,2023 3:39 PM
To: getsentry/sentry-java ***@***.***>
Cc: feiwang ***@***.***>, Mention ***@***.***>
Subject: Re: [getsentry/sentry-java] attach screenshots only when crashhappens (Issue #2665)
Hi @kasogg @hu441444238xin I have good news for you: We've added support for customizing the capture behavior with the upcoming 6.24.0 release of our SDK. The docs also illustrate on how your use-case can be supported.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Problem Statement
Is there a way to attach screenshots only in crash issues? Custom exception do not need to attach screenshots.
Solution Brainstorm
Add an option in SentryAndroidOptions.
No response
The text was updated successfully, but these errors were encountered: