FAQ

Common questions about integrating the Code Scanner component.

Is there a fee for the Code Scanner component?

Integrating the Code Scanner component is free.

Charges apply only when you enable log reporting. The log instrumentation and reporting features depend on the Mobile Analysis component, which is a billable service. When log reporting is enabled, the Mobile Analysis component collects scan metrics—including the number of scan attempts, successful scans, and failed scans—to help you monitor scan performance. Charges follow the Mobile Analysis component billing rules. For details, see Pricing of legacy mPaaS component billing items.

To avoid charges, disable log reporting. For instructions, see Log reporting.

The private cloud version of the Code Scanner component is a paid service. Contact our business team for pricing details.

How to initialize mPaaS for an Android project using the native AAR method?

Add the following code to the Application class. If you use the hotpatching feature (QuinoxlessApplication), you do not need to initialize mPaaS.

Call MP.init(this) in the onCreate() method of your Application class. If your project uses the hotpatching feature (QuinoxlessApplication), skip this step—mPaaS is already initialized by QuinoxlessApplication.

public class MyApplication extends Application {
    
    @Override
    public void onCreate() {
        super.onCreate();
        // Initialize mPaaS
        MP.init(this);    
    }
}

For more information, see Initialize mPaaS.

How to resolve freezes when starting the scanner in Android baseline 10.1.68?

When the Code Scanner component coexists with other components in AAR or mPaaS Inside mode, it attempts to load those components synchronously on the main thread if mPaaS is not initialized. This causes the main thread to freeze.

To fix this, call MP.init(this) in your Application class before the scanner starts. This ensures all components load during app startup rather than on-demand on the main thread.