Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flipper Support in Expo SDK 48+ #54

Closed
jakobo opened this issue Mar 1, 2023 · 0 comments
Closed

Flipper Support in Expo SDK 48+ #54

jakobo opened this issue Mar 1, 2023 · 0 comments
Labels
has workaround Has a workaround, please read through thread SDK 48 Affects plugin in Expo SDK 48 upstream expo Upstream issue with expo (check linked issues)

Comments

@jakobo
Copy link
Owner

jakobo commented Mar 1, 2023

🎉 It's happened! Flipper support is now a natural part of your expo build via the official build-properties plugin.

How to Use

Build Properties Plugin docs

In your app.config.js:

import { withPlugins } from 'expo/config-plugins';
import { withBuildProperties } from 'expo-build-properties';

/*
$ANDROID_FLIPPER (string) - Flipper is always enabled in Android. If you're
using a specific version of react-native-flipper, you can specify the matching
semver string here. During the gradle build, react-native will select the correct
library versions.

$IOS_FLIPPER (boolean | string) - Flipper is disabled by default in iOS because
it's highly likely you are using Firebase or another podfile that enables the
use_frameworks directive. You can opt into flipper on iOS one of two ways:
- `true` will use the version of Flipper bundled with your current react-native version
  great for layout debugging, performance checks, etc
- A semver string matching the `react-native-flipper` in your `package.json`. This
  is needed if you are using flipper plugins, which need to talk to Flipper via the
  JS bridge API. Flipper moves fast, and ensuring your versions match is critical
  to having the iOS device properly show up in the debugger.

Finally, be sure to check the Flipper GitHub if you're using a non-standard flipper
verison, as the latest flipper is not always the most stable.
*/

export default withPlugins(config, [
  [withBuildProperties, {
    "android": {
      "flipper" : $ANDROID_FLIPPER
    },
    "ios": {
      "flipper": $IOS_FLIPPER
    }
  }]
]);

Getting Help

The best way to get help is to check the expo tracker for an issue and open an issue if needed. Myself, other contributors to expo-community-flipper, Kudo (expo team) and others are there and want to help you succeed.

Closing

I want to thank every single contributor to expo-community-flipper. Those who filed bugs, helped answer questions, waited on and reported eas build results, and generally made expo better; you all made this library an absolute joy to work on. I hope to avoid looking at a Podfile for a little bit. ❤️

@jakobo jakobo added has workaround Has a workaround, please read through thread upstream expo Upstream issue with expo (check linked issues) SDK 48 Affects plugin in Expo SDK 48 labels Mar 1, 2023
Repository owner locked as resolved and limited conversation to collaborators Mar 1, 2023
@jakobo jakobo pinned this issue Mar 1, 2023
@jakobo jakobo closed this as completed Mar 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
has workaround Has a workaround, please read through thread SDK 48 Affects plugin in Expo SDK 48 upstream expo Upstream issue with expo (check linked issues)
Projects
None yet
Development

No branches or pull requests

1 participant