chore: Convert SentryFramesTrackingIntegration to Swift

[itaybre]

Converts SentryFramesTrackingIntegration to Swift as part of the Swift project

#skip-changelog

Closes #7066

[linear]

COCOA-999 Refactor `SentryFramesTrackingIntegration.m` in Swift

[itaybre]

Lint fails, and that's expected for now, enable ready-to-merge to run all tests

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.691%. Comparing base (8440c54) to head (fb98b73).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@              Coverage Diff              @@
##              main     #7044       +/-   ##
=============================================
- Coverage   84.710%   84.691%   -0.020%     
=============================================
  Files          459       459               
  Lines        27490     27482        -8     
  Branches     12117     12116        -1     
=============================================
- Hits         23287     23275       -12     
- Misses        4162      4166        +4     
  Partials        41        41               

Files with missing lines	Coverage Δ
Sources/Sentry/SentryBaseIntegration.m	83.908% <ø> (-3.248%)	⬇️
Sources/Sentry/SentrySDKInternal.m	84.518% <100.000%> (-0.065%)	⬇️
Sources/Swift/Core/Integrations/Integrations.swift	100.000% <100.000%> (ø)
...amesTracking/SentryFramesTrackingIntegration.swift	100.000% <100.000%> (ø)
Sources/Swift/SentryDependencyContainer.swift	98.275% <ø> (ø)

... and 5 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8440c54...fb98b73. Read the comment docs.

[github-actions]

Performance metrics 🚀

	Plain	With Sentry	Diff
Startup time	1212.21 ms	1242.60 ms	30.39 ms
Size	24.14 KiB	1.03 MiB	1.01 MiB

Baseline results on branch: main

Startup times

Revision	Plain	With Sentry	Diff
c6d2354	1226.53 ms	1252.69 ms	26.16 ms
feaf817	1217.00 ms	1244.92 ms	27.92 ms
51b7dd3	1235.06 ms	1258.21 ms	23.15 ms
543b791	1234.23 ms	1265.49 ms	31.26 ms
9766cb1	1233.54 ms	1267.65 ms	34.10 ms
397b9c9	1230.23 ms	1249.29 ms	19.06 ms
27e7514	1229.47 ms	1245.60 ms	16.13 ms
5cbd333	1219.93 ms	1241.76 ms	21.83 ms
67e2286	1217.83 ms	1250.04 ms	32.21 ms
fa27d5b	1195.50 ms	1218.19 ms	22.69 ms

App size

Revision	Plain	With Sentry	Diff
c6d2354	23.75 KiB	919.70 KiB	895.95 KiB
feaf817	24.14 KiB	1.03 MiB	1.01 MiB
51b7dd3	23.75 KiB	913.26 KiB	889.52 KiB
543b791	24.14 KiB	1.01 MiB	1010.98 KiB
9766cb1	23.75 KiB	1023.78 KiB	1000.03 KiB
397b9c9	23.75 KiB	959.44 KiB	935.70 KiB
27e7514	23.75 KiB	919.69 KiB	895.94 KiB
5cbd333	23.74 KiB	969.77 KiB	946.02 KiB
67e2286	24.14 KiB	1.02 MiB	1022.54 KiB
fa27d5b	24.14 KiB	1.01 MiB	1015.38 KiB

Previous results on branch: itay/cocoa-999-refactor-sentryframestrackingintegrationm-in-swift

Startup times

Revision	Plain	With Sentry	Diff
638b07b	1216.77 ms	1245.51 ms	28.74 ms
7c7d5e2	1224.90 ms	1255.13 ms	30.23 ms
9b8916c	1223.80 ms	1245.29 ms	21.49 ms

App size

Revision	Plain	With Sentry	Diff
638b07b	24.14 KiB	1.03 MiB	1.01 MiB
7c7d5e2	24.14 KiB	1.03 MiB	1.00 MiB
9b8916c	24.14 KiB	1.03 MiB	1.00 MiB

[philprime]

h: I don't understand where all of this logic comes from, can you please elaborate why the Swift version has much more logic here?

[itaybre]

Looks like I forgot to remove the old code.
But this is the code in SentryBaseIntegration: https://github.com/getsentry/sentry-cocoa/blob/main/Sources/Sentry/SentryBaseIntegration.m#L157
This is what determines if the integration is enabled or not

[cursor]

Integration order change breaks frames tracker dependency

The conversion moves SentryFramesTrackingIntegration from ObjC integrations to Swift integrations, which changes when it's installed. Previously it was installed early, before SentryWatchdogTerminationTrackingIntegration. Now Swift integrations are installed after all ObjC integrations, so the frames tracker starts after the watchdog termination integration. Since SentryANRTrackerV2 (used by watchdog tracking) depends on the frames tracker to compute frame delays, calling getFramesDelaySPI returns -1 when isRunning is false, causing ANR detection to skip frames-based analysis until the Swift integrations complete installation. The comment in the old code states "the watchdog tracker uses the frames tracker, so frame tracking must be enabled if watchdog tracking is enabled."

Additional Locations (1)

• Sources/Sentry/SentrySDKInternal.m#L514-L517

 

[itaybre]

Interesting, worth checking out