Troubleshooting & FAQs
Troubleshoot common error scenarios and find answers to frequently asked questions.
Order creation is the primary step of the Razorpay payment flow. An Order creates when a customer clicks the pay button on your app. A corresponding order_id generates in the response. Pass this order_id to the Razorpay Checkout options added in your Capacitor app. Know more about
.To raise a request for a new feature, go to New Issue → Feature Request on our
.-
Go to your project's iOS folder and run 'pod update' to update all the pods.
-
If you do not want to update all pods, run 'pod update razorpay-pod'
- Cause: As per Apple's policy, if you use a subscription model in your iOS app, you must use Apple's in-app purchase APIs. Apple does not redirect out of the app for digital product purchases.
- Resolution: Use Apple's in-app purchase APIs.
This is because of the new changes introduced in Xcode 12.
To resolve this:
- Use for launching the app on your Mac.
- Add the following lines to Podfile within
post_install do |installer|
.
installer.pods_project.build_configurations.each do |config|config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"end
Know more about
.To check the SDK version:
- Open your Flutter project in your preferred code editor.
- Open the
pubspec.yaml
file in the root directory of your project. - In the
dependencies
section, look for the Razorpay entry. The version number is specified next to the package name in the formatx.y.z
.
To update the SDK version, follow these steps:
- Open the terminal or command prompt and navigate to your project directory where the
package.json
file resides. - Use the following command to update the dependencies listed in your pubspec.yaml file to their latest compatible versions.
dart pub upgrade <razorpay_flutter_customui>
- If you are using a Flutter iOS application, run
cd ios && pod repo update && pod update
to ensure the internal iOS dependencies are updated to the versions set by the Razorpay package. This is because cocoapods may not automatically update the internal trunk spec to fetch the latest versions. - After running the update command, review the updates fetched by npm to ensure they do not introduce any breaking changes.
- Conduct thorough testing to ensure that the updated packages do not adversely affect the application functionality and commit the changes.
Is this integration guide useful?
ON THIS PAGE