fix(expo): declare AppCheckCore modular dependencies - #1519
Merged
vonovak merged 2 commits intoJul 27, 2026
Merged
Conversation
Added dependencies for GoogleSignIn and related modules.
Collaborator
|
Thanks; afaict this works for expo, but the community cli users will need to specify |
github-actions Bot
pushed a commit
that referenced
this pull request
Jul 27, 2026
## [16.1.4](v16.1.3...v16.1.4) (2026-07-27) ### Bug Fixes * **expo:** declare AppCheckCore modular dependencies ([#1519](#1519)) ([8594b76](8594b76)) ⭐ **Tip**: there's a [paid version of the package](https://universal-sign-in.com/#pricing) with a [new implementation](https://react-native-google-signin.github.io/docs/one-tap), advanced [security features](https://react-native-google-signin.github.io/docs/security), support for [web](https://react-native-google-signin.github.io/docs/setting-up/web), and more features.
|
🎉 This PR is included in version 16.1.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix Expo iOS prebuild failures with the current
GoogleSignIn/AppCheckCorepod graph by declaring the pods that need modular headers from the Expo adapter podspec.Why
Fresh Expo 56 installs with
@react-native-google-signin/google-signin@16.1.2can resolveGoogleSignIn 9.2.0andAppCheckCore 11.3.0. In Expo's default static CocoaPods setup, CocoaPods then fails becauseAppCheckCoreis a Swift pod that depends onGoogleUtilitiesandRecaptchaInterop, which do not define modules unless modular headers are enabled.Expo autolinking already enables modular headers for direct dependencies of Expo modules with native code. The Expo adapter is this package's Swift Expo module, so declaring the specific
AppCheckCoredependency pods there lets Expo apply its normal modular-header handling without requiring generated Podfile edits or anAppCheckCoreversion pin.What Changed
Added these direct dependencies to
ExpoAdapterGoogleSignIn.podspecso Expo marks them modular:GoogleUtilities/EnvironmentGoogleUtilities/UserDefaultsRecaptchaInteropValidation
Created a fresh Expo 56 repro app:
npx create-expo-app@latest rngsi-expo56-repro --template blank-typescript --yes cd rngsi-expo56-repro npm install @react-native-google-signin/google-signin@16.1.2 npx expo prebuild --clean --platform iosBaseline failed during pod install:
After applying this patch:
Results:
pod installsucceeds.xcodebuildsucceeds.GoogleSignIn 9.2.0,AppCheckCore 11.3.0, andRecaptchaInterop 101.0.0.Closes #1517.