Skip to content

[Due for payment 2025-07-22] [Due for payment 2025-07-15] Bump react-native-screens and react-navigation to newer versions #62850

Closed

Description

@mountiny

Problem

The react-navigation 6 we use right now utilises react-native-screens 3, which will be deprecated soon. We also have patches for react-navigation that could be removed by updating to version 7. This will reduce the maintenance overhead.

Solution

  • Update to react-navigation 7 which will require bumping the react-native-screens too
  • Remove App patches that are included in the react-navigation 7 updates
  • by updating to newer version we will move to use usePreventRemove instead of UNSTABLE_usePreventRemove - stable version coming in the new version
  • Investigate preloading to improve the perceived performance of the app
Issue OwnerCurrent Issue Owner: @abekkala

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on May 27, 2025
  2. melvin-bot commented on May 27, 2025

    @melvin-bot

    Triggered auto assignment to @abekkala (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.

  3. mountiny commented on May 27, 2025

    @mountiny
    ContributorAuthor

    @staszekscp Could you please list out the patches that can be removed

  4. changed the title [-]bump react-native-screens and react-navigation to newer versions[/-] [+]Bump react-native-screens and react-navigation to newer versions[/+] on May 27, 2025
  5. mountiny commented on May 27, 2025

    @mountiny
    ContributorAuthor

    I think we have some custom react- navigation changes we cannot easily remove but even if we can get rid of some of them its beneficial

  6. melvin-bot commented on Jun 2, 2025

    @melvin-bot

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

  7. mountiny commented on Jun 2, 2025

    @mountiny
    ContributorAuthor

    Full proposal will be posted later

  8. mountiny commented on Jun 2, 2025

    @mountiny
    ContributorAuthor

    Proposal posted here

  9. 56 remaining items

  10. abekkala commented on Jul 15, 2025

    @abekkala
    Contributor

    @allgandalf bumping this from above:

    it's unclear to me which PR is linked for this issue payout:
    I initially thought it was #65840 but that one is showing Vit as the Reviewer.

    Will be easiest if @allgandalf lists out the PRs please 🙇

  11. allgandalf commented on Jul 16, 2025

    @allgandalf
    Contributor

    No special regression tests here, regular regression testing should already be in place for this one!

  12. mountiny commented on Jul 16, 2025

    @mountiny
    ContributorAuthor

    $750 to @allgandalf

  13. abekkala commented on Jul 18, 2025

    @abekkala
    Contributor

    PAYMENT SUMMARY FOR JULY 22

  14. allgandalf commented on Jul 18, 2025

    @allgandalf
    Contributor

    Accepted 👍

  15. melvin-bot commented on Jul 21, 2025

    @melvin-bot

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

  16. melvin-bot commented on Jul 22, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @staszekscp is from an agency-contributor and not due payment
    • ROLE: @allgandalf paid $(AMOUNT) via Upwork (LINK)

    BugZero Checklist (@abekkala)

    • 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
  17. abekkala commented on Jul 23, 2025

    @abekkala
    Contributor

    @allgandalf payment sent and contract ended - thank you! 🎉

  18. melvin-bot commented on Oct 15, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

    If a regression has occurred and you are the assigned CM follow the instructions here.

    If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

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 productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions