This is a companion piece to the article https://blog.expo.dev/developing-react-native-with-expo-and-flipper-8c426bdf995a in case you are running a managed build on EAS.
You'll need to add the expo config plugins to your dependencies: yarn add @expo/config-plugins
plugins.withDangerousMod
which means you will need to reverify this file with each expo SDK release. This is because we are modifying our Podfile directly and doing so requires certain strings to exist as reference points in the Expo template. That said, the worst that happens is that your app will not include Flipper.
If you'd like to create an /eas
directory and put flipper-expo.js
there, you can do that and update app.config.json
and the require for package.json
(Line 9 of flipper-expo.js
) accordingly.
- Reads your app's
Podfile
based on the EAS Managed Workflow template located at${config.modRequest.platformProjectRoot}/Podfile
- Verifies you've got flipper in your
package.json
& it's pinned to a specific version - Merges the
useFlipper!()
call into the podfile, using a version that matches the version specified in yourpackage.json
- Merges the
post_install
for Flipper into the post-install step of your Podfile
These techniques are based on the Google Maps Config Plugin which has to do similar modifications to the Podfile.