feat: Expo SDK 53 Upgrade

[frankcalise]

Description

• Upgrade the boilerplate to utilize Expo SDK 53 (start with npx expo install --fix)
• Change the new architecture to be default on at this point? I think we have enough client projects with it on
• Update documentation that mention Expo/RN Versions
• Review the Expo SDK 53 blog post for breaking changes and affected packages, config plugins and updates we need to make related to what is used in the boilerplate

Testing

• Run successfully on Android, iOS and Web
• Make sure the maestro test still works
• Confirm you can still write inline config plugins successfully

Notes

• A big help is spinning up a bare Expo SDK 53 app outside of Ignite and understanding it
• Look for places we can reduce complexity, code and config in the boilerplate - as things usually improve on this side with each SDK upgrade and it helps our maintenance cycle

[tuanlevi95]

seem expo 53 using latest react native 0.79, react 19, and got a lot of issues, related to axios

[frankcalise]

@tuanlevi95 yeah there is an open axios issue, however you can work around it with updating your metro.config.js resolvers like so:

config.resolver.unstable_conditionNames = ["require", "default", "browser"]

[ChristopherGabba]

@frankcalise

Somehow I a scrollable list screen using the <Screen /> component and after upgrading the app to Expo 53 / React Native 79.2 / React 19, I get this like 200 times:

 ERROR  Warning: Invalid prop `isParentDetached` supplied to `React.Fragment`. React.Fragment can only have `key` and `children` props.

  139 |
  140 | function ScreenWithoutScrolling(props: ScreenProps) {
> 141 |   const { style, contentContainerStyle, children } = props
      |                                                           ^
  142 |   return (
  143 |     <View style={[$outerStyle, style]}>
  144 |       <View style={[$innerStyle, contentContainerStyle]}>{children}</View>

 ERROR  Warning: Invalid prop `isParentDetached` supplied to `React.Fragment`. React.Fragment can only have `key` and `children` props.

  139 |
  140 | function ScreenWithoutScrolling(props: ScreenProps) {
> 141 |   const { style, contentContainerStyle, children } = props
      |                                                           ^
  142 |   return (
  143 |     <View style={[$outerStyle, style]}>
  144 |       <View style={[$innerStyle, contentContainerStyle]}>{children}</View>

So somehow the update doesn't like how this component is de-structuring props.

[ChristopherGabba]

Nevermind, Weirdly I just debugged this down to the Zeego Context Menu preview, so its actually not related to this component. No idea why react is throwing an error and implying its this component. Kind of strange.

[frankcalise]

Closed by #2948

[markrickert]

@frankcalise well... not really :P

That was a PR to @fpena's branch that's currently living in #2938. If you could look it over, that would be amazing!

[frankcalise]

@markrickert oh yeah ok, didn't see it was targeted against his original!

[fehmisener]

Any updates on this issue, when will the PR be merged?

[MedScribeIO]

The whole work is highly appreciated. We are well aware that the maintainers are doing this for free. Still, guys, for more than a month now, support for 53 couldn't be added. This is a bit strange. We are waiting for this, please.

[jamonholmgren]

Still, guys, for more than a month now, support for 53 couldn't be added. This is a bit strange. We are waiting for this, please.

Hey @MedScribeIO, thanks for using Ignite!

One thing you should know about Ignite is that we don't usually push out upgrades as soon as they happen. We often have to test on client projects and ensure that it works well and there aren't any issues. This often takes a month or more before it would land.

Of course, you could always help! Try spinning up a new app using 52, upgrade it manually to 53, and tell us if you run into any issues. It might help us test it in a more timely manner.

We also have a pretty big effort right now toward v11. That's the main focus. v11 will have some pretty big changes, such as removing MST entirely, new arch by default, and more.

Appreciate you being a part of our community!