In these situations, developers have to quickly gain knowledge about other OS’s specifics or ask their colleagues for help. When you want to build a mobile app for both iOS and Android it is ideal to have at least one person in a team with knowledge about each platform, but it is not always possible. During this time we’ve worked on several projects that had teams build up from developers with different backgrounds: native or frontend. Invoking the React Native Codegen if a library or app is using the Codegen for the New Architecture.For the last year, we’ve been using React Native more and more.Setting up the Metro DevServer Port as an Android resource so the app knows on which port to connect.Setting up the buildConfigFields so that you can know at runtime if Hermes or the New Architecture are enabled.Setting up the NDK to let you build apps that are using the New Architecture.Setting up the proper Maven repositories (Maven Central, Google Maven Repo, JSC local Maven repo, etc.) needed to consume all the necessary Maven Dependencies.Setting up the proper version of the :react-android and :hermes-android dependency, reading the React Native version from the package.json of react-native.Add a createBundleJsAndAssets task for every non debuggable variant, that is responsible of invoking the bundle, hermesc and compose-source-map commands.Here is a summary of the plugin responsibilities: The plugin is also used inside 3rd party libraries, to run the Codegen used for the New Architecture. The React Native Gradle Plugin is responsible for configuring your Application build to ship React Native applications to production. What is the plugin doing under the hood? For example, if you list fullStaging in the debuggableVariants, you won't be able to publish it to a store as it will be missing the bundle. This is necessary because the plugin will skip the JS bundling for all the debuggableVariants: you'll need Metro to run them.

React native gradle version