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.

Sign up for GitHub

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

Jump to bottom

Improve Screenshot/ViewHierarchy debouncing default behavior #2917

Closed
kahest opened this issue Sep 5, 2023 · 0 comments · Fixed by #2945
Closed

Improve Screenshot/ViewHierarchy debouncing default behavior #2917

kahest opened this issue Sep 5, 2023 · 0 comments · Fixed by #2945
Assignees
@stefanosiano
Labels
enhancement New feature or request Platform: Android

Comments

@kahest
Copy link
Member

kahest commented Sep 5, 2023

Description

Currently, capture events for Screenshots/ViewHierarchies are debounced based on time proximity with no consideration of the number of events per time frame. While this can be overridden using BeforeCaptureCallback to provide completely custom logic, the default behavior could be improved.

Suggestion is to introduce a threshold for number of events within a certain time frame. Below the threshold, no debouncing is applide by default.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stefanosiano stefanosiano

Labels
enhancement New feature or request Platform: Android
Projects
Mobile & Cross Platform SDK
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

improve default debouncing mechanism getsentry/sentry-java
3 participants
@kahest @romtsn @stefanosiano