Skip to content

fix: use public api instead of private in expo config plugin#1496

Merged
vonovak merged 1 commit intomasterfrom
fix/use-public-api
Feb 28, 2026
Merged

fix: use public api instead of private in expo config plugin#1496
vonovak merged 1 commit intomasterfrom
fix/use-public-api

Conversation

@vonovak
Copy link
Collaborator

@vonovak vonovak commented Feb 28, 2026

closes #1492

Summary

The Expo config plugin imports appendScheme directly 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

  • Removed import { appendScheme } from '@expo/config-plugins/build/ios/Scheme'
  • Replaced with IOSConfig.Scheme.appendScheme() from the already-imported expo/config-plugins

@vonovak vonovak merged commit 32911ef into master Feb 28, 2026
2 checks passed
@vonovak vonovak deleted the fix/use-public-api branch February 28, 2026 22:15
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.
@github-actions
Copy link

🎉 This PR is included in version 16.1.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant