feat(replay): Use logs instead of captureMessage for mobile touch start debugging
#92502
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tart debugging This PR does two things: - fix to only send on mobile replays - change to use logs instead of captureMessage, since we dont need the full event context
github-actions
bot
added
the
Scope: Frontend
billyvg
commented
May 29, 2025
static/app/utils/replays/playback/hooks/useTouchEventsCheck.tsx
Outdated
Show resolved
Hide resolved
ryan953
approved these changes
May 29, 2025
Co-authored-by: Ryan Albrecht <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does two things: