Sanniv Khare 9 min read

React Native 0.89 readiness: 30 libraries checked before release

React Native 0.89 readiness: 30 libraries checked before release

Short version: of 30 widely used React Native libraries, 29 have nothing in their native code that breaks against React Native 0.89, and every peer range on npm accepts 0.89.0 final. The one to act on is @notifee/react-native 9.1.8: its Android headless task finds out whether the app is bridgeless by calling DefaultNewArchitectureEntryPoint.getBridgelessEnabled() through reflection, and 0.89 deletes that getter. On 0.89 the check returns false, and the fallback path asks for a ReactNativeHost that a 0.89 app does not have. Reading the source, that affects both foreground and background notification events on Android, so plan the change before you bump.

We checked the latest npm version of each library on 20 November 2026 against react-native 0.88.1 and 0.89.0-rc.2. React Native’s release overview lists 0.89.0 for 7 December 2026.

Why we did this: our banking apps and TV apps run React Native 0.88.1 and share most of this dependency list, so the “does X support 0.89” question lands on our desk the day 0.89.0 ships. This post is a source and metadata check; it makes no build or runtime claims.

How we checked

Three steps, all on our Linux test server with Node 24 and npm.

  1. What 0.89 removes. We unpacked the npm tarballs of react-native 0.88.1 and 0.89.0-rc.2 and listed the headers, Kotlin and Java files that exist only in 0.88.1: 15 files. We added the members our 0.89 RC overview and rc.2 native diff found removed (the fabricEnabled, turboModulesEnabled and bridgelessEnabled flags on both platforms).
  2. What each library declares. npm view for the latest version, its publish date, any newer next or beta tag, and its react-native peer range.
  3. What each library compiles against. npm pack of the latest version (and of the newer prerelease where one exists), then a scan of every .h, .mm, .cpp, .kt, .java, podspec and Gradle file for the removed APIs, outside example/ and test folders.
npm pack react-native@0.88.1 react-native@0.89.0-rc.2
mkdir a b
tar xzf react-native-0.88.1.tgz -C a --strip-components=1
tar xzf react-native-0.89.0-rc.2.tgz -C b --strip-components=1
(cd a; find . -name '*.h' -o -name '*.kt' -o -name '*.java' | sort) > fa
(cd b; find . -name '*.h' -o -name '*.kt' -o -name '*.java' | sort) > fb
comm -23 fa fb    # 15 files exist only in 0.88.1

What React Native 0.89 removes from native code

The ones a library is likely to touch:

  • iOS: RCTModuleData.h, RCTCxxBridgeDelegate.h, RCTBridge+Inspector.h, the old RCTNativeAnimatedModule.h, and React/Profiler/RCTProfile.h with RCTMacros.h. RCTRootViewFactoryConfiguration loses bridgelessEnabled and turboModuleEnabled.
  • Shared C++: react/renderer/graphics/Geometry.h and react/renderer/graphics/conversions.h. Both carried a deprecation #warning in 0.88.1; the replacements are the specific headers (Float.h, Rect.h and so on), the new umbrella <React/Graphics.h>, and react/renderer/core/graphicsConversions.h.
  • Android: the fabricEnabled, turboModulesEnabled, bridgelessEnabled, concurrentReactEnabled and isConfigurationValid members of DefaultNewArchitectureEntryPoint, the legacy TimingModule, and PullTransactionMountItem. CoreComponentsRegistry.h moves from jni/react/fabric/ to jni/react/newarchdefaults/.

One more change is a deprecation, not a removal: JavaTurboModule::invokeJavaMethod gains an overload without the cachedMethodID argument, and the old one is marked [[deprecated]] with a comment that the ID is “neither read nor written”. Code generated by older codegen still compiles, with warnings.

The scan

The checker is a short Python script: a table of regular expressions and a walk over each unpacked package. It also marks a hit as “guarded” when an #if, __has_include or try sits in the three lines above it, which separates code that already handles both versions from code that does not. The core of it, to adapt:

REMOVED = {
  "RCTModuleData.h": r'RCTModuleData\.h|\bRCTModuleData\b',
  "RCTCxxBridgeDelegate.h": r'RCTCxxBridgeDelegate',
  "RCTBridge+Inspector.h": r'RCTBridge\+Inspector',
  "RCTNativeAnimatedModule.h": r'RCTNativeAnimatedModule\.h',
  "RCTProfile.h / RCTMacros.h": r'RCTProfile\.h|RCTMacros\.h',
  "graphics/Geometry.h": r'renderer/graphics/Geometry\.h',
  "graphics/conversions.h": r'renderer/graphics/conversions\.h',
  "bridgeless/turbo flags": r'\b(bridgelessEnabled|turboModuleEnabled)\b',
  "entry point flags": r'DefaultNewArchitectureEntryPoint\.'
      r'(fabricEnabled|turboModulesEnabled|bridgelessEnabled)',
  "TimingModule": r'modules\.core\.TimingModule\b',
  "CoreComponentsRegistry.h": r'CoreComponentsRegistry\.h',
}
DEPRECATED = {"invokeJavaMethod(cachedMethodID)":
              r'invokeJavaMethod\(.*cachedMethodI[dD]'}
EXT = ('.h', '.mm', '.m', '.cpp', '.swift', '.kt', '.java',
       '.podspec', '.rb', '.gradle', '.kts')
Terminal output: hits per package from the 0.89 scan

Hits per package from our scan of 30 libraries against React Native 0.89.0-rc.2.

Seven packages had hits. Each one needed reading, because a regular expression cannot tell a broken include from a handled one.

The 30 libraries

Package, latest (published) Peer range Verdict
react-native-screens 4.30.1 (2026-10-28, next 5.0.0-beta.1) * Silent, nothing removed found
react-native-safe-area-context 5.11.1 (2026-11-03) * Silent, nothing removed found
react-native-reanimated 4.8.0 (2026-11-19) 0.87 - 0.89 Declares 0.89
react-native-worklets 0.14.0 (2026-11-19) 0.87 - 0.89 Declares 0.89
react-native-gesture-handler 3.5.0 (2026-11-05) * Silent, nothing removed found
react-native-svg 15.16.1 (2026-11-05) * Ready: has 0.89 #if paths
react-native-webview 14.0.1 (2026-06-20, next 17.1.0) * Silent, nothing removed found
@react-native-async-storage/async-storage 3.1.1 (2026-05-29) * Silent, nothing removed found
react-native-mmkv 4.3.2 (2026-06-22) * Silent, nothing removed found
@shopify/flash-list 2.3.3 (2026-10-01) * No native code
@react-native-firebase/app 27.1.1 (2026-11-10) >=0.60.0-0 OK, deprecation warnings
react-native-vision-camera 5.2.4 (2026-10-29) * OK: header moved, still exported
react-native-keyboard-controller 1.23.1 (2026-11-16) * Silent, nothing removed found
react-native-pager-view 10.0.3 (2026-11-16) * Silent, nothing removed found
react-native-maps 1.29.11 (2026-09-27) >= 0.76.0 OK, deprecation warnings
react-native-permissions 5.6.3 (2026-10-16) * Silent, nothing removed found
@sentry/react-native 8.36.0 (2026-11-17) >=0.65.0 Silent, nothing removed found
lottie-react-native 7.5.1 (2026-11-13) >=0.84 Silent, nothing removed found
react-native-nitro-modules 0.37.2 (2026-11-03) * Silent, nothing removed found
expo-modules-core 58.1.0 (2026-11-11) * OK: header moved, still exported
react-native-device-info 15.0.2 (2026-02-21) * Silent, nothing removed found
react-native-image-picker 8.3.0 (2026-10-13) * Silent, nothing removed found
@react-native-community/netinfo 12.0.1 (2026-02-14) >=0.59 Silent, nothing removed found
react-native-video 6.19.3 (2026-09-18, next 7.0.0-beta.13) * Silent, nothing removed found
react-native-keychain 11.0.0 (2026-11-06) >=0.82.0 Silent, nothing removed found
react-native-blob-util 1.1.1 (2026-11-09) >=0.84.0 Silent, nothing removed found
@react-native-community/datetimepicker 9.3.0 (2026-11-05) * Ready: uses the new umbrella header
react-native-linear-gradient 2.8.3 (2023-09-06, next 3.0.0-beta.2) * Silent, nothing removed found
@notifee/react-native 9.1.8 (2024-12-20) * Blocks background events (Android, by source)
react-native-share 12.3.1 (2026-05-04) (none) Silent, nothing removed found

“Silent” means the peer range does not name 0.89 and the native sources contain none of the removed APIs we searched for. It does not mean the maintainers tested 0.89; only Reanimated and Worklets say so in their ranges (we covered that release in Reanimated 4.7 to 4.8). Every range in the table accepts 0.89.0 final under npm’s semver rules.

Notifee: the one that breaks

@notifee/react-native 9.1.8, published 20 December 2024 and still the latest on npm, decides how to reach React in a background (headless) task with this method in HeadlessTask.java:

public static boolean isBridgelessArchitectureEnabled() {
  try {
    Class<?> entryPoint = Class.forName(
        "com.facebook.react.defaults.DefaultNewArchitectureEntryPoint");
    Method bridgelessEnabled = entryPoint.getMethod("getBridgelessEnabled");
    Object result = bridgelessEnabled.invoke(null);
    return (result == Boolean.TRUE);
  } catch (Exception e) {
    return false;
  }
}

In 0.88.1, bridgelessEnabled is a @JvmStatic property, so getBridgelessEnabled() exists as a static method and the call returns true. In 0.89.0-rc.2 the object keeps only releaseLevel and load(), so getMethod throws NoSuchMethodException, the catch swallows it, and the method returns false.

Before and after: DefaultNewArchitectureEntryPoint in 0.88.1 and 0.89.0-rc.2

DefaultNewArchitectureEntryPoint in 0.88.1 and 0.89.0-rc.2: the getter Notifee reflects on is gone.

False sends getReactContext() down the old-architecture path: getReactNativeHost(context).getReactInstanceManager(). The 0.89 community template’s MainApplication overrides only reactHost, and the default reactNativeHost getter in ReactApplication throws RuntimeException("You should not use ReactNativeHost directly in the New Architecture"). Reading the source, that exception is not caught on this path. Two callers reach this code, and they end differently:

  • Background events (isAppInForeground() false) go through startHeadlessTask to createReactContextAndScheduleTask, which calls getReactContext() with no try around it. Reading the source, the exception escapes, so the event should never reach your onBackgroundEvent handler.
  • Foreground events go through NotifeeReactUtils.sendEvent, which wraps the same call in try and logs the exception under the SEND_EVENT tag. By the source, a press or dismiss in the foreground is dropped with a log line instead of a crash.

That is a trace through the source of 9.1.8 and 0.89.0-rc.2; confirm it on a test device with one foreground and one background notification before you decide.

Your options, smallest first:

  • Patch the check. On 0.89 every app is bridgeless, so the method can return true when the getter is missing. A sketch for patch-package; adapt it and keep the original for older React Native versions:
} catch (NoSuchMethodException e) {
  // React Native 0.89 removed the getter: bridgeless is the only mode
  return true;
} catch (Exception e) {
  return false;
}
  • Move to a maintained fork that already targets bridgeless only. Check its Android headless code for the same reflection before you switch.
  • Stay on 0.88 until the notifications path is settled, if notification events are central to your app.

The hits that turned out fine

  • expo-modules-core 58.1.0 includes <CoreComponentsRegistry.h> and react-native-vision-camera 5.2.4 (in its generated Nitro code) includes <react/fabric/CoreComponentsRegistry.h>. The header moved to newarchdefaults/, but 0.89’s ReactAndroid/build.gradle.kts exports that folder at the include root and adds an explicit entry that also exports the moved file under react/fabric/. Both include paths keep resolving through the prefab package.
  • @react-native-community/datetimepicker 9.3.0 includes Geometry.h only in the #else branch of #if __has_include(<React/Graphics.h>). React/Graphics.h is new in 0.89, so this library is already prepared.
  • react-native-svg 15.16.1 wraps every invokeJavaMethod call in #if REACT_NATIVE_MINOR_VERSION >= 89 and uses the new overload there.
  • react-native-maps 1.29.11 and @react-native-firebase/app 27.1.1 ship checked-in generated JNI that calls the deprecated overload: 7 and 23 calls. Expect compiler warnings, not errors, unless your build turns warnings into errors.

We also searched the JavaScript of all 30 packages for APIs 0.89 drops (TouchableBounce, unstable_getScrollParent, blurOnSubmit, @react-native/assets-registry). The only match was a comment in react-native-svg.

What to check on your own app

  1. Run the same scan over node_modules for your native dependencies, including private ones: python3 check089.py node_modules/* node_modules/@*/*.
  2. If you use Notifee, decide between the patch, a fork or waiting, and test a foreground and a background notification on Android after the bump. Watch Logcat for SEND_EVENT.
  3. Search your own android/ and ios/ folders for the removed flags. Our 0.89 RC overview has the full list and the template edits.
  4. Check the next and beta tags of the libraries you depend on in the week before 7 December: screens, webview, video and linear-gradient already have newer prereleases than their latest.
  5. Build once with warnings visible and note which libraries print the invokeJavaMethod deprecation, so the next release that removes it does not surprise you.

When 0.89.0 final ships, we will update this page with the library versions published since.

Made by the team behind this post

Apps from our studio

  • Goes with this post

    Cardigami

    Pop-up greeting cards that rise out of the fold on iPhone Duo.

    iPhone · App Store

    Get
  • Goes with this post

    BMDB.fun

    Your Bollywood world at a glance, with links straight to the OTT app that streams each film.

    Android TV · Web · Mobile

    Get
  • Nix

    The Mac uninstaller that finds what the Trash leaves behind: caches, logs, derived data and saved states.

    macOS

    Get
  • OneClick QuitAll

    Quit every running app in one click. See memory and CPU first.

    macOS · Mac App Store

    Get

Need this built? Let’s talk.

We build and run apps for Mac, TV, mobile and the web, and write about what we learn.