stripe.setOptions error: null is not an object (evaluating 'StripeModule.init')
See original GitHub issueBefore I have submitted the issue
[X] I have read an installation guide
[X] I know that for an iOS I need to install pods because I’ve read the installation guide
[X] I have read a linking guide and checked that everything is OK like in manual linking guide
[X] I know that before using tipsi-stripe
I need to set options for my app as described in usage guide
The problem
I am running into issues with setting the options. I am on a Windows PC and Android and I went through all the proper linking steps in the offical documentation, but I am still getting an error when setting the options in the file.
It is returning that 'null is not an object (evaluating ‘StripeModule.init’). I am confused since I am not on Mac, so I can’t just simply link and use Cocoa Pods. Any help from anyone who has run into this in the past?
Environment
tipsi-stripe
version: @7.5.1- iOS or Android: Android
- OS version: Android 9 (Google Pixel)
- React-Native version: 0.59.10
- (Android only)
com.google.firebase:firebase-core
version: ??? - (Android only)
com.google.android.gms:play-services-base
version: ???
Links to logs and sources
Here is a Gist of all the linking I did in the Android files: https://gist.github.com/Riive-Inc/8aadce38869915ecb3d4c8d548bf0daa
For Android
, please provide the following sections from android/app/build.gradle
:
- android.compileSdkVersion: 28
- android.buildToolsVersion: 28.0.3
- android.defaultConfig.minSdkVersion: 21
- android.defaultConfig.targetSdkVersion: 27
Screenshots, GIFs (Must to have)
The error:
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:8
Top GitHub Comments
Hi @LivanDiaz,
These are my setting for tipsi-stripe. iOS: podfile
Android:(linking manually) android/settings.gradle
android/app/build.gradle
android/app/src/main/java/<bundle>/MainApplication.java
These settings are done for react-native 0.62.2
I hope these will help for you to fix the issue…
Thanks
same issue, no clear fix from any of these threads… anyone have success?