fix: use public api instead of private in expo config plugin#1496
Merged
fix: use public api instead of private in expo config plugin#1496
Conversation
github-actions bot
pushed a commit
that referenced
this pull request
Feb 28, 2026
## [16.1.2](v16.1.1...v16.1.2) (2026-02-28) ### Bug Fixes * use public api instead of private in expo config plugin ([#1496](#1496)) ([32911ef](32911ef)) ⭐ **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.2 🎉 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.
closes #1492
Summary
The Expo config plugin imports
appendSchemedirectly from@expo/config-plugins/build/ios/Scheme, which is not declared as a dependency. This causes issues in strict package managers like pnpm, where undeclared dependencies are not accessible.Changes
import { appendScheme } from '@expo/config-plugins/build/ios/Scheme'IOSConfig.Scheme.appendScheme()from the already-importedexpo/config-plugins