Report slow and frozen frames as span data too

[markushi]

Description

As of now slow and frozen frames are collected and attached to the root transaction. But for Mobile Vitals to work, the app start spans need to have the frame data set on the span data hash too.

Example span payload:

"spans": [
    {
      "timestamp": 1742508702.814,
      "start_timestamp": 1742508700.431,
      "op": "app.start.cold",
      "span_id": "42dbf44cc31249b4",
      "parent_span_id": "7168f0ee0fb14b00",
      "trace_id": "a8317f799fbb4d4e90103fc8dff13829",
      "status": "ok",
      "description": "Cold Start",
      "origin": "auto.ui.activity",
      "data": {
        "thread.name": "main",
        "thread.id": "13245",
        "frames.slow": 1, <<<
        "frames.frozen": 0, <<<
        "frames.total": 136, <<<
        "frames.delay": 0.131674152, <<<
      },

[krystofwoldrich]

Let's tackle this in multiple steps, based on the type of span (app start, ttid/ttfd, started thru API).

[antonis]

Let's tackle this in multiple steps, based on the type of span (app start, ttid/ttfd, started thru API).

Opened sub issues for the above

[kerenkhatiwada]

Related to Zendesk ticket #166337, is there an ETA for this fix?

[antonis]

Thank you for bumping this @kerenkhatiwada 🙇 I'm planning to resume this work next week and ship it with a new version by the end of the month.

[oferRounds]

Thank you @antonis, looking forward!