Closed kpujjigit closed 10 months ago
@kpujjigit Seems to work (again?), see e.g. here. I checked the last 20 or so instances by selecting "Latest" event and navigating back one by one - everyone had 5 events in the trace with 2 tx and 2 issues. Compare to "Oldest" event from Sept 20 which is missing the backend error.
@kpujjigit Suspect commits have been always brittle. Next time let's immediately raise this in #discuss-issues
and get to the bottom of it. In my experience usually it has nothing to do with SDK/client-side.
@kahest - This is resolved, issue was on the Flask side. See more here - https://github.com/sentry-demos/empower/pull/366
@kpujjigit Suspect commits have been always brittle. Next time let's immediately raise this in
#discuss-issues
and get to the bottom of it. In my experience usually it has nothing to do with SDK/client-side.
@realkosty just verifying this comment is in the right spot? This GH Issue concerns Dist. Tracing, not Suspect Commits; those are still broken.
The Full Trace View does not yet link to the backend Flask error that is invoked as part of the iOS Demo's Flagship Error.
Example from Flagship Error: https://demo.sentry.io/issues/4221692556/?project=6249899
(Currently only seeing the backend Transaction in addition to the mobile error)