v 1.0.2 emits an error when using expo

[enqqi]

Before submitting a new issue

• I tested using the latest version of the library, as the bug might be already fixed.
• I tested using a supported version of react native.
• I checked for possible duplicate issues, with possible answers.

Bug summary

Latest version (1.0.2) emits an error when using expo

bunx expo@latest install --fix

...<other logs>...
Skipping config plugin check: Unable to resolve a valid config plugin for react-native-bottom-tabs.
• main export of react-native-bottom-tabs does not appear to be a config plugin: the following error was thrown when importing /Users/z/code/book.pr/node_modules/.bun/react-native-bottom-tabs@1.0.2+bcc058c2efaafc11/node_modules/react-native-bottom-tabs/app.plugin.js: Cannot destructure property 'createRunOncePlugin' of 'import_config_plugins.default' as it is undefined.
Verify that react-native-bottom-tabs includes a config plugin. If it does not, then remove the entry from plugins in your app config file. Learn more: https://docs.expo.dev/guides/config-plugins/

Library version

1.0.2

Environment info

System:
  OS: macOS 26.0.1
  CPU: (14) arm64 Apple M4 Pro
  Memory: 2.16 GB / 48.00 GB
  Shell:
    version: "5.9"
    path: /opt/homebrew/bin/zsh
Binaries:
  Node:
    version: 22.19.0
    path: /Users/z/.local/state/fnm_multishells/92124_1761330541378/bin/node
  Yarn: Not Found
  npm:
    version: 11.6.0
    path: /Users/z/.local/state/fnm_multishells/92124_1761330541378/bin/npm
  Watchman:
    version: 2025.10.06.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 25.0
      - iOS 26.0
      - macOS 26.0
      - tvOS 26.0
      - visionOS 26.0
      - watchOS 26.0
  Android SDK:
    API Levels:
      - "36"
      - "36"
    Build Tools:
      - 36.1.0
    Android NDK: Not Found
IDEs:
  Android Studio: 2025.1 AI-251.27812.49.2514.14217341
  Xcode:
    version: 26.0.1/17A400
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.16
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 20.0.2
    wanted: ^20.0.2
  react:
    installed: 19.1.0
    wanted: 19.1.0
  react-native:
    installed: 0.81.5
    wanted: 0.81.5
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Steps to reproduce

1. Install latest expo project
2. add "react-native-bottom-tabs", as a config plugin
3. Run expo install --fix
4. get error

Reproducible sample code

https://github.com/callstackincubator/react-native-bottom-tabs/tree/main/packages/expo-template

`expo install --fix` on the repo

[enqqi]

Unable to build the expo dev client

eas build -p ios -e development --local --clear-cache

Failed to read the app config from the project using "npx expo config" command: npx expo config --json exited with non-zero code: 1.
Falling back to the version of "@expo/config" shipped with the EAS CLI.
Cannot destructure property 'createRunOncePlugin' of 'import_config_plugins.default' as it is undefined.
    Error: build command failed.

[okwasniewski]

Hey, which Expo SDK are you using? Can you please provide a reproduction?

[enqqi]

I’m currently using "expo": "54.0.20".

After upgrading to 1.0.2, the config plugin stopped working in Expo. I reverted to 1.0.1, and that version works fine. Just wanted to flag this in case others run into the same issue, or if there's a known fix coming.

You can test it in the repo I shared in the original comment, or any new expo project.

[erenkulaksiz]

"react-native-bottom-tabs": "^1.0.2",
"expo": "~54.0.13",
"react-native": "0.81.4",

PluginError: Unable to resolve a valid config plugin for react-native-bottom-tabs. • main export of react-native-bottom-tabs does not appear to be a config plugin: the following error was thrown when importing /Users/eren/Desktop/project-monorepo/node_modules/react-native-bottom-tabs/app.plugin.js: require() of ES Module /Users/eren/Desktop/project-monorepo/node_modules/react-native-bottom-tabs/lib/module/expo.js from /Users/eren/Desktop/project-monorepo/node_modules/react-native-bottom-tabs/app.plugin.js not supported. Instead change the require of expo.js in /Users/eren/Desktop/project-monorepo/node_modules/react-native-bottom-tabs/app.plugin.js to a dynamic import() which is available in all CommonJS modules. ERR_REQUIRE_ESM Verify that react-native-bottom-tabs includes a config plugin. If it does not, then remove the entry from plugins in your app config file. Learn more: https://docs.expo.dev/guides/config-plugins/

Edit: Downgrading to 1.0.1 not worked. But replacing expo plugin code with this worked:

const { createRunOncePlugin, withAndroidStyles } = require('@expo/config-plugins');

const MATERIAL3_THEME_DYANMIC = 'Theme.Material3.DynamicColors.DayNight.NoActionBar';
const MATERIAL3_THEME = 'Theme.Material3.DayNight.NoActionBar';
const MATERIAL2_THEME = 'Theme.MaterialComponents.DayNight.NoActionBar';
const MATERIAL3_EXPRESSIVE_THEME = 'Theme.Material3Expressive.DayNight.NoActionBar';
const withMaterial3Theme = (config, options) => {
  const theme = options?.theme;
  return withAndroidStyles(config, stylesConfig => {
    stylesConfig.modResults.resources.style = stylesConfig.modResults.resources.style?.map(style => {
      if (style.$.name === 'AppTheme') {
        if (theme === 'material3-dynamic') {
          style.$.parent = MATERIAL3_THEME_DYANMIC;
        } else if (theme === 'material2') {
          style.$.parent = MATERIAL2_THEME;
        } else if (theme === 'material3-expressive') {
          style.$.parent = MATERIAL3_EXPRESSIVE_THEME;
        } else {
          style.$.parent = MATERIAL3_THEME;
        }
      }
      return style;
    });
    return stylesConfig;
  });
};
module.exports = createRunOncePlugin(withMaterial3Theme, 'react-native-bottom-tabs');

But i hate to modify packages :D

[kcotias]

Getting the same!

[mdcuk34]

Same here - the above workaround works though

[TowhidKashem]

same issue.

[alextbogdanov]

+1