iOS SDK FAQs
This page contains frequently asked questions about the HyperKYC iOS SDK, covering common issues, permissions, compatibility, and troubleshooting.
1. Why am I seeing "Unable to present on <…> which is already presenting"?
This happens if the SDK is launched from a controller that is already presenting another view (modal, alert, etc.).
Solution: Always initialize and launch HyperKYC from your app's main/root view controller (or top-most visible controller). This ensures a clean presentation stack and avoids UIKit presentation errors.
2. Does the SDK support iOS 26 or face capture on iOS 26 devices?
Yes. HyperKYC SDK supports iOS 26 from version 0.48.0 onwards.
- Workflows (document capture, liveness, NFC, etc.) are compatible on iOS 26.
- The face capture red overlay issue seen on earlier SDK versions has been fixed starting with v0.48.0.
3. Why was my iOS app flagged during App Store review for using the NFC framework?
Some apps may receive queries from App Store reviewers regarding the usage of the NFC framework.
The HyperKYC SDK uses NFC only when the NFC module is enabled in your workflow, and strictly for scanning ISO7816-compliant NFC smart cards (such as e-passports or national ID cards).
The SDK does not use NFC for payments or any financial transactions.
If your workflow does not include NFC, the SDK will not invoke or require NFC functionality.
4. Why Does My App Store Upload Fail with a CFBundleExecutable Key Error in v1.0.0?
Solution: To resolve the issue, run the following command and try again:
rm -rf ~/Library/Caches/CocoaPods; rm -rf Pods; rm -rf ~/Library/Developer/Xcode/DerivedData/*; pod deintegrate; pod setup; pod cache clean —all; pod repo update; pod install --repo-update