iProov understands that organizations can be reluctant to update their environments. We work hard to:
If you have concerns, contact Support or your Customer Success team.
Improvements to SDK performance and reliability.
iProov plays a critical role in your onboarding and authentication journeys. You should ensure your implementationn is always using the latest iProov SDK. We strongly recommend this be incorporated into your release processes. Your Customer Success team can help you define this process.
Upgrading SDKs is straightforward and our releases are backwards compatible, unless otherwise specified. See the upgrade guides on our GitHub pages:
Android: https://github.com/iProov/android/wiki/Upgrade-Guide
iOS: https://github.com/iProov/ios/wiki/Upgrade-Guide
Web: https://github.com/iProov/web/wiki/Upgrade-Guide
To stay up to date with our client SDK releases, subscribe to our GitHub release notes:
You will be notified when a release is published and what has changed.
The release schedule varies according to the need to patch bugs and deliver new features. This schedule is flexible and we may release more rapidly in response to issues. It is important to subscribe to stay up-to date.
Whilst upgrades are optional, they typically contain security updates and new features that you may find useful. We normally support an SDK version for six months following the release of the next version.
iProov SDKs do not stop working after six months, however, we recommend regular updates. SDKs often include security updates and, in some instances, are tightly coupled with iProov backend changes. If an SDK is significantly outdated, and we update our backend to fix security vulnerabilities, we may block requests from some SDK versions.