major
semver matches the supported Expo SDK version. This helps spot inconsistencies between your Expo SDK and this plugin, as well as ensuring any changes to the upstream config-plugins system are properly addressed.
Project is now part of the official expo build-properties-plugin https://docs.expo.dev/versions/latest/sdk/build-properties/
- Improves failure message if running SDK 48 and the build-properties-plugin is available in the expo template
- Fixes issue where
Dev.Debug
was not a whitelisted metro configuration 45ed26d #49
- Added support for the default
NO_FLIPPER
emerging standard c6e0732 - Added support for all profiles, possibly related to a regression where react-native would attempt to bundle a non-linked flipper resulting in a symbole error
_OBJC_CLASS_$_FlipperClient
c6e0732
Release for compatibility with SDK 47.
- Added the ability to explicitly enable/disable flipper on a per platform level ref
- Added the ability to strip
use_frameworks
on iOS ref
- Adds all-contributors. Thank you to every single person who's helped make expo-community-flipper awesome ❤️
Migration If you were using individual pod specifications (folly, etc), you can remove all of that now. The Flipper team recommends using only the Flipper version, relying on the pod and maven to pull down the necessary dependencies.
- Fixes a breaking issue with Podfile generation introduced in react-native 0.69.2 ref
- Removes the legacy
use_flipper
declaration - Removes the
post_install
flipper code - Removes the
AppDelegate
code as the RCTAppSetupUtils already exist and this was redundant ref
- Removes the legacy
- Removes individual pod configs as those are no longer encouraged by the FB Flipper Team
- Removed old SDK tests
- Requires Expo SDK 46, which is now actively checked using
semver
against the config's SDK version. In React Native 0.68+, theAppDelegate
files are all objective-c++, and there is nowithAppDelegate
support for swift files. The Semver check avoids a footgun of running this plugin with SDK 45 and swiftAppDelegate
files and ending up with non-functional flipper.
Migration Please upgrade to the latest Expo SDK. expo-community-flipper
only maintains versions that are compatible with the supported Expo SDK versions.
- Modifies
AppDelegate.mm
to enableRCTAppSetupUtils
per flipper manual setup
- Upgrades Expo SDK requirement to 46
- Adds the ability to disable flipper via an ENV variable in EAS / Expo builds
FLIPPER_DISABLE
- Adds a post install step required by Flipper for native modules
- Revised version to match latest Expo SDK. No plugin API changes.
- Resolved idempotency issue with merging flipper into podfiles that contain a use-flipper directive ref
- (chore) Created an example application that can be used for future triage
- Revised version to match latest Expo SDK. No plugin API changes.
- Allows for specifying a universal flipper version as a string argument to the plugin
build/
directory is committed for transparency- Prevents footgun where you could specify Flipper's pods without specifying a Flipper version
- Adds support for specifying individual pod versions