Open rgommezz opened 3 years ago
matvidako
commented
3 years ago Hi,
you're correct, SDKs share some of the classes and that is why you can't simply include both dependencies. However, we have a solution that includes some features from BlinkInput into BlinkID SDK. VIN recognizer is included so it covers your use case. To get access, you'll have to contact our support at support@microblink.com.
rgommezz
commented
3 years ago Hello @matvidako,
Thanks for the prompt response, I got the custom package.
I am able to scan VIN inside documents with a document overlay, but not as text OCR with a text overlay (see screenshot below).
It seems it doesn't incorporate react native wrappers for FieldByFieldScan activities/ViewControllers, unless I am missing something.
Does it mean we'd have to extend that custom RN solution ourselves in order to add support for that?
Hello,
I am trying to integrate both BlinkID and BlinkInput products into a React Native application
Environment
I started with blinkID without any issues at all, getting the USDL scan up and running, but once I attempted to install the BlinkInput wrapper for VIN scanning, I got SDK clashes in Android and iOS platforms. You can find the build outputs below.
Is there a way to circumvent this? The classic way of fixing this on Android for instance, is by removing one of the binary dependencies, but that would remove some of the particular classes needed by either of the two. It seems both SDKs share some core classes, but since they are packaged up in different JARs, I am not aware of any way to exclude those ones.
For iOS, I still haven't dug into it.
We are currently trialling BlinkID as our main solution for ID and VIN scanning. Unfortunately, if this issue is difficult to address in the short time frame, we'd have to evaluate alternatives.
Let me know if you need more debugging information.
iOS
[!] The 'Pods-myApp' target has frameworks with conflicting names: microblink.framework.Android