You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using capacitor-razorpay in an ionic capacitor project with Capacitor 4
What happened:
On App submission of testflight, getting the error below
ITMS-90562: Invalid Bundle - The app submission can not be successfully recompiled from bitcode due to missing symbols during linking. You can try to reproduce and diagnose such issues locally by following the instructions from: https://developer.apple.com/library/archive/technotes/tn2432/_index.html
ITMS-90562: Invalid Bundle - Disallowed LLVM instrumentation. Do not submit apps with LLVM profiling instrumentation or coverage collection enabled. Turn off LLVM profiling or code coverage, rebuild your app and resubmit the app.
The technical documentation provided by Apple suggests checking which Framework binary inside the archive has GCC or LLVM instrumentation, and only Razorpay.framework/Razorpay has LLVM instrumentation
sectname __llvm_prf_cnts
sectname __llvm_prf_data
sectname __llvm_prf_names
sectname __llvm_prf_vnds
The suggested solution by Apple and by others have been tried across the Project, Target, and Pods to set
CLANG_ENABLE_CODE_COVERAGE = No
SKIP_INSTALL = NO
BUILD_LIBRARY_FOR_DISTRIBUTION = YES
Yet to no avail, the Razorpay.framework/Razorpay binary still has LLVM instrumentation and the archive submission is still getting rejected
Steps To Reproduce
To Reproduce the issue just start a new ionic capacitor project and add capacitor-razorpay
install node
npm i -g @angular/cli @ionic/cli @capacitor/cli
ionic start new-project-name (follow through the wizard / choose options in terminal, choose to add capacitor to project)
npx cap open ios (this will open the xcode project)
Product->Archive
Right click on the latest archive->Show in Finder
Right click on the archive->Show Package Contents
Right click Products/Applications/->Show Package Contents
Open Terminal here and run
otool -l -arch all Frameworks/Razorpay.framework/Razorpay | grep __llvm_prf
Suggested solution:
CLANG_ENABLE_CODE_COVERAGE = No
seems to be what needs to be done, but it isn't taking effect for me, maybe because it is a dependency in the podspec file applivery/applivery-ios-sdk#7 Here someone has fixed the same issue by removing codeCoverageEnabled = "YES" as can be seen in comparing the fixed branch applivery/applivery-ios-sdk@v2.5...v2.5.1
Razorpay pod Version :
1.3
Xcode Version :
Version 13.0 (13A233)
iOS Deployment Target :
13.0
What you did:
Using capacitor-razorpay in an ionic capacitor project with Capacitor 4
What happened:
On App submission of testflight, getting the error below
ITMS-90562: Invalid Bundle - The app submission can not be successfully recompiled from bitcode due to missing symbols during linking. You can try to reproduce and diagnose such issues locally by following the instructions from: https://developer.apple.com/library/archive/technotes/tn2432/_index.html
ITMS-90562: Invalid Bundle - Disallowed LLVM instrumentation. Do not submit apps with LLVM profiling instrumentation or coverage collection enabled. Turn off LLVM profiling or code coverage, rebuild your app and resubmit the app.
The technical documentation provided by Apple suggests checking which Framework binary inside the archive has GCC or LLVM instrumentation, and only Razorpay.framework/Razorpay has LLVM instrumentation
sectname __llvm_prf_cnts
sectname __llvm_prf_data
sectname __llvm_prf_names
sectname __llvm_prf_vnds
The suggested solution by Apple and by others have been tried across the Project, Target, and Pods to set
CLANG_ENABLE_CODE_COVERAGE = No
SKIP_INSTALL = NO
BUILD_LIBRARY_FOR_DISTRIBUTION = YES
Yet to no avail, the Razorpay.framework/Razorpay binary still has LLVM instrumentation and the archive submission is still getting rejected
Steps To Reproduce
To Reproduce the issue just start a new ionic capacitor project and add capacitor-razorpay
Suggested solution:
CLANG_ENABLE_CODE_COVERAGE = No
seems to be what needs to be done, but it isn't taking effect for me, maybe because it is a dependency in the podspec file
applivery/applivery-ios-sdk#7 Here someone has fixed the same issue by removing codeCoverageEnabled = "YES" as can be seen in comparing the fixed branch applivery/applivery-ios-sdk@v2.5...v2.5.1
Useful Links to understand the issue
The text was updated successfully, but these errors were encountered: