getsentry
Send a back-navigation transaction if an error occurred inside of it
We currently discard "back navigation" transactions if there are no child spans, but in the chance that an error occurs during the transaction, the trace id is attached to the event but the transaction is not sent, causing a trace not found on the dashboard.
We should consider sending back-navigation transactions when there is an event that occurred inside of it.
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Why don't we send back navigation transactions in the first place? Is that to spare some quota because at this moment nothing is really happening?
If so, that makes sense, just wondering if the solution here is to not set the traceId at all then.
We would need to change the default of this option, so this is a breaking change.
https://github.com/getsentry/sentry-react-native/blob/11ab73752331eb40918174de20c0793c7e262cfb/src/js/tracing/reactnativetracing.ts#L62
