I'm using react-native-vision-camera to build a QR-Code-Scanner for my app. I followed this guide by dynamsoft: https://www.dynamsoft.com/codepool/react-native-qr-code-scanner-vision-camera.html
In the beginning everything worked fine but now I'm always getting an Exception when reading QR-Codes with my camera. Even with the provided example project in the post it's not working properly anymore.
The detected result I get always has asterisks in it like this: [Attention(exceptionCode:-20111)] *ttp*//**ca*h*st*9*02/*entalobje*ts*book**98420*d*6b**-4***-9e***6*d796*0c*55
I already tried reinstalling the library and everything but I can't get it to work.
vision-camera-dynamsoft-barcode-reader has an internal dependency on DynamsoftBarcodeReader SDK and it needs an active license, which I found out in their other examples. In all their examples, public license are used which has an expiration date.
Due to this reason, I made a switch to vision-camera-code-scanner. This was already suggested in Community Plugin List of VisionCamera.
Hope this helps!
Related
I have a working Electron app which I wrote about two years ago. I'm not an employee of a company, but just some guy that wrote an app that a few people use to make the world a better place. Anyway, I need to make some changes to the app but my computer crashed a while back so I downloaded my old code from Github onto my new computer and started to get to work. But immediately I found the app wouldn't work in the new 17.0.0 version of electron because the REMOTE module in Electron was deprecated and then removed in previous versions. I tried to follow the instructions here... https://www.npmjs.com/package/#electron/remote?activeTab=readme to replace REMOTE with the new #electron/remote module. I've had several problems, my most recent is:
JavaScript Error: Uncaught Exception: TypeError BrowserWindow is not a constuctor at app.createWindows (C:...\main.js:89:17).
I use the remote functionality (properties?) over 50 times in my app, including .dialogue, .getGlobal, .getCurrentWindow, and .BrowserWindow.getAllWindows
I'm not including my code here because I'm not really looking for a a coding solution (unless that's the easy/best/only thing I should do and you can give me a solution from the information I've written) but more general advice on what direction I should go to solve this problem. I'm a good programmer in a language that is not Electron, or JavaScript, or NodeJS! So, with the right instruction I can get by, but please be easy on me. (For example I get lost in the instructions for #electron/remote around the API Reference section.) Thanks for any help you can provide.
Mike
Some big changes have been made to Electron over the past couple of years, especially with the use of remote. I would hate to say it but it looks like you are in for a bit of work to get it operational again.
You will want to look at ipcMain, ipcRender and contextBridge.
The inclusion of webPreferences: {preload: ""} in your new BrowserWindow() method plus the use of the above Electron methods will place you in a good starting position for safe, quick, thread seperated code.
See Context Isolation and Inter-Process Communication for more info.
PS: If you need a quick bit of code to get you going / give you an idea then let me know.
Following the ODATA V4 tutorial in step 2: app runs against mockserver, tips are given to run it against a real server. Used the existing index.html as test/mockServer.html and created a new index.html, pointing to ComponentSupport for oninit. Added cors-anywhere and adjusted the manifest. Works well, both mockserver and real.
That was in step 2 and the app worked fine also against a real server. Fast-forward to step 5 and I notice the app fails to load any data when running against a real server. Long story short, the backend is throwing an error, not even "count" together with "top" is accepted. I checked the docs for ODATA, "count" does not seem to be an exclusive option.
Am I fundamentally misunderstanding the way ODATA works? I am especially puzzled by the fact that the mockserver runs fine.
EDIT: created bugreport
As reported in the closing comment of my bugreport, Microsoft has confirmed the issue: "This was due to an error in the version of the OData WebAPI library we were using in the backing service. I have an update with various fixes, including updating to the latest WebAPI library that contains this fix, that I just haven't pushed out to production yet. Let me see when if I can get that deployed."
I am trying to use Swagger UI to document our node.js API, so I went to http://swagger.io/docs/, down to Swagger UI Documentation -> Usage, to find this
Now, this is not the only place that provides these instructions, there are dozens of blogs & tutorials saying the same thing, so that's exactly what I did.
Cloned the repo, went into /dist/ and ran the /dist/index.html and all I get is an empty page with an error:
I'm slowly going crazy now as I can't find anything about it and literally every place I looked just has the same, copied, instructions with nothing else provided (like what could go wrong? you just open a file...)
Any help or explanations are much appreciated!
P.S. for some reason opening the /public/index.html works (mentioned nowhere on the www)
I think this is bug in new version of swagger-UI. This is fresh release and they are still modifying and fixing bugs.
Look here: Swagger-ui cannot access JS scripts. This seems to be similar problem, maybe it will help you.
The current HelloWorld example on websharper.com doesn't work anymore due to changes made in WebSharper 3.4. It now requires some attributes and other stuff to compile correctly.
I am just getting started with WebSharper and I would like to see a minimum (html+javascript client-side hello world) example that works. Any help would be appreciated!
The samples on the website use Html.Client (the HTML language soon to be retired in favor of UI.Next), so to run them you need to start from a template that isn't based on UI.Next.
Following the instructions here, I was able to run them without any issues, extra attributes, etc.
trigger.io;
after upgrading to launchimage module 2.1 I just get error 'Validation failed for module 'launchimage' with error: ipad'
any ideas what this error is about?
the old docs were really good, providing a very clear spec:
http://legacy-docs.trigger.io/en/v1.4/modules/launchimage.html
the new docs for version 2.1 are totally opaque:
https://trigger.io/modules/launchimage/current/docs/index.html
n.b. apologies for posting this to SO - its basically a trigger.io support request
I believe this error indicates that you haven't filled out the public lauchimage module in its entirety like this.
If you are packaging the app as universal I think you'll need to have all the fields filled out as Trigger then prepares your ipa for all platforms(iPad and iPhone).
I found its easiest to just ignore the docs, create a demo project and use the trigger.io toolkit app to generate example config - prevents toolkit app from overwriting existing app config.
have to say I'd way prefer to work from the documentation and edit json config files directly rather than spend my time going through tedious point-and-click config..