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
Read and follow the guides described in the documentation.
Try to reproduce in our demo project.
Search for your issue in the existing GitHub issues.
Bug Description
Incorrect types for expectedPass on iOS. The variables defined on eImageQualityCheckType that are shown in the documentation examples are typed incorrectly for the iOS library. The variables in JS are defined as numbers but iOS expects them as strings
Steps To Reproduce
Try to setup your document scan config using the exact example from the docs and your app will crash because the parameters are incorrect.
I attempted to use the getTranslation method but that method expects a callback which is just completely unnecessary for doing a simple number to string mapping. I think the iOS native code needs to be update to accept the number type like the docs show. Or you could do the mapping on the JS side. Or even just define the string versions of the eImageQualityCheckType in JS and let the consumer do their own mappings.
The text was updated successfully, but these errors were encountered:
Before Submitting, be sure to
Bug Description
Incorrect types for
expectedPass
on iOS. The variables defined oneImageQualityCheckType
that are shown in the documentation examples are typed incorrectly for the iOS library. The variables in JS are defined as numbers but iOS expects them as stringsSteps To Reproduce
Try to setup your document scan config using the exact example from the docs and your app will crash because the parameters are incorrect.
I attempted to use the
getTranslation
method but that method expects a callback which is just completely unnecessary for doing a simple number to string mapping. I think the iOS native code needs to be update to accept the number type like the docs show. Or you could do the mapping on the JS side. Or even just define the string versions of theeImageQualityCheckType
in JS and let the consumer do their own mappings.The text was updated successfully, but these errors were encountered: