[mvanhorn]

📜 Description

SentryTracer now records the wall-clock time when the deadline timeout is scheduled and, when the timer fires far later than scheduled (more than 2x the configured deadlineTimeout), drops the transaction instead of force-finishing it with now(). The drop follows the existing dropIfNoChildren pattern in finish(): DEBUG log, clear the scope's transaction, cancel timers, no captureTransaction. Timers that fire within the slack behave exactly as before (forceFinish with DEADLINE_EXCEEDED).

💡 Motivation and Context

When an Android app cold-starts and is backgrounded before first frame, the ui.load transaction's 30s deadline timer (a java.util.Timer) is frozen during Doze and fires only hours later when the device wakes. forceFinish then stamps the root span and all children with the current time, producing app-start transactions spanning hours and skewing user-perceived launch metrics. "Timer fired far later than scheduled" is the exact failure signature, so the check stays in platform-neutral core with no Android API and no public API change.

Resolves #5752

💚 How did you test it?

New unit tests in SentryTracerTest: a deadline timeout that fires within the slack still force-finishes with DEADLINE_EXCEEDED; a simulated late fire (scheduled timestamp shifted beyond 2x deadline) drops the transaction, clears it from the scope, and captures nothing. Ran the sentry module test suite.

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.

🔮 Next steps

[cursor]

Stale Bugbot comment from a previous run.

[mvanhorn]

Fixed the failing checks in 3bc4794: the root span is now finished when the deadline timer fires too late (so the dropped transaction reads as finished), the two logger-mock tests enable options.isDebug so DiagnosticLogger actually forwards to the mock, and the test file is spotless-formatted. Verified locally on JDK 17: spotlessCheck plus the full SentryTracerTest suite pass.

[mvanhorn]

Brought the branch up to date with main (c134c2e). It was 69 commits behind with conflicts in CHANGELOG.md and SentryTracer.java, both resolved, so it's mergeable again.

The fix itself is unchanged from 3bc4794.

[runningcode]

Hi @mvanhorn sorry for the delay, we've just prioritized a project looking at how we measure time and set deadline timers in the SDK. It will be a big refactor and we will reconsider this PR if the refactor doesn't fix this issue.

[mvanhorn]

Merged main back in (98e3ecd) to clear the SentryTracerTest import conflict. Two small follow-ups came with it: the changelog entry had drifted into an already released section, so it is back under Unreleased, and the late deadline check now compares in long millis because the new -Werror LongDoubleConversion rule flagged the old double math. spotlessCheck and SentryTracerTest (120 tests) pass locally on JDK 21. No rush on review given the timer refactor you mentioned.

[cursor]

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

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

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

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

[mvanhorn]

Pushed 2755b91 to address the Bugbot finding on the late-deadline drop: it now reuses the normal finish path and skips only the capture, so profilers and the performance collector are no longer left running. All 121 SentryTracerTest cases are green on JDK 21, including the new one. Still no rush given the timer refactor.