Skip to content

Frequently Asked Questions

General

How to hide the powered by Regula watermark?

Trial license keys have the powered by Regula watermark by default. Please reach out to our Sales Team to discuss the presence of the watermark on the scanning screen.

How to perform a hologram check?

First of all, turn on the holograms check setting:

DocumentReader.Instance().processParams().checkHologram = true;

For more information, see the Custom Settings page.

DocReader.shared.processParams.checkHologram = true

For more information, see the Custom Settings page.

DocumentReader.Instance().ProcessParams().CheckHologram = (Java.Lang.Boolean)true;

For more information, see the Custom Settings page.

RGLDocReader.Shared.ProcessParams.CheckHologram = true;

For more information, see the Custom Settings page.

DocumentReader.setConfig({
    processParams: {
        checkHologram: true
    },
}, (str) => { console.log(str) }, (error) => { console.log(error) });

For more information, see the Custom Settings page.

DocumentReader.setConfig({
    processParams: {
        checkHologram: true
    },
}, function (m) { }, function (e) { console.log(e); });

For more information, see the Custom Settings page.

DocumentReader.setConfig({
    processParams: {
        checkHologram: true
    }
});

For more information, see the Custom Settings page.

DocumentReader.setConfig({
  "processParams": {"checkHologram": true}
});

For more information, see the Custom Settings page.

Then, after the initialization of the SDK is successfully finished but before starting the camera, choose the processing scenario that supports Document Type recognition, for example:

DocumentReader.Instance().processParams().scenario = Scenario.SCENARIO_FULL_PROCESS;

See the Scenarios page for more details.

DocReader.shared.processParams.scenario = RGL_SCENARIO_FULL_PROCESS

See the Scenarios page for more details.

DocumentReader.Instance().ProcessParams().Scenario = Scenario.ScenarioFullProcess;

See the Scenarios page for more details.

RGLDocReader.Shared.ProcessParams.Scenario = Constants.RGL_SCENARIO_FULL_PROCESS;

See the Scenarios page for more details.

DocumentReader.setConfig({
    processParams: {
        scenario: "FullProcess"
    },
}, (str) => { console.log(str) }, (error) => { console.log(error) });

See the Scenarios page for more details.

DocumentReader.setConfig({
    processParams: {
        scenario: "FullProcess"
    }
}, function (m) { }, function (e) { console.log(e); });

See the Scenarios page for more details.

DocumentReader.setConfig({
    processParams: {
        scenario: "FullProcess"
    }
});

See the Scenarios page for more details.

DocumentReader.setConfig({
  "processParams": {"scenario": ScenarioIdentifier.SCENARIO_FULL_PROCESS}
});

See the Scenarios page for more details.

During the document processing, the flashlight on your device will be turned on by the SDK, you do not need to turn it on yourself. Follow the animation instructions.

When the processing is finished, you will receive the results of the hologram check in the Authenticity Results.

Pick the platform of interest above and navigate to the Authenticity Result section for more details.

Pick the platform of interest above and navigate to the Authenticity Result section for more details.

Pick the platform of interest above and navigate to the Authenticity Result section for more details.

Pick the platform of interest above and navigate to the Authenticity Result section for more details.

Pick the platform of interest above and navigate to the Authenticity Result section for more details.

Pick the platform of interest above and navigate to the Authenticity Result section for more details.

Pick the platform of interest above and navigate to the Authenticity Result section for more details.

Pick the platform of interest above and navigate to the Authenticity Result section for more details.

iOS

Code signing "DocumentReader.framework" failed: Troubleshooting

If the frameworks are integrated to the project manually, you may encounter the issue App Store Connect Operation Error. ERROR ITMS-90087: "Unsupported Architectures" / Code signing failed:

Our frameworks support two architectures for device deployment:

  • arm7, an older variation of the 32-bit ARM CPU, as used in the A5 and earlier.
  • arm64 is the current 64-bit ARM CPU architecture, as used since the iPhone 5S and later, the iPad Air, Air 2 and Pro, with the A7 and later chips.

i386 and x86_64 are used in Simulators.

Although all architectures are useful in some situations, when submitting an app to the App Store, you can only have arm7, and arm64 architectures. If you encounter the error "ERROR ITMS-90087: Unsupported Architectures" or "Code signing failed", it means that you're trying to submit a binary to the App Store, and that this binary has unsupported architectures inside. You have to remove the unsupported architectures (i386 and x86_64) from the binary you're submitting. There are several approaches which are listed below.

The first approach is to remove them manually. Open Terminal inside the framework directory and run the following commands:

lipo -remove i386 -output DocumentReader.framework/DocumentReader DocumentReader.framework/DocumentReader
lipo -remove x86_64 -output DocumentReader.framework/DocumentReader DocumentReader.framework/DocumentReader

The second approach is to run the embedded script (strip-unused-architectures-from-target.sh).

You can verify that the architectures are removed via lipo:

lipo -info DocumentReader.framework/DocumentReader

Android

How to remove unused language resources?

If you are using a library that includes language resources, your APK includes all translated language strings for the messages in those libraries whether the rest of your app is translated to the same languages or not.

If you'd like to keep only the languages that your app officially supports, you can specify those languages using the resConfig property. Any resources for languages not specified are removed.

The following snippet shows how to limit your language resources to just English and Russian:

android {
    defaultConfig {
        ...
        resConfigs "en", "ru"
    }
}

Source: https://developer.android.com/studio/build/shrink-code#unused-alt-resources

Back to top