Skip to content

Latest commit

 

History

History
399 lines (226 loc) · 34.4 KB

CHANGELOG.md

File metadata and controls

399 lines (226 loc) · 34.4 KB

Changelog

History prior to 3.7.0 is available in the per-package CHANGELOG files.

6.2.0

Minor Changes

  • #514 6517ec5 Thanks @DanielPotorCK! - Allow ios.extraSpmXcframeworks in brownfield config so package:ios --add-spm-package can include project-declared XCFrameworks as additional SPM binary targets.

Patch Changes

  • Updated dependencies [6517ec5]:

    • @callstack/brownfield-cli@6.2.0
  • Updated dependencies []:

    • @callstack/react-native-brownfield@6.2.0

6.1.1

Patch Changes

  • Updated dependencies [a9726c1]:

    • @callstack/brownfield-cli@6.1.1
  • #519 a9726c1 Thanks @RaphaelFakhri! - brownfield navigation:codegen now generates NSNumber for optional number and boolean method parameters on iOS. Previously, the generated Swift delegate used Double? and Bool?, which can't be represented in an @objc protocol, so the iOS build failed.

  • Updated dependencies [66ac701, 5884ce9]:

    • @callstack/react-native-brownfield@6.1.1
  • #516 66ac701 Thanks @malopezr7! - Android: ReactNativeBrownfield.initialize can now be called again after it throws. Before, a failure while loading native libraries or creating the ReactHost left it marked as initialized, so the next call returned without error and ReactNativeBrownfield.shared was never set.

  • #517 5884ce9 Thanks @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.

6.1.0

Minor Changes

  • #522 20776bb Thanks @KisaneNeko! - feat: the published POM and module.json now 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 in android.excludeDependencies (as group:module or group), which the config plugin writes into the generated module.

  • #520 b87cdff Thanks @KisaneNeko! - fix: pick the right .so files for the Android AAR. With useStrippedSoFiles = false, the AAR now has libappmodules.so and libreact_codegen_*.so. Before this fix, those libs were missing and host apps crashed. The AAR also stops embedding the .so files of Maven dependencies. The host already gets those through the POM, so its build no longer fails with 2 files found with path 'lib/<abi>/<name>.so'. If your app module builds or ships a .so of its own, list it in reactBrownfield.dynamicLibs, which is back. The build lists the .so files it left out in <brownfield module>/build/reports/brownfield/<variant>/skipped-so.txt. After upgrading, check that file: it lists the .so files that used to be in the AAR and now aren't.

Patch Changes

  • 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 520811c Thanks @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 f3dbbd1 Thanks @KisaneNeko! - fix: keep the resources of every library embedded in the Android AAR; previously only one library's res/values survived and host apps failed at resource linking. As in a regular app, the module's own res and resValues 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 58aedad Thanks @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 6a258da Thanks @RaphaelFakhri! - ReactNativeBrownfield.onMessage no longer calls the callback a second time, with the raw message text, when the callback throws. The error now propagates instead of being swallowed.

6.0.1

Patch Changes

  • Updated dependencies [79817d1, 69fe3e3]:

    • @callstack/brownfield-cli@6.0.1
  • #487 79817d1 Thanks @KisaneNeko! - Support Expo modules in React Native CLI apps. brownfield package:* no longer runs expo prebuild on projects with committed android/ and ios/ 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, run npx expo prebuild yourself after changing app.json or config plugins. create-react-native-brownfield now 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-expo now also turns Expo's precompiled modules on or off for pod install, and turns on Swift explicit modules so packaging works in projects that still carry the old SWIFT_ENABLE_EXPLICIT_MODULES = NO workaround. 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:ios now copies the expo-image dependency XCFrameworks (SDWebImage and libavif) as real files instead of symlinks into node_modules, so the package works when moved to another machine. Re-running create-react-native-brownfield after pod install no longer adds a second Sources build phase to the framework target, which made the next pod install fail. The package:ios script that create-react-native-brownfield adds now passes --add-spm-package, so the iOS app adds one local Swift package instead of every XCFramework. Existing scripts aren't changed.

  • #485 69fe3e3 Thanks @hurali97! - respect --destination in package:ios when merging XCFrameworks

  • #508 7e63e20 Thanks @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 3b38aeb Thanks @hurali97! - fix: resolve the namespace from AndroidManifest.xml package for libraries without a namespace in build.gradle

  • #500 0f62490 Thanks @hurali97! - fix(android): stop the scaffolded ReactNativeHostManager from loading React Native twice The ReactNativeHostManager.kt generated by npm create @callstack/react-native-brownfield for React Native CLI projects called loadReactNative(application) and then ReactNativeBrownfield.initialize(...). Both run DefaultNewArchitectureEntryPoint.load(), which overrides the React Native feature flags, so the app crashed on startup with Feature flags cannot be overridden more than once. The generated host manager now:

    • no longer calls loadReactNative (ReactNativeBrownfield.initialize already loads the native libraries and feature flags exactly once);
    • passes the ReactHost as a factory to the non-deprecated initialize overload, so it is built after SoLoader.init instead of crashing with SoLoader.init() not yet called;
    • keeps the one behavior loadReactNative provided on the side by flagging edge-to-edge when IS_EDGE_TO_EDGE_ENABLED is set. Fixes #492.

6.0.0

Major Changes

  • #494 d28810c Thanks @hurali97! - Add Android startup, TTID/TTFD, and JS/UI responsiveness metrics. Android's OnJSBundleLoaded callback now receives JSBundleTimings instead of a Boolean.

Patch Changes

  • Updated dependencies []:

    • @callstack/brownfield-cli@6.0.0
  • Updated dependencies [d28810c]:

    • @callstack/react-native-brownfield@6.0.0

5.3.0

Minor Changes

  • #480 f17f556 Thanks @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/scaffold subpath export it uses

Patch Changes

  • Updated dependencies []:

    • @callstack/brownfield-cli@5.3.0
  • Updated dependencies [f17f556]:

    • @callstack/react-native-brownfield@5.3.0

5.2.0

Minor Changes

Patch Changes

  • Updated dependencies [31c3939]:

    • @callstack/brownfield-cli@5.2.0
  • #477 9e57d43 Thanks @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

5.1.1

Patch Changes

  • Updated dependencies []:

    • @callstack/brownfield-cli@5.1.1
  • #458 bf976fd Thanks @KisaneNeko! - Bump the Brownfield Gradle Plugin version injected by the Expo config plugin to 2.0.0-alpha09.

  • #462 2f7d5da Thanks @likevy! - fixes #457, android back callbacks survived RN fragment view destruction, retaining delegates and intercepting back presses after re-entry

  • #470 09162c2 Thanks @KisaneNeko! - Fix popToNative() 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.

5.1.0

Minor Changes

  • #450 4846a05 Thanks @borisyankov! - Add preloadBundle to startReactNative on iOS. Without a preload, startReactNative only 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.initialize does the same operation. This shape of startReactNative also takes the launch options for the React Host. onBundleLoaded now 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.

Patch Changes

5.0.2

Patch Changes

  • #449 83657e7 Thanks @hurali97! - Fix npm publishing by upgrading to Changesets v3 (Yarn rewrites workspace: ranges on publish) and correcting package repository metadata required for npm provenance.

  • Updated dependencies [83657e7]:

    • @callstack/brownfield-cli@5.0.2

5.0.1

Patch Changes

  • Updated dependencies []:

    • @callstack/brownfield-cli@5.0.1
  • #442 7898f8a Thanks @janicduplessis! - feat: allow extending the list of .so files kept out of the AAR Adds a reactBrownfield.ignoreEmbeddedLibs option so a project can name additional native libraries that should not be embedded, next to the built-in IGNORE_EMBEDDED_LIBS list.

5.0.0

Major Changes

Patch Changes

4.3.0

Minor Changes

Patch Changes

  • Updated dependencies [627fcbc, 8894482]:
    • @callstack/brownfield-cli@4.3.0

4.2.0

Minor Changes

Patch Changes

  • Updated dependencies [39cf6a7]:
    • @callstack/brownfield-cli@4.2.0

4.1.0

Minor Changes

Patch Changes

  • Updated dependencies [dd1082a]:

    • @callstack/brownfield-cli@4.1.0
  • #417 28b534e Thanks @hurali97! - fix: merge classes to contain third party libs classes

4.0.0

Major Changes

Patch Changes

  • Updated dependencies [dee9559]:

    • @callstack/brownfield-cli@4.0.0
  • #414 803f8ca Thanks @artus9033! - fix: duplicated JNI libs on cold publish

3.15.0

Minor Changes

Patch Changes

  • Updated dependencies []:
    • @callstack/brownfield-cli@3.15.0

3.14.0

Minor Changes

Patch Changes

  • Updated dependencies [10ff597]:
    • @callstack/brownfield-cli@3.14.0

3.13.2

Patch Changes

3.13.1

Patch Changes

3.13.0

Minor Changes

Patch Changes

  • Updated dependencies [ef835b5]:

    • @callstack/brownfield-cli@3.13.0
  • #391 95dbb43 Thanks @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.

3.12.0

Minor Changes

Patch Changes

  • Updated dependencies []:
    • @callstack/brownfield-cli@3.12.0

3.11.0

Minor Changes

  • #358 3715ac7 Thanks @adamTrz! - Add --add-spm-package to brownfield package:ios so packaging can also generate a local Swift Package Manager wrapper around the produced XCFrameworks, including a generated Package.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 05c557d Thanks @hurali97! - keep only one reference of xcframeworks when spm enabled

  • #317 c04301b Thanks @adamTrz! - Add an opt-in iOS Debug mode for loading the embedded JavaScript bundle with preferEmbeddedBundleInDebug, fix bundleURLOverride fallback behavior when the override returns nil, and add native bundle-resolution tests.

Patch Changes

3.10.0

Minor Changes

  • #323 3456d3a Thanks @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-core to brownfield package:ios so 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-core when 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.

Patch Changes

  • Updated dependencies [3456d3a]:

    • @callstack/brownfield-cli@3.10.0
  • #323 3456d3a Thanks @artus9033! - Force BUILD_LIBRARY_FOR_DISTRIBUTION / SWIFT_EMIT_MODULE_INTERFACE on the CocoaPods ReactBrownfield, Brownie and BrownfieldNavigation targets so Release builds emit .swiftinterface files and xcodebuild -create-xcframework (brownfield package:ios) can merge slices.

3.9.0

Minor Changes

  • #326 80e6364 Thanks @artus9033! - feat: strip SO files by default, deprecate experimental option in favor of useStrippedSoFiles

Patch Changes

  • Updated dependencies [80e6364]:
    • @callstack/brownfield-cli@3.9.0

3.8.1

Patch Changes

  • #336 35b6f0a Thanks @hurali97! - fix: allow unregistering the navigation delegate

  • Updated dependencies [e78084d]:

    • @callstack/brownfield-cli@3.8.1
  • #335 e78084d Thanks @hurali97! - fix: Object params correctly reflect the generated native code instead of Any

3.8.0

Minor Changes

Patch Changes

  • Updated dependencies [d93dcd9]:
    • @callstack/brownfield-cli@3.8.0

3.7.0

Minor Changes

Patch Changes