Skip to content

[Due for payment 2026-03-11] Start Sentry in spans in native code #82974

Closed

Description

@roryabraham

Problem

When a user opens the app, if Sentry spans don't start until JS is loaded, then we don't have visibility into how long it took the native code to initialize.

Solution

Start Sentry from native.

Issue OwnerCurrent Issue Owner: @abdulrahuman5196

Activity

  1. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Feb 19, 2026
  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Feb 19, 2026
  3. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 19, 2026
  4. melvin-bot commented on Feb 19, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @jayeshmangwani (External)

  5. melvin-bot commented on Feb 19, 2026

    @melvin-bot

    Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  6. melvin-bot commented on Feb 19, 2026

    @melvin-bot

    Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.

  7. 23 remaining items

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Mar 4, 2026
  9. changed the title [-]Start Sentry in spans in native code[/-] [+][Due for payment 2026-03-11] Start Sentry in spans in native code[/+] on Mar 4, 2026
  10. melvin-bot commented on Mar 4, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  11. melvin-bot commented on Mar 4, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.30-3 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-03-11. 🎊

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

  12. melvin-bot commented on Mar 4, 2026

    @melvin-bot

    @abdulrahuman5196 The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  13. abdulrahuman5196 commented on Mar 4, 2026

    @abdulrahuman5196
    Contributor

    @roryabraham i didn't review the PR could you remove me from this issue?

  14. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Mar 4, 2026
  15. roryabraham commented on Mar 7, 2026

    @roryabraham
    ContributorAuthor

    This is done

  16. removed
    Awaiting PaymentAuto-added when associated PR is deployed to production
    on Mar 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.ExternalAdded to denote the issue can be worked on by a contributorWeeklyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions