Skip to main content

FAQ

General#

Trial#

My app stopped working.

Solution: Please check if the license key is correctly set in your app. You can find information on how to do that in the “Get Started” section of the corresponding Scanbot SDK documentation for your platform. Furthermore, please make sure your trial license has not expired yet.


Your example app crashes after some time / after x images.

Solution: Our example apps do not contain a Scanbot SDK license key and run in a trial mode (trial period of 1 minute). After the trial period is over the Scanbot SDK functions will stop working. The UI components (like Scanning UI) will stop working or may be terminated. You have to restart the app to get another trial period.

DPI vs Resolution#

Do I need high DPI values?

DPI is not relevant when creating image files like JPG or PNG. It’s all about resolution (pixels) when working with image files. The image resolution simply depends on the camera device. The quality (resolution) of an image file is not affected by the DPI value. The DPI value is just meta-data stored in the image header. The cameras of all iOS and Android devices store 72 DPI values in the JPG image header files (since 72 DPI is an old standard for web images). The Scanbot SDK does not use this value in any way when creating or modifying scanned image files. The DPI value only matters when you want to print an image on paper. However, you can also specify (or overwrite) the desired DPI value when sending an image file to a printer.

App size#

Adding your SDK to my Android app drastically increase the size of my app.

Solution: Please check your ABI Settings - see our docs. Each ABI contains native lib files and increases the APK size. We recommend to support “arm64-v8a” and “armeabi-v7a” in any case. Support for “x86” or “x86_64" highly depends on your use case. If you are developing a B2C app and don’t have some special (in-house) enterprise devices like Zebra, you can remove these architectures from the release/production build and keep them only for your CI/test/debug build. You can control this via Gradle. If you have to support all of these architectures or in general want to optimize the size of the final APK, we highly recommend going with the new “Android App Bundle” approach. The ARM 64-bit architecture (“arm64-v8a”) is the most common one. ARM 32-bit architecture (“armeabi-v7a”) is the old one and deprecated. It is used by some very old devices like Samsung Galaxy S3, etc. “x86" and “x86_64” are typically used on emulators, but also on some older or very rare Android devices. Furthermore, some enterprise Android tablets like Zebra, or some Chromebooks are based on “x86" or “x86_64”. However, most of them are also compatible with the ARM architecture. So it’s up to you to choose which devices ( architectures/ABIs) you need to support.

Specific#

Android#

I am getting the error: android.view.InflateException: Binary XML file line #8: Binary XML file line #8: Error inflating class net.doo.snap.camera.ScanbotCameraView

Solution: Please ensure that the Scanbot SDK is initialized before using any UI components like ScanbotCameraView or other SDK functions.


I got a (trial) license key and integrated it in my app. But now the app crashes.

OR

I am getting the error: A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 6627 ...

Solution: Please make sure the application ID (on Android) or bundle ID (on iOS) of your app matches the license keys we generated for you. If you are testing our example apps with your license key, please adjust the application/bundle ID accordingly.

Please also make sure you have inserted the license key string exactly as provided in the license file. The line breaks \n in the license key string are important and may not be removed.


I'm getting the error Java.Lang.UnsatisfiedLinkError: No implementation found for long io.scanbot.sdk.core.contourdetector.ContourDetector.ctor() (tried Java_net_doo_snap_lib_detector_ContourDetector_ctor and Java_net_doo_snap_lib_detector_ContourDetector_ctor__) occurred

Solution: Please adjust the Android ABI settings of your project. Then, clean and rebuild the project, remove the debug app from the device, and reinstall it.


I'm getting the error: android.view.InflateException: Binary XML file line #8: Binary XML file line #8: Error inflating class io.scanbot.sdk.camera.ScanbotCameraView

Solution: Please ensure that the Scanbot SDK is initialized before using any UI components like ScanbotCameraView or other SDK functions.


I am getting the error: No version of NDK matched the requested version XX.X.XXXXXXX

Solution: To install the compatible NDK in Android Studio for Scanbot SDK, do the following:

  1. Open "Preferences" in Android Studio and navigate to "Android SDK".
  2. In the tab "SDK Tools" activate the checkbox "Show Package Details".
  3. Select the desired NDK version XX.X.XXXXXXX and install it.

alt

Xamarin#

SBSDK properties are null

This issue is a race condition inside Xamarin Forms. It may happen on both iOS and Android, depending on the device's hardware as well as the Xamarin Forms version.

Solution: Force registration of native dependencies. Please add the following lines to your MainActivity and AppDelegate, respectively:

ScanbotBarcodeSDK.Forms.Droid.DependencyManager.Register();
ScanbotBarcodeSDK.Forms.iOS.DependencyManager.Register();