Migrating from 8.2.1 to 8.3.0
- New profile bundles should be used as older than the version 4 are not compatible with 8.3.0
- RecognizerApi.framework dynamic dependency is now required to link with the app
- Added support for simulators x86_64
- AFNetworking dependency is made as optional, hence you can remove it if you don’t use IDSEnterpriseService class
Migrating from 8.2.0 to 8.2.1
- New profile bundles should be used as older than the version 3 are not compatible with 8.2.1
Migrating from 8.1.4 to 8.2.0
- Added new 3rd party dependency: ZipZap
- New profile management system deprecated MJCS-profile.bundle bundles. You need to obtain new packages of .zip files and install them as described in this guide.
- [MJCS loadSDK] is not compulsory to call before using the SDK
Migrating from 8.1.0 to 8.1.1
For Proxy setups if you are using liveness:
- idscanenterprisesvc/journey/liveness/
Migrating from 1.6.25 to 8.1.0
- Changed the way how we add MJCS to the project. (Please refer to section: “Using the SDK”)
- Changed package & framework name to “MJCS”.
Added scanner types for A4 scanning and extraction and selfie scanning.
- IDSDocumentScannerControllerTypeUtility
- IDSDocumentScannerControllerTypeSelfie
Changed response objects for DocumentScannerService:
- We no longer provide any response in metadata object but IDESDocument object.
- The result is unified under IDESDocument class
- The legacy “IDSMetadataMachineReadableZoneObject” OCR results are removed and now we offer server results as they have higher accuracy.
Changed Endpoints and their actions:
* Changed endpoints for users using reverse proxy or similar, changes reflect increased security with 8.0.0 IEOS servers.
* From idscanenterprisesvc/scan/send to idscanenterprisesvc/journey/upload
* From idscanenterprisesvc/search/getentryresult/ to idscanenterprisesvc/journey/get/
* Refer for updated actions in section “Concept of IEOS driven Onboarding Journeys”
Migrating from 1.6.x to 8.1.0
All applies from 1.6.25 to 8.1.0
We offer IDSCustomerJourneyController integration approach as its easy and requires minimal change to support customer journeys.