BlinkID / blinkid-in-browser

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

Updating In-browser-sdk version from 5.16.0 to 5.18.0 #82

Closed DilipV2503 closed 2 years ago

DilipV2503 commented 2 years ago

Hello, I updated the version of in-browser-sdk from 5.16.0 to 5.18.0 and getting the below error MicrosoftTeams-image (3)

and, The below code , I am using image

Please let me know what I am missing also I have checked the document and it is setting the workerLocation also for the new version

Note:- Is it necessary to set workerLocation Path? If yes then what should be the path

AngTim commented 2 years ago

Hello Dilip,

I hope you're doing well. Thank you for the inquiry and the code snippet. Can you try to access the file that is throwing the 404 error via your browser? There is no need currently to modify the workerLocation path.

Let us know if you are able to access the file, and feel free to contact us if you have any additional questions or issues.

Kind regards, Angelo Web Support Associate Microblink LTD

DilipV2503 commented 2 years ago

Hello @AngTim

Yes, I am getting the 404 error when trying to access the URL which appears in the console.

Let me know if you need anything else.

Thanks!

AngTim commented 2 years ago

Hello Dilip,

Apologies for the late reply; we had holidays for a few days. The 404 error could be either caused by an incorrect path to the resources or not hosting resources at all.

It can look something like this for hosting the resources locally:

loadSettings.engineLocation = "http://localhost/resources" loadSettings.workerLocation = "http://localhost/resources/BlinkCardWasmSDK.worker.min.js"

Please try to modify the engine and worker location, check if you are hosting the resources correctly, and let us know if you still receive the same error.

If you have any additional questions or issues, contact us.

Kind regards, Angelo Web Support Associate Microblink LTD

AngTim commented 2 years ago

The thread was inactive.