feat: Automatic trace instrumentation for MAUI

[jamescrosswell]

Resolves #5116

• Auto-create traces for MAUI UI events #5116

Description

Adds automatic tracing support in Sentry.Maui applications.

This initial PR is fairly lean and adds only adds tracing for button clicks and Shell navigation events. So if you click on a button or an image button that results in a Shell navigation, this will be captured automatically as a transaction, which is useful to identify performance problems with application navigation.

Trivial button clicks (with no child spans) wil be filtered automatically and not captured.

The plan is to expand on this functionality to also automatically create traces for Scroll events and capture things like Mobile Vitals at startup:

• Mobile Vitals #3181

Sample

An example of the output from Sentry.Samples.Maui when opening and closing the SubmitFeedback modal:

Note

Tracing for button clicks only works if the buttons have some id associated with them (x:Name)... for example:

sentry-dotnet/samples/Sentry.Samples.Maui/SubmitFeedback.xaml

Lines 20 to 21 in bc1c8ab

	<Button x:Name="CancelBtn" Text="Cancel" Clicked="OnCancelClicked" BackgroundColor="Red" TextColor="White" />
	<Button x:Name="SubmitBtn" Text="Submit" Clicked="OnSubmitClicked" BackgroundColor="Green" TextColor="White" />

Resolves: #5109

• Transactions for UI events in MAUI #5109

Implementation

Tracing for UI applications is a little bit complex.

Typically very little work will be done on the main UI thread, to avoid freezing/blocking this. So a UI interaction like a button click might navigate to a new view, a spinner icon animation kicks off and, technically, at that point, the navigation is completed. In reality the app may be implementing some kind of progressive display and loading of portions of that display is still taking place in the background (getting some stuff from a database to load up in the main panel, pulling access control credentials from a remote source to determine what actions should be available on the menu etc.).

The solution we have then is to start a new transaction with an idle timer on it:

• If the idle timeout is reached before any other activity happens on the transaction (child spans added) then we simply discard the transaction as trivial/irrelevant.
• If a child span kicks off on the transaction though, we reset the idle timeout... and we keep doing that as long as there is activity
• When the idle timeout finally triggers, if there are child spans on the transaction, the end date/time for the transaction is set as the end date/time of the last child span to finish

This won't be accurate 100% of the time, but it should be a pretty good approximation most of the time.

[github-actions]

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

Features ✨

• feat: Automatic trace instrumentation for MAUI by jamescrosswell in #5138

Fixes 🐛

• fix: prevent redundant native exceptions on Android/CoreCLR by jpnurmi in #5127

Dependencies ⬆️

Deps

• chore(deps): update Java SDK to v8.39.0 by github-actions in #5137
• chore(deps): update Native SDK to v0.13.7 by github-actions in #5136

Other

• perf(logs): avoid string allocation when no parameters are passed by Flash0ver in #4697
• chore: fix missing skill by jamescrosswell in #5134

---

_{🤖 This preview updates automatically when you update the PR.}

[codecov]

Codecov Report

❌ Patch coverage is 64.35644% with 36 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.94%. Comparing base (e99c3d1) to head (d17a61e).
⚠️ Report is 34 commits behind head on main.

Files with missing lines	Patch %	Lines
src/Sentry/TransactionTracer.cs	70.76%	10 Missing and 9 partials ⚠️
src/Sentry/Infrastructure/SystemTimer.cs	0.00%	6 Missing ⚠️
src/Sentry/SentrySdk.cs	0.00%	5 Missing and 1 partial ⚠️
src/Sentry/Extensibility/DisabledHub.cs	0.00%	1 Missing ⚠️
src/Sentry/Extensibility/HubAdapter.cs	0.00%	1 Missing ⚠️
...c/Sentry/Internal/DefaultSentryStructuredLogger.cs	87.50%	0 Missing and 1 partial ⚠️
src/Sentry/Internal/Hub.cs	50.00%	1 Missing ⚠️
src/Sentry/Internal/NoOpTransaction.cs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5138      +/-   ##
==========================================
+ Coverage   74.04%   76.94%   +2.89%     
==========================================
  Files         501      413      -88     
  Lines       18107    15366    -2741     
  Branches     3523     3047     -476     
==========================================
- Hits        13408    11823    -1585     
+ Misses       3838     2820    -1018     
+ Partials      861      723     -138     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jamescrosswell]

Removing this tests for two reasons:

1. It's in the wrong place... this is testing the TransactionTracer, not the SentryTransaction
2. The behaviour has changed with this PR... we only automatically capture transactions on IdleTimeout now if they have child spans. So a simple button click wouldn't create an auto-transaction but a button click that triggered a navigation event or which made ah HTTP request would.

Tests for all of that stuff instrumented in test/Sentry.Tests/TransactionTracerTests.cs

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d17a61e. Configure here.}