-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Razer payment react native---Cannot read property 'open' of undefined #104
Comments
Ran into the same issue, realized that I forgot to link the package using |
If you face such issue please try the manual linking process specified here , https://facebook.github.io/react-native/docs/linking-libraries-ios or watch our integration videos |
Facing same issue on android as well :( |
@ArjithN please refer the manual linking process for android on react - native docs specified above. |
same I need help for the same issue. Kindly help me as well. @ashwingattani @iThink32, what is the solution for this. open is thrown as undefined. |
hiw can we do it in Expo platform |
You cant do react-native link in expo app |
@Akulvarshney where you able to find a solution? The same happens to me too, saying Error [TypeError: Cannot read property 'open' of null]. Any help would be great. |
The react-native-razorpay package internally uses native libraries for Android and iOS. The error suggests that the native libraries aren't included in the build. During our testing we have been able to resolve this and switching to development build than expo build which allows for the usage of native libraries. Maybe this will help resolve the issue for you folks. |
"react-native-razorpay": "^2.3.0" //Razorpay version I am using |
If it is react cli that means the package wasn't correctly installed. Can you try reinstalling the package? @gopikap |
@vivekshindhe Thank you so much, after re-installation I got the page. |
Hi ,
Working on razor payment gateway , But getting an error of cannot read property 'OPEN' of undefined,
Below is the code used:
The text was updated successfully, but these errors were encountered: