History prior to 3.7.0 is available in the per-package CHANGELOG files.
- #514
6517ec5Thanks @DanielPotorCK! - Allowios.extraSpmXcframeworksin brownfield config sopackage:ios --add-spm-packagecan include project-declared XCFrameworks as additional SPM binary targets.
-
Updated dependencies [
6517ec5]:- @callstack/brownfield-cli@6.2.0
-
Updated dependencies []:
- @callstack/react-native-brownfield@6.2.0
-
Updated dependencies [
a9726c1]:- @callstack/brownfield-cli@6.1.1
-
#519
a9726c1Thanks @RaphaelFakhri! -brownfield navigation:codegennow generatesNSNumberfor optionalnumberandbooleanmethod parameters on iOS. Previously, the generated Swift delegate usedDouble?andBool?, which can't be represented in an@objcprotocol, so the iOS build failed. -
Updated dependencies [
66ac701,5884ce9]:- @callstack/react-native-brownfield@6.1.1
-
#516
66ac701Thanks @malopezr7! - Android:ReactNativeBrownfield.initializecan now be called again after it throws. Before, a failure while loading native libraries or creating theReactHostleft it marked as initialized, so the next call returned without error andReactNativeBrownfield.sharedwas never set. -
#517
5884ce9Thanks @tlq5l! - Fix an iOS crash (std::bad_function_call) when native code posts a message to JS while the Brownfield module's JS emitter is still being set up. If the Brownfield module exists but its JS emitter is not ready when delivery happens, the message is dropped and a log line is written. If the module does not exist yet, the message is dropped without a log line.
-
#522
20776bbThanks @KisaneNeko! - feat: the published POM andmodule.jsonnow follow the brownfield module's Gradle exclude rules (configurations.all { exclude(...) }). Before, the plugin re-added an excluded dependency when it injected the embedded libraries' dependencies, so the host app still resolved it. The excludes are also written onto every dependency the plugin injects, so the excluded library can't arrive through one of them. On Expo, list them inandroid.excludeDependencies(asgroup:moduleorgroup), which the config plugin writes into the generated module. -
#520
b87cdffThanks @KisaneNeko! - fix: pick the right.sofiles for the Android AAR. WithuseStrippedSoFiles = false, the AAR now haslibappmodules.soandlibreact_codegen_*.so. Before this fix, those libs were missing and host apps crashed. The AAR also stops embedding the.sofiles of Maven dependencies. The host already gets those through the POM, so its build no longer fails with2 files found with path 'lib/<abi>/<name>.so'. If your app module builds or ships a.soof its own, list it inreactBrownfield.dynamicLibs, which is back. The build lists the.sofiles it left out in<brownfield module>/build/reports/brownfield/<variant>/skipped-so.txt. After upgrading, check that file: it lists the.sofiles that used to be in the AAR and now aren't.
-
Updated dependencies [
20776bb]:- @callstack/brownfield-cli@6.1.0
-
Updated dependencies [
520811c,f3dbbd1,b87cdff,20776bb,58aedad,6a258da]:- @callstack/react-native-brownfield@6.1.0
-
#512
520811cThanks @KisaneNeko! - fix: package classes from libraries' local jars (libs/*.jar) into the Android AAR; previously host apps crashed with NoClassDefFoundError. If your app also has those classes, because it added the jar itself as a workaround or depends on a library that the jar bundles, the build now fails with duplicate classes: remove the app's copy -
#513
f3dbbd1Thanks @KisaneNeko! - fix: keep the resources of every library embedded in the Android AAR; previously only one library'sres/valuessurvived and host apps failed at resource linking. As in a regular app, the module's ownresandresValues win over a library's, and when two libraries define the same resource the first one wins (previously the last one won for files such as drawables) -
#521
58aedadThanks @KisaneNeko! - fix: the AAR build no longer fails with duplicate resources when an embedded library ships the same drawables Metro generates for the app's bundle. Metro's copy wins. -
#503
6a258daThanks @RaphaelFakhri! -ReactNativeBrownfield.onMessageno longer calls the callback a second time, with the raw message text, when the callback throws. The error now propagates instead of being swallowed.
-
Updated dependencies [
79817d1,69fe3e3]:- @callstack/brownfield-cli@6.0.1
-
#487
79817d1Thanks @KisaneNeko! - Support Expo modules in React Native CLI apps.brownfield package:*no longer runsexpo prebuildon projects with committedandroid/andios/directories, which used to delete the brownfield library module. Prebuild now runs only when the native directory is missing or gitignored. If you commit the generated directories of an Expo app, runnpx expo prebuildyourself after changingapp.jsonor config plugins.create-react-native-brownfieldnow detects Expo and sets up the iOS framework to use the Expo runtime. On a re-run after adding Expo, it also raises an existing framework target to iOS 16.4.--use-prebuilt-exponow also turns Expo's precompiled modules on or off forpod install, and turns on Swift explicit modules so packaging works in projects that still carry the oldSWIFT_ENABLE_EXPLICIT_MODULES = NOworkaround. It defaults to building Expo from source when the app's React Native version doesn't match the one Expo's precompiled modules were built for.package:iosnow copies the expo-image dependency XCFrameworks (SDWebImage and libavif) as real files instead of symlinks intonode_modules, so the package works when moved to another machine. Re-runningcreate-react-native-brownfieldafterpod installno longer adds a second Sources build phase to the framework target, which made the nextpod installfail. Thepackage:iosscript thatcreate-react-native-brownfieldadds now passes--add-spm-package, so the iOS app adds one local Swift package instead of every XCFramework. Existing scripts aren't changed. -
#485
69fe3e3Thanks @hurali97! - respect--destinationinpackage:ioswhen merging XCFrameworks -
#508
7e63e20Thanks @malopezr7! - Fix an iOS crash with expo-updates 57 when updates are enabled. The Expo runtime no longer asks the Updates controller for its launch asset before the controller has started. -
#495
3b38aebThanks @hurali97! - fix: resolve the namespace from AndroidManifest.xmlpackagefor libraries without anamespacein build.gradle -
#500
0f62490Thanks @hurali97! - fix(android): stop the scaffoldedReactNativeHostManagerfrom loading React Native twice TheReactNativeHostManager.ktgenerated bynpm create @callstack/react-native-brownfieldfor React Native CLI projects calledloadReactNative(application)and thenReactNativeBrownfield.initialize(...). Both runDefaultNewArchitectureEntryPoint.load(), which overrides the React Native feature flags, so the app crashed on startup withFeature flags cannot be overridden more than once. The generated host manager now:- no longer calls
loadReactNative(ReactNativeBrownfield.initializealready loads the native libraries and feature flags exactly once); - passes the
ReactHostas a factory to the non-deprecatedinitializeoverload, so it is built afterSoLoader.initinstead of crashing withSoLoader.init() not yet called; - keeps the one behavior
loadReactNativeprovided on the side by flagging edge-to-edge whenIS_EDGE_TO_EDGE_ENABLEDis set. Fixes #492.
- no longer calls
- #494
d28810cThanks @hurali97! - Add Android startup, TTID/TTFD, and JS/UI responsiveness metrics. Android'sOnJSBundleLoadedcallback now receivesJSBundleTimingsinstead of a Boolean.
-
Updated dependencies []:
- @callstack/brownfield-cli@6.0.0
-
Updated dependencies [
d28810c]:- @callstack/react-native-brownfield@6.0.0
- #480
f17f556Thanks @gedu! - add @callstack/create-react-native-brownfield: scaffold Brownfield packaging targets in an existing React Native CLI project (npm create @callstack/react-native-brownfield), plus the@callstack/react-native-brownfield/scaffoldsubpath export it uses
-
Updated dependencies []:
- @callstack/brownfield-cli@5.3.0
-
Updated dependencies [
f17f556]:- @callstack/react-native-brownfield@5.3.0
-
Updated dependencies [
31c3939]:- @callstack/brownfield-cli@5.2.0
-
#477
9e57d43Thanks @KisaneNeko! - fix: publish dependencies of community libraries (e.g. react-native-screens, lottie-react-native) embedded in Expo brownfield AARs; the published POM now lists them, previously host apps could crash with NoClassDefFoundError
-
Updated dependencies []:
- @callstack/brownfield-cli@5.1.1
-
#458
bf976fdThanks @KisaneNeko! - Bump the Brownfield Gradle Plugin version injected by the Expo config plugin to2.0.0-alpha09. -
#462
2f7d5daThanks @likevy! - fixes #457, android back callbacks survived RN fragment view destruction, retaining delegates and intercepting back presses after re-entry -
#470
09162c2Thanks @KisaneNeko! - FixpopToNative()on iOS closing every React Native screen instead of only the topmost one.popToNative()is delivered as an app-wide notification, so every live React Native surface acted on it — including surfaces buried under other screens, and each surface acted twice when hosted by SwiftUI. In a stack such as RN → native → RN, a single call tore down the whole navigation stack, taking native screens with it. A React Native surface now acts only when it is the topmost one on screen, and only once per host. Two consequences worth knowing about:- When no React Native surface is on screen — for example one hidden behind a full-screen native modal —
popToNative()is now a no-op instead of popping the hidden screen. It logs when this happens. popToNative()no longer dismisses a modally presented native screen that merely contains a React Native surface. Only a surface that owns a navigation stack entry pops.
- When no React Native surface is on screen — for example one hidden behind a full-screen native modal —
- #450
4846a05Thanks @borisyankov! - AddpreloadBundletostartReactNativeon iOS. Without a preload,startReactNativeonly makes the factory, and React Native loads the JavaScript bundle when it creates the first React Native view.startReactNative(launchOptions:preloadBundle:onBundleLoaded:)moves that work to the app launch: the call starts the React Host, and React Native evaluates the bundle on the JavaScript thread, in parallel with the remainder of the app launch. On Android,ReactNativeBrownfield.initializedoes the same operation. This shape ofstartReactNativealso takes the launch options for the React Host.onBundleLoadednow runs on the main thread, and not on the JavaScript thread. A callback that you add after React Native loaded the bundle runs in the next turn of the main run loop.
-
Updated dependencies []:
- @callstack/brownfield-cli@5.1.0
-
#381
b8e8da5Thanks @alpharius-ck! - e2e tests for android
-
#449
83657e7Thanks @hurali97! - Fix npm publishing by upgrading to Changesets v3 (Yarn rewritesworkspace:ranges on publish) and correcting packagerepositorymetadata required for npm provenance. -
Updated dependencies [
83657e7]:- @callstack/brownfield-cli@5.0.2
-
Updated dependencies []:
- @callstack/brownfield-cli@5.0.1
-
#442
7898f8aThanks @janicduplessis! - feat: allow extending the list of .so files kept out of the AAR Adds areactBrownfield.ignoreEmbeddedLibsoption so a project can name additional native libraries that should not be embedded, next to the built-inIGNORE_EMBEDDED_LIBSlist.
-
Updated dependencies [
1183202]:- @callstack/brownfield-cli@5.0.0
-
#412
627fcbcThanks @Doko-Demo-Doa! - feat: add support for callback and promise to brownfield navigation -
#422
8894482Thanks @hurali97! - feat: support proguard/R8 minification
- Updated dependencies [
39cf6a7]:- @callstack/brownfield-cli@4.2.0
-
Updated dependencies [
dd1082a]:- @callstack/brownfield-cli@4.1.0
-
#417
28b534eThanks @hurali97! - fix: merge classes to contain third party libs classes
-
Updated dependencies [
dee9559]:- @callstack/brownfield-cli@4.0.0
-
#414
803f8caThanks @artus9033! - fix: duplicated JNI libs on cold publish
- Updated dependencies []:
- @callstack/brownfield-cli@3.15.0
- Updated dependencies [
10ff597]:- @callstack/brownfield-cli@3.14.0
-
Updated dependencies [
8e90842,3475c3d,4088c01]:- @callstack/brownfield-cli@3.13.2
-
#398
8e90842Thanks @artus9033! - feat: support brownfield unified config file in Expo -
#402
3475c3dThanks @artus9033! - feat: support local BGP in Expo config plugin -
#397
4088c01Thanks @artus9033! - fix: generate config schema with descriptions, add more descriptions -
#401
c4410f6Thanks @artus9033! - fix: brownfield Gradle Plugin not to depend on *UpdatesResources task from expo-updates if it is absent
-
Updated dependencies [
89bc23c]:- @callstack/brownfield-cli@3.13.1
-
#394
89bc23cThanks @Esemesek! - Fix schema.json not being released
-
#352
b451bb1Thanks @alpharius-ck! - e2e tests -
#339
ef835b5Thanks @Esemesek! - Added configuration file support for react-native-brownfield packages. -
#359
533569bThanks @MrMuzyk! - Expose the Brownfield Android Gradle Plugin source from the npm package for opt-in local patching.
-
Updated dependencies [
ef835b5]:- @callstack/brownfield-cli@3.13.0
-
#391
95dbb43Thanks @adamTrz! - Fix Expo iOS framework debug bundle packaging so Debug builds load from Metro when it is available and fall back to embedded bundles without dev-server-only runtime code.
- Updated dependencies []:
- @callstack/brownfield-cli@3.12.0
-
#358
3715ac7Thanks @adamTrz! - Add--add-spm-packagetobrownfield package:iosso packaging can also generate a local Swift Package Manager wrapper around the produced XCFrameworks, including a generatedPackage.swift,README.md, and Xcode integration instructions. Fail fast when Debug packaging cannot resolve the app framework name while local SPM output is requested. -
#364
05c557dThanks @hurali97! - keep only one reference of xcframeworks when spm enabled -
#317
c04301bThanks @adamTrz! - Add an opt-in iOS Debug mode for loading the embedded JavaScript bundle withpreferEmbeddedBundleInDebug, fixbundleURLOverridefallback behavior when the override returnsnil, and add native bundle-resolution tests.
-
Updated dependencies [
3715ac7,05c557d]:- @callstack/brownfield-cli@3.11.0
-
#353
7955c62Thanks @marcinszalski-callstack! - fix: call copyStrippedSoLibs once after the loop to avoid redundant SO file copying -
#361
aa14eb2Thanks @hurali97! - make EXUpdates as a dependency only when installed -
#347
c19a81bThanks @marcinszalski-callstack! - fix: fix method to deallocate reactNativeFactory instance for expo
- #323
3456d3aThanks @artus9033! - Support RN prebuilts in Brownfield, by default enabled in RN >= 0.84, opt-in in RN 0.83; or in Expo 55+ (Expo 54 is not supported). Add--use-prebuilt-rn-coretobrownfield package:iosso callers can opt into or out of React Native Apple prebuilt binaries; omitting the flag defers to version-aware defaults handled by Rock. The CLI rejects--use-prebuilt-rn-corewhen React Native is older than 0.81 or when the project is Expo SDK older than 55. Fix brownfield framework dylib install names to use @rpath instead of hardcoded paths.
-
Updated dependencies [
3456d3a]:- @callstack/brownfield-cli@3.10.0
-
#323
3456d3aThanks @artus9033! - ForceBUILD_LIBRARY_FOR_DISTRIBUTION/SWIFT_EMIT_MODULE_INTERFACEon the CocoaPods ReactBrownfield, Brownie and BrownfieldNavigation targets so Release builds emit.swiftinterfacefiles andxcodebuild -create-xcframework(brownfieldpackage:ios) can merge slices.
- #326
80e6364Thanks @artus9033! - feat: strip SO files by default, deprecate experimental option in favor of useStrippedSoFiles
- Updated dependencies [
80e6364]:- @callstack/brownfield-cli@3.9.0
-
#336
35b6f0aThanks @hurali97! - fix: allow unregistering the navigation delegate -
Updated dependencies [
e78084d]:- @callstack/brownfield-cli@3.8.1
-
#335
e78084dThanks @hurali97! - fix: Object params correctly reflect the generated native code instead of Any
- Updated dependencies [
d93dcd9]:- @callstack/brownfield-cli@3.8.0
- #313
c153378Thanks @alpharius-ck! - Jest unit tests
-
#322
cbc99cfThanks @marcinszalski-callstack! - fix: make sure android libs are loaded for expo apps -
Updated dependencies [
c153378]:- @callstack/brownfield-cli@3.7.0
-
#315
874332bThanks @marcinszalski-callstack! - fix: make sure native libs are loaded for RN >= 0.80