Skip to content

[Due for payment 2026-07-21] Upgrade RN to 0.85 and Expo SDK 56 #91629

Description

@mountiny

Upgrade React Native (RN) to the Latest Version for Enhanced Performance and Compatibility

Background:

Over time, our codebase has grown to include numerous custom patches, and the open-source ecosystem around React Native continues to evolve with frequent updates, performance improvements, and new features. Third-party libraries often adapt quickly to these changes.

Problem:

Using an outdated React Native version complicates patch management, restricts compatibility with modern libraries, and negatively impacts app performance and stability.

Solution:

  • Upgrade React Native to 0.85 and Expo SDK 56
  • Audit and remove unnecessary patches
  • Conduct thorough testing for stability.
Issue OwnerCurrent Issue Owner: @jakubstec

Activity

  1. mountiny commented on May 25, 2026

    @mountiny
    ContributorAuthor

    @jakubstec Let's plan out how we will process this update, lets start with all the dependencies we can update in prs before the RN and Expo so we make sure the PRs are as small as possible

  2. jakubstec commented on May 27, 2026

    @jakubstec
    Member

    I'll catch up with @war-in and come up with a proper plan tomorrow! ☺️☺️

  3. jakubstec commented on May 29, 2026

    @jakubstec
    Member

    Okay so, I think we'll start with the patches, then I'll try to build a project locally with bumped RN and expo (with Upgrade helper), then I'll build on all the platforms and fix potential problems - then go through necessary dependencies that need to be updated and finally bump RN and expo (also remembering to simultaneously make prs to Mobile-Expensify)

    kudos to @war-in for already bumping react-native-live-markdown 🥳

    Also, I'll be OoO 01.06 - 05.06, so I'll work on it as soon as I'm back if that's okay! Meanwhile, Marcin will help me here when i'm away:)

  4. war-in commented on Jun 1, 2026

    @war-in
    Contributor

    From @jakubstec's investigation, looks like we have to upgrade react-native-reanimated and react-native-worklets before the main React Native bump PR. I'll prepare a PR soon.

    @mountiny can I get the issue for it? 🙏

  5. 60 remaining items

  6. parasharrajat commented on Jul 20, 2026

    @parasharrajat
    Member

    Not yet @mountiny

  7. melvin-bot commented on Jul 23, 2026

    @melvin-bot

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

  8. melvin-bot commented on Jul 24, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  9. mountiny commented on Jul 24, 2026

    @mountiny
    ContributorAuthor

    There was not that many back and forths on the main PR so I would suggest $500 for testing on that PR

  10. melvin-bot commented on Jul 24, 2026

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  11. mallenexpensify commented on Jul 24, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @parasharrajat due $500 via NewDot

  12. moved this from AWAITING DEPLOYMENT to Done in [#whatsnext] #qualityon Jul 24, 2026
  13. garrettmknight commented on Sep 18, 2026

    @garrettmknight
    Contributor

    $500 approved for @parasharrajat

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 productionDailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staffTask

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions