Expo 52 and New Architecture 🎉

[JulienTexier]

✨ What has changed?

This PR updates Expo to SDK 52 and enables the New Architecture 🥳

Note

Linter and prettier has been removed at this point and will be added and improved in an upcoming PR.

With the upgrade comes many changes, including:

• Upgrade of many libraries
• Separation of configurations like lingui, figmage and prettier to their own files for easier maintenance
• Use of expo's drop_console instead of Babel plugin transform-remove-console
• Bottom Sheet component slightly improved (the playground was not working anymore with the latest version of the library)
• Playground utils file moved to components (it was wrongly in the app folder, so Expo Router considered it a route.
• NavigationThemeProvider using DefaultTheme to have default fonts if none are added to the project
• StatusBar moved to expo-status-bar
• i18n using expo-localization to get system locale
• Correct text example in store.config.json for English subtitle

Important

There is a known bug with the splashscreen at the moment (the icon is very small). It will be fixed at a later stage. We are monitoring this thread to know more about the issue.

[github-actions]

Hi! 👋

To ensure a smooth review process, it is recommended to trigger a build (or an update if no native changes have been made since the last build).

You can do so by applying the appropriate label based on your needs:

• 🏗️ 🍏 iOS Build: Select eas-build-ios:dev to trigger a build for iOS
• 🏗️ 🤖 Android Build: Select eas-build-android:dev to trigger a build for Android
• 🏗️ 📲 All Platforms Build: Select eas-build-all:dev to trigger builds for both platforms
• 🌐 EAS Update: Select eas-update to trigger an update (automatically for both platforms)

Note

The update is managed by a custom GitHub action, while the build actions are handled directly via EAS integration.

Once you apply the respective label, the appropriate workflow will be triggered automatically. You can monitor the progress in the Actions tab.

Warning

If you push new commits to your PR branch after selecting a build label, a new build will be triggered automatically.

It is advisable to remove the label once applied and reapply it if necessary; you will likely need to trigger an update instead of a fresh build.

Important

After merging changes into the dev branch, a build will automatically be triggered for both platform using the dev profile.

Therefore, there is no need to manually initiate a build after merging to the dev branch.

Additionally, builds will automatically trigger when promoting changes to test, stag, and prod.

For the prod branch, the build will also be automatically submitted to the app stores.

For more information, refer to the PR Reviews Guide.

[hugohutri]

[JulienTexier]

The package.json has it as 0.0.1 and I figured an app created from the template shouldn't start at 1.0.0.

Even React Native is still not there... 😀