-
Notifications
You must be signed in to change notification settings - Fork 10
Known Issues
Due to obfuscation there's an error you may receive from iProov with iProov.CqlF.Errors in the description. Don't be alarmed by this, CqlF is just the result of obfuscation. This will not be obfuscated in future releases.
We have identified an issue in iProov iOS SDK 11.0.1 affecting a subset of devices on iOS 17.1.x following Apple’s recent iOS upgrades. At the end of a GPA and LA scan the SDK throws a Socket timeout error.
The issue appears to only affect iPhone 11 Pro devices and below on iOS 17.1.x.
A 11.0.2 patch remediating the issue is available and we recommend to upgrade.
We have not observed abnormal behaviour prior to 11.0.1, all previous versions including 11.0.0 appear unaffected.
Starscream causes a crash with iProov SDK v10.x.x when run on Xcode 15. You can use Xcode 14.x.x with no problem. If you want to use Xcode 15, please upgrade to iProov SDK v11.x.x.
We are aware of an issue with one of our dependencies, Starscream.
Starscream has recently published a patch release containing breaking changes. This results in errors following a pod-update on Cocoapods, as current versions of iProov SDK will not be able to consume the latest Starscream patch.
We have contacted Starscream asking if they intend to revert the breaking changes as recommended by Semantic Versioning here and here. This is so we can safely plan long term mitigations with the smallest impact for anyone consuming the iProov SDK.
In the meantime, if you or your customers are experiencing this issue, the following options are available:
- Upgrade to iProov SDK 10.3.1 which locks Starscream to 4.0.4, the last version before breaking changes.
- It is also possible for the end user to avoid the auto upgrade of the Starscream pod by adding the following line to their Podfile
pod 'Starscream', '4.0.4'. This option does not require an update to the iProov SDK.
A very intermittent issue has been found around the face detector not being able to detect a face for Genuine Presence Assurance after multiple hours/days. The error received indicates it occurs within Apple's face detection library, for which we have currently logged an issue with Apple and are awaiting feedback.
Please look at this page about updating for use past Dec 2024
Using iProov SDK versions prior to v9.5.1 in Xcode 14.0 beta will result in the following error:
Failed to build module 'iProov'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.5 (swiftlang-1300.0.31.1 clang-1300.0.29.1)', while this compiler is 'Apple Swift version 5.7 (swiftlang-5.7.0.113.202 clang-1400.0.16.2)'). Please select a toolchain which matches the SDK.
You may also receive other build errors, such as:
iProov.framework/Modules/iProov.swiftmodule/arm64-apple-ios.swiftinterface:26:39: Redundant conformance of 'CGRect' to protocol 'CustomDebugStringConvertible'
To resolve this issue, use iProov SDK v9.5.1 or newer.
Users of Xcode 13 must follow the Guidance for users of Xcode 13.
When running SDK v9.0.0 on Xcode versions earlier than Xcode 12.5, you will get an error when running the app:
dyld: Symbol not found: __ZN5swift34swift50override_conformsToProtocolEPKNS_14TargetMetadataINS_9InProcessEEEPKNS_24TargetProtocolDescriptorIS1_EEPFPKNS_18TargetWitnessTableIS1_EES4_S8_E
Referenced from: /private/var/containers/Bundle/Application/2BEBE672-07C5-4505-8304-E82A1C7799F1/Example.app/Frameworks/iProov.framework/iProov
Expected in: /private/var/containers/Bundle/Application/2BEBE672-07C5-4505-8304-E82A1C7799F1/Example.app/Frameworks/Starscream.framework/Starscream
in /private/var/containers/Bundle/Application/2BEBE672-07C5-4505-8304-E82A1C7799F1/Example.app/Frameworks/iProov.framework/iProov
dyld: launch, loading dependent libraries
DYLD_LIBRARY_PATH=/usr/lib/system/introspection
DYLD_INSERT_LIBRARIES=/Developer/usr/lib/libBacktraceRecording.dylib:/Developer/usr/lib/libMainThreadChecker.dylib:/Developer/Library/PrivateFrameworks/DTDDISupport.framework/libViewDebuggerSupport.dylib
You should either upgrade to Xcode 12.5, or upgrade to SDK v9.0.1 or newer which is built against Xcode 12.4 and does not exhibit this issue.
💡 If you have any additional insights to provide regarding the above issues, please contact support, referencing the MOB number.