We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Platform:
The upgrade to RN 0.74 added the local resource ios/Bizcuit/PrivacyInfo.xcprivacy
ios/Bizcuit/PrivacyInfo.xcprivacy
After upgrading the Klippa Scanner SDK version to 0.4.2, the embedded PrivacyInfo.xcprivacy conflicts with the local version.
PrivacyInfo.xcprivacy
This line in the Pod spec triggers the issue:
Pod::Spec.new do |spec| spec.name = 'Klippa-Scanner' spec.version = '1.2.1' spec.summary = 'Klippa OCR SDK' spec.description = 'SDK to do document scanning for iOS.' spec.homepage = 'https://www.klippa.com/en/ocr/ocr-sdk/' spec.license = 'PRIVATE' // ... spec.resources = "KlippaScanner.xcframework/*/KlippaScanner.framework/**/*.{strings,png,xcprivacy}"
Revert back to Klippa Scanner SDK version to 0.4.1, re-install Pods and clean workspace
This SO comment may point in the direction of a proper fix for this issue: https://stackoverflow.com/a/78344724/885397
This is how Sentry fixed the same issue: getsentry/sentry-cocoa#3651
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Platform:
The upgrade to RN 0.74 added the local resource
ios/Bizcuit/PrivacyInfo.xcprivacy
After upgrading the Klippa Scanner SDK version to 0.4.2, the embedded
PrivacyInfo.xcprivacy
conflicts with the local version.This line in the Pod spec triggers the issue:
Work around
Revert back to Klippa Scanner SDK version to 0.4.1, re-install Pods and clean workspace
This SO comment may point in the direction of a proper fix for this issue: https://stackoverflow.com/a/78344724/885397
This is how Sentry fixed the same issue: getsentry/sentry-cocoa#3651
The text was updated successfully, but these errors were encountered: