search

BlinkID / blinkid-in-browser

BlinkID In-browser SDK for WebAssembly-enabled browsers.
https://microblink.com/blinkid
64 stars 31 forks source link

Bug: Blink ID 6.8.0 Unable to scan documents in Firefox Browser #139

Open bandredh opened 4 months ago

bandredh commented 4 months ago

Bug Description: An issue arises when using the BlinkID UI Browser SDK in a project and enabling the returnFaceImage: true and returnEncodedFaceImage: true options within the customSettings configuration, specifically when running the application in the Firefox browser. The problem occurs as the ID scan fails to capture a document, but when these options are set to false, the ID scan successfully captures the document in Firefox.

Steps to Reproduce:

  1. Integrate the BlinkID UI Browser SDK into the project.
  2. Enable the returnFaceImage: true and returnEncodedFaceImage: true options within the customSettings configuration.
  3. Launch the application in the Firefox browser.
  4. Initiate an ID scan using the BlinkID UI Browser SDK.
  5. Observe that the ID scan does not capture the document.

Expected Behavior: Regardless of the browser being used, the ID scan should properly capture the document and return the face image when the returnFaceImage: true and returnEncodedFaceImage: true options are enabled within the customSettings configuration.

Actual Behavior: Specifically in the Firefox browser, the ID scan fails to capture the document and does not return the face image when the returnFaceImage: true and returnEncodedFaceImage: true options are enabled. Conversely, when these options are set to false, the ID scan successfully captures the document in Firefox

Firefox version: 127.0.2 BlinkId version: 6.8.0 Windows 11 Enterprise

AngTim commented 4 months ago

Hello Bandredh,

Thank you for the report and for describing the whole behavior and results. We have tried to reproduce the issue from our side on a MacBook Pro (M1) on a Firefox browser (Version 127.0.2 -64-bit) with the UI component of the BlinkID SDK (Version 6.8.0) from our examples directory and we noticed no problems or errors with the scanning process or the extraction of the faceImage and fullDocumentImage as well.

The code example that was used to update the recognizer settings:

`function run() { // Important: if attributes or properties are changed, whole component is rerendered const blinkId = document.querySelector("blinkid-in-browser");

blinkId.recognizers = ["BlinkIdMultiSideRecognizer"];

blinkId.recognizerOptions = { "BlinkIdMultiSideRecognizer":{ "returnFaceImage":true, "returnEncodedFaceImage":true, "returnFullDocumentImage": true, "returnEncodedFullDocumentImage":true } } `

UI-firefox Screenshot 2024-07-08 at 11 43 50 Screenshot 2024-07-08 at 11 44 04

Can you please try to repeat the scanning process while using the above suggestion of the recognizer settings? In our scenario, we were scanning a Croatian ID sample document.

Kind regards, Angelo Web Support Specialist Microblink LTD

bandredh commented 4 months ago

Hello Team

Thank you for your update. In our work, we have been in the process of updating the version of BlinkID from 6.2.1v to 6.8.0. However, during this update, we encountered a significant issue with the id scan functionality specifically in the Firefox browser. Prior to version 6.6.0, the id scan was functioning properly across all major browsers, including MS Edge, firefox and Chrome. However, upon updating to versions higher than equal to >=6.6.0, the id scan issue started to be triggered exclusively in the Firefox browser.

Interestingly, we did discover a temporary workaround where disabling the 'returnFaceImage' and 'returnEncodedFaceImage' fields in the customSettings allowed the scanning to proceed successfully. However, for our project requirements, we need to have these fields enabled to facilitate further facial image comparison processes.

Upon reviewing the changelog.md for version 6.6.0, it appears that the added 'BloodType' and 'Sponsor' fields in BlinkIdMultiSideRecognizer.Result cannot be identified as the cause for the issue being triggered.

Considering these findings, we suspect that there might be a need for specific polyfill updates or additional browser conditions that are mandatory for Firefox starting from version 6.6.0 in order to overcome this issue. It is worth noting that this issue seems to be limited to the Firefox browser and has only surfaced after the version update from 6.5.2v to any version higher than 6.6.0 without any other code changes.

Could you please verify on any new conditions introduced from version 6.6.0 onwards that are specifically relevant to Firefox compatibility