-
Notifications
You must be signed in to change notification settings - Fork 299
Description
Describe the bug
The stripe-android-issuing-push-provisioning:1.1.0 library has a transitive dependency on com.google.android.gms:play-services-tapandpay:17.1.2, which is a private SDK that Google distributes
To Reproduce
- Add stripe-android-issuing-push-provisioning:1.1.0 as a dependency in an Expo/React Native project
- Configure EAS Build or any containerized Android build system
- Run eas build --platform android or equivalent
- Build fails with dependency resolution error for play-services-tapandpay:17.1.2
Expected behavior
The library should build successfully in containerized build environments like EAS Build, GitHub Actions, or other CI/CD systems that don't have access to locally installed private Android SDKs.
Screenshots
Could not find com.google.android.gms:play-services-tapandpay:17.1.2
Searched in: maven.org, google(), jcenter(), etc.
Required by: com.stripe:stripe-android-issuing-push-provisioning:1.1.0
Desktop (please complete the following information):
- OS: macOS/Linux (build environment)
- EAS Build: Cloud and local builds
- Expo SDK: 52.0.x
Smartphone (please complete the following information):
N/A
Additional context
The stripe-android-issuing-push-provisioning library depends on com.google.android.gms:play-services-tapandpay:17.1.2, which is a private SDK distributed separately by Google outside of public Maven repositories. This prevents builds in containerized environments that can't access locally installed private SDKs.
Local development builds work when the private SDK is manually installed in the Android SDK directory, but EAS build fails, both locally and in the cloud