v3.1.10

Fixed

• Stability: internal resource lifecycle management has been improved to reduce crashes due to memory leakage.
• UX: touch scrolling is now blocked between the started event and exiting fullscreen.
• UX: Page jank when entering fullscreen, particularly in Chrome, has been fixed - see changes.
• Allow landscape: an issue causing broken images in the rotate slot has been fixed.
• Cameras: An issue where mobile devices could choose the environment facing camera has been fixed.
• Safari Desktop: AbortError is now handled. These cases remain subject to video data timeout checks.

Changed

• started event behaviour has been changed in a BC-safe way to reduce page jank:
  • The started event is now sent after entering fullscreen rather than in parallel
  • The started slot manager callback no longer hides all slots when entering fullscreen.
  • The streaming event is the soonest event that all slots are hidden.
• Internal UI lifecycle management has been tidied which may yield a slight improvement in UI performance.

v3.1.9

Fixed

• Problems entering fullscreen will no longer abort the transaction. In these rare cases, transactions will be allowed to continue.
• Opera Touch is now a supported browser after working around a WebKit issue.
• When running Web SDK inside a react-native-webview, it no longer flags the environment as unsupported.

Internals

• The following are now sent to the backend to improve telemetry and customer support:
  • When Web SDK detects it's within an iframe, the window innerWidth and innerHeight are sent.
  • Fullscreen status is sent.

3.1.8

20.4.2021 3.1.8

Fixed

• When a user cancels inside Native Bridge, the cancelled event is now correctly triggered from the Web SDK.
• UI text overflow is now elegantly managed, rather than clipping at the edges.
• Speculative fix to some Android webview environments crashing due to an undefined browser name.
• Liveness transactions no longer experience UX issues when rotating to and from landscape orientation.
• The SDK will issue a clear error message if it receives an invalid looking token to the SDK, rather than displaying a server error.
• The unsupported event now aborts the claim with a device_unsupported code which will aid analytics.

3.1.7

14.4.2021 3.1.7

Fixed

• is_native_bridge property restored to event payloads. Previously this was only present during native bridge claims.
• Fixed streamed event to fire when all video frames have streamed. Previously this erroneously fired after encoding.

3.1.6

5.3.2021 3.1.6

Fixed

• Fixed UI animation loop not always stopping
• Improve scanline synchronisation with flashing
• Various performance improvements

Changed

• Optimised UI opening / rotation experience

3.1.5

4.3.2021 3.1.5

Fixed

• Fixed starting in landscape orientation then rotating to portrait UI issues
• Improved GPA flash timing, particularly on Android
• Improved low FPS detection
• Added missing feedback property from some error events
• Fixed documentation to correctly reflect error_fullscreen_change and error_no_face_found event names
• Fixed instances when rare Android Native SDK crashes may take the Web SDK with them, too
• Fixed occasional .emit function not found errors
• Fixed issues when lower end Android cameras were unable to request a video feed in a useful aspect ratio

Added

• Added error_no_face_found to public documentation

3.1.4

12.2.2021 3.1.4

Fixed

• Fixed an issue where the progress bar would not display if show_countdown is enabled.
• Fixed kiosk_mode issue on iPads where the camera is drawn partly off screen.
• Fixed an issue where the camera remains active after a timeout occurs.
• Fixed an issue where multiple cameras broadcasts multiple times. It now broadcasts once.
• Fixed an issue where slot encapsulation was broken and events may be bound to slots outside the component.
• Fixed iPads on iOS < 14 showing as unsupported in 3.1.x.
• Fixed an issue where specifying a path with base_url was not respected.
• Fixed an issue where iframed Web SDK components time out waiting for gyro information in mobile Safari.
  • This is a WebKit issue: https://bugs.webkit.org/show_bug.cgi?id=221399
  • Until this is fixed, iframed components in mobile Safari will immediately fire the unsupported event when using Liveness.

Changed

• Internals: changed Web Component attachment mode to closed.
• Internals: the Web SDK will now connect and emit console warnings and errors to our Socket.IO server for quality improvement and crash analysis.
• Bundle size: the main Web SDK entrypoint no longer includes Baidu and KaiOS build targets
  • These browsers currently do not support our minimum requirements
  • The iProovSupport component is still built to target these browsers so you can still establish support
  • The main package size has reduced by 18% with no material change to browser support

Added

• 20% more π

3.1.3

6.1.2021 3.1.3

Fixed

• Fixed desktop Safari issue when starting in certain camera resolutions.

3.1.2

1.1.2021 3.1.2

Added

• Improved documentation on the web public repo.

Fixed

• The console object is no longer overridden. Sorry about that.
• Documentation updates and inaccuracies:
  • Various iProovSupport documentation relating to payloads and availability on the global object
  • Documentation relating to the payload of the progress event has been corrected.
• iProovSupport can now be loaded standalone without a bundler; regeneratorRuntime is now defined.
• Language strings can now be customised on slotted elements. Previously this didn't work.
• Fixed double checking for videoInput. Just once is enough.
• iProovSupport prompting in Chrome prompts instantly, previously it delayed.
• Fixed SDK crashing if passing a token not associated with a user_id. Unlikely, but displays a clean error instead.

3.1.1

Available at: https://www.npmjs.com/package/@iproov/web/v/3.1.1

24.12.2020 3.1.1

Fixed

• Assets which contained // caused 403 issues when hosting assets on Amazon S3. The paths have now been fixed.
• When starting iProov on a bezel-free phone, the layout appeared misaligned. This has now been fixed.
• Disabled underlying TensorflowJS WASM threads due to instability. SIMD remains available.

23.12.2020 3.1.0

Added

• Desktop device support for Liveness. We no longer require a mobile device for Liveness transactions.
• The SDK can now optionally return a selfie frame from the scanning process for both GPA and Liveness transactions.
  • If this is enabled for your service provider, this will be present in the passed and failed callback payloads.
• iProovSupport is a separate export to facilitate a smaller critical bundle size for integrators.
  • Using a module bundler you can run import { iProovSupport } from "@iproov/web/iProovSupport"
  • Script tag integrations can still access window.IProov.IProovSupport for the time being.
• version property on the iProovMe component.
  • This is also accessible on window.IProov.version.
• Multiple camera device support on desktop, including ability to customise.
• Added the csp_nonce option. See Content Security Policy.
• External dependencies are now loaded with <link rel=preload> for non-blocking parallel loading.
• Our feature detector now runs the latest Tensorflow release which includes support for WebAssembly threads and SIMD.
• New streamed event to accommodate the original documented functionality.
• Support added from iOS 14.3 for WKWebView based browsers on iOS such as Chrome, Firefox, MS Edge, etc.

Fixed

• Various CSP warnings have been resolved. See Content Security Policy.
• Firefox and Safari no longer display the grant button unless required.
• Further performance improvements targeted at lower end machines which have a net-positive effect across the board.
• UX improvements for Liveness on mobile devices
• Kiosk mode performance issues on Safari
• Progress bar animation

Changed

• Bundling and modularisation upgrades.
  • Dependencies are once again modular, and will be loaded as needed.
  • This reduces the bundle size from 4MB (plus dependencies) to around 1.3MB gzipped (including dependencies).
  • With the iProovSupport change, the pre-gzip impact to an integration's critical bundle is 16KB raw (was 4MB).
  • With that, assets_url's meaning is changing again, we're afraid...
  • Customers now have a choice to either serve Web SDK assets "on premises", use our CDN, or reverse proxy.
  • This affects CDN and reverse proxy configurations; we do hope this is the last change to asset loading for a long time.
  • Please see the upgrade guide for steps needed.
• The main entry file for the npm package is now iProovMe.js.
• Language files have been updated to be brought into line with native SDKs.
• Minor tweaks to UI to bring the UI experience inline with native SDKs.
• Improved resolution management for less capable or hardware constrained devices.
• Improved our encoder for better speed and the latest bugfixes.
• Bandwidth usage reduced
• The streamed event now emits at the correct time, which may break integrations that rely upon it.
  • To upgrade, replace streamed with streaming which takes its place.

Removed

• Bundled Web Component support. Polyfills are now loaded on an as-needed basis.
• Automatic transpilation for the following outdated browsers:
  • Blackberry < 10
  • Edge < 85
  • Firefox < 82
  • IE < 11
  • IE Mobile (all)
  • iOS Safari < 13.4
  • Opera < 70
  • Safari < 13.1
  • Please see .browserslistrc for the current targeted browsers.
  • If your app must support older browsers, simply transpile the standalone iProovSupport.js checker as needed.