[🐛] Config plugin invalid "Unexpected token 'typeof'" with Expo SDK 54 / React Native 0.81

[Vinntoo]

%23%23 Bug Report

%23%23%23 Environment

• react-native-google-mobile-ads: ^16.0.3
• Expo SDK: 54.0.33
• React Native: 0.81.5
• React: 19.1.0
• New Architecture: Enabled
• Platform: Android

%23%23%23 What happened%3F

When running the project with Expo SDK 54 and React Native 0.81.5, two errors occur:

1. Package "react-native-google-mobile-ads" does not contain a valid config plugin.
2. Unexpected token 'typeof'

The package is configured as an Expo config plugin in app.json as documented:

{
  "expo": {
    "plugins": [
      [
        "react-native-google-mobile-ads",
        {
          "androidAppId": "ca-app-pub-xxxxxxxxxxxxxxxx~xxxxxxxxxx",
          "iosAppId": "ca-app-pub-xxxxxxxxxxxxxxxx~xxxxxxxxxx"
        }
      ]
    ]
  }
}

The first error suggests the package does not export a valid Expo config plugin. The second error (Unexpected token 'typeof') appears to be a syntax parsing issue in the plugin code, possibly due to TypeScript syntax not being compiled correctly for the Expo config plugin entry point.

%23%23%23 Steps to Reproduce

1. Create a new Expo SDK 54 project with React Native 0.81.5
2. Install react-native-google-mobile-ads@^16.0.3
3. Add the plugin config to app.json as shown above
4. Run npx expo prebuild or npx expo start

%23%23%23 Expected Behavior

The config plugin should be recognized and applied without errors during prebuild/start.

%23%23%23 Actual Behavior

Two errors are thrown:

Package "react-native-google-mobile-ads" does not contain a valid config plugin.
Learn more: https://docs.expo.dev/guides/config-plugins/%23creating-a-plugin

Unexpected token 'typeof'

%23%23%23 package.json Dependencies

{
  "expo": "~54.0.33",
  "react": "19.1.0",
  "react-native": "0.81.5",
  "react-native-google-mobile-ads": "^16.0.3"
}

This may be a compatibility issue between v16 of this package and Expo SDK 54 / React Native 0.81.

[lachtos]

Have you tried 16.0.1?
16.0.2 introduced breaking change for old arch (RN 0.81), maybe this is related? Downgrading to 16.0.1 worked for me, though the issue was different and I don't use expo.

[Vinntoo]

Have you tried 16.0.1? 16.0.2 introduced breaking change for old arch (RN 0.81), maybe this is related? Downgrading to 16.0.1 worked for me, though the issue was different and I don't use expo.

Hi @lachtos, thanks for sharing your experience.

That’s helpful to know about the breaking change introduced in 16.0.2 for the old architecture. In my case, I’m fully using Expo SDK, so I’m particularly interested in understanding how this change impacts Expo-based setups specifically.

At the moment, downgrading to 16.0.1 isn’t a viable option for me, as I need to stay aligned with the current Expo SDK requirements. I’m therefore trying to identify a solution that works within the supported Expo environment rather than rolling back versions.

I appreciate the insight and would be glad to hear if you come across any Expo-compatible workarounds or additional findings.

Thanks again!

[mikehardy]

16.0.2 wasn't intended to be a breaking change - all supported versions of react-native and expo support new architecture, and all the other modules were already converted

something else is going on and this will need some investigation but an affected user, followed by a PR I think

[Vinntoo]

16.0.2 wasn't intended to be a breaking change - all supported versions of react-native and expo support new architecture, and all the other modules were already converted

something else is going on and this will need some investigation but an affected user, followed by a PR I think

Understood that 16.0.2 wasn’t intended to be a breaking change. This still appears to be an Expo config-related issue.

The app builds and runs, but we consistently see this warning during config parsing:

Package "react-native-google-mobile-ads" does not contain a valid config plugin.
Learn more: https://docs.expo.dev/guides/config-plugins/#creating-a-plugin

Unexpected token 'typeof'

The warning is persistent in app.json, even though functionality works.