Skip to main content
When a framework is distributed, it contains architectures of the simulators so that the consumer of the framework can build it on a simulator. However, when uploading the archive on iTunes, you have to strip these architectures. If you use Cocoapods, it strips the simulator architectures on its own.Since you are not using it, please follow the below-mentioned steps:
  1. Download the script.
  2. Locate the directory in which Razorpay.framework is present in the archive that you are trying to upload.
  3. Move the attached script to the above directory and run it.
  4. Remove the script file.
No. You see the update SDK alert because a newer version of our SDK is available. We recommend you use the latest SDK. This message shows up only when running the app on a simulator or using a test key to initialise the SDK.
  • Ensure that Razorpay.framework is present in your project settings in both the Embedded Binaries and Linked Frameworks.
  • Set Always Embed Swift Libraries to “yes” in the project settings. It can happen because of the incompatibility between the developed Swift version with Razorpay.framework and the Swift version of your project.
  • We recommend using the framework compiled with the required Swift language from our iOS documentation.
Razorpay’s bitcode enabled framework works even if you do not enable bitcode in your project.
There are multiple Swift versions available, but unfortunately, Apple does not make all the versions compatible, so we release frameworks compiled in multiple Swift versions.
  • Download the framework that is compatible with your project.
  • If you run into a compatibility issue, ensure that you try both frameworks.
A module map is used to define the header files that should be converted into modules and used by your project. Razorpay handles this internally.
  • Cause: By default, the Xcode’s name is assumed to be Xcode.app. For example, your default Xcode appears as Xcode9.3.
  • Resolution: Insert this script in the directory that contains Razorpay.framework file and run it from your terminal.
Add the following code in the ViewController.m file:
Add code
This will improve the iOS sample app experience and reduce the build failure.
No, we do not support Xamarin. However, since Xamarin is essentially a wrapper around Android and iOS, you can create your own Xamarin wrapper using our Android and iOS SDKs.You can refer to Xamarin for integrating native Android and iOS libraries. Alternatively, you can use web integration to open the checkout form in a web view.
To check the SDK version:
  1. Open your iOS project in Xcode.
  2. In the project navigator, locate the Podfile in the root directory of your project.
  3. Open the Podfile and look for the line that specifies the Razorpay SDK pod. The version number is represented by x.y.z.
To update the iOS Standard SDK, follow these steps:
  1. In your project’s Podfile, specify the latest SDK version. If you do not mention any version, it automatically picks the latest version from Cocoapods.
  2. Run pod repo update to fetch the latest release versions of the pods.
  3. After updating, ensure that the integration is successful and there are no issues with the updated SDK.
After installing the razorpay-pod cocoapod in the project, once the application is archived, privacy report can be generated from the context menu for the created archive. The data used by the Razorpay SDK will be listed under Razorpay.framework along with the reasons for the usage of the data. For more information, you can refer to Apple’s documentation for generating the privacy report. For more information about PrivacyManifests and Required Reason API please refer to Apple’s documentation.
After the installation of the razorpay-pod cocoapod, inside the pods folder, expand the folder Development Pods/razorpay-pod/Frameworks. Inside this folder, you will find the Razorpay.xcframework file. On selecting this file, XCode’s File inspector shows you the XCFramework’s code signing status. If the framework is signed with an Apple Developer certificate, the inspector also shows which Apple Developer team signed the framework.You can find more about verification of the signature here.