Skip to content

[Due for payment 2026-06-01] Add Sentry span for OpenApp/ReconnectApp network request on app startup #90671

Closed

Description

@mountiny

Problem

There is currently no Sentry performance span that measures the time from native app startup (before the JS runtime begins) through the completion of the initial network request on app startup (OpenApp or ReconnectApp).

With the introduction of react-native-nitro-fetch (see #88110) which prefetches the startup network request natively — before the JS bundle executes — we need telemetry that begins measuring from native startup time rather than from the JS bundle execution start. The existing span infrastructure only starts measuring after JS has started, which means it cannot capture the actual performance gain from native prefetching.

Solution

Add a dedicated Sentry span that:

  • Starts at the native app startup time, sourced from the AppStartTimeModule nitro module (before JS runtime initializes)
  • Ends when the initial OpenApp or ReconnectApp network request completes
  • Allows accurate measurement of the end-to-end startup network request latency, including the NitroFetch prefetch benefit

Related PR: #90667

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. melvin-bot commented on May 19, 2026

    @melvin-bot

    @chrispader Huh... This is 4 days overdue. Who can take care of this?

  2. melvin-bot commented on May 25, 2026

    @melvin-bot

    @mkhutornyi Eep! 4 days overdue now. Issues have feelings too...

  3. changed the title [-]Add Sentry span for OpenApp/ReconnectApp network request on app startup[/-] [+][Due for payment 2026-06-01] Add Sentry span for OpenApp/ReconnectApp network request on app startup[/+] on May 25, 2026
  4. melvin-bot commented on May 25, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.81-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-06-01. 🎊

    For reference, here are some details about the assignees on this issue:

    • @chrispader does not require payment (Contractor)
    • @mkhutornyi requires payment through NewDot Manual Requests
  5. mkhutornyi commented on May 26, 2026

    @mkhutornyi
    Contributor

    No need checklist

  6. melvin-bot commented on May 29, 2026

    @melvin-bot

    @mkhutornyi Whoops! This issue is 2 days overdue. Let's get this updated quick!

  7. melvin-bot commented on May 31, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  8. melvin-bot commented on May 31, 2026

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@mallenexpensify)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  9. mallenexpensify commented on Jun 1, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @mkhutornyi due $250 via NewDot

  10. trjExpensify commented on Jun 23, 2026

    @trjExpensify
    Contributor

    approved $250 for @mkhutornyi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2Task

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions