UROVO ScanManager Kotlin example and validation checklist

Prepare a reproducible SDK baseline

Package the approved SDK artifact through the controlled developer-download process. Record its version and SHA-256 alongside the application build and device record.

Keep vendor APIs behind a scanner adapter so business logic can be unit tested without hardware and another capture implementation can be substituted.

• Approved SDK source only
• Artifact hash recorded
• Adapter boundary defined
• Device matrix created

Own the scanner lifecycle once

The API reference documents openScanner, closeScanner, startDecode, stopDecode and output-mode functions. Decide whether the activity, a foreground service or another application-scoped component owns those calls.

Avoid multiple screens opening the scanner independently. Make stop and close safe to repeat and surface failed return values in diagnostic state without logging barcode payloads.

• Single resource owner
• Idempotent cleanup
• Return values observed
• No payloads in ordinary logs

Validate the broadcast payload

A successful decode broadcast can include raw data, a decoded string, length and barcode type. Check action, nullability and length before delivering a domain event.

Choose one authoritative representation. If encoding matters, preserve raw bytes and decode under an explicit charset instead of assuming every barcode is simple ASCII.

• Action exactly matches
• Length consistent with payload
• Encoding policy documented
• Duplicate event guard

Move from demo to production evidence

Compile success proves only source compatibility. Run the application on each intended model, OS and firmware with representative labels and lifecycle scenarios.

Record scanner settings and the output mode after configuration. Regression-test after firmware, SDK, application or MDM policy changes.

• Representative scan corpus
• Sleep and resume cycles
• Rapid and long-code cases
• Versioned test record

Minimal lifecycle-aware Kotlin example

Verify output-mode constants, Android receiver flags and lifecycle ownership against the exact SDK, target API and application architecture.

import android.content.BroadcastReceiver
import android.content.Context
import android.content.Intent
import android.content.IntentFilter
import android.device.ScanManager
import androidx.appcompat.app.AppCompatActivity

class UrovoScannerActivity : AppCompatActivity() {
    private val scanner = ScanManager()
    private var receiverRegistered = false

    private val decodeReceiver = object : BroadcastReceiver() {
        override fun onReceive(context: Context, intent: Intent) {
            if (intent.action != ScanManager.ACTION_DECODE) return
            val raw = intent.getByteArrayExtra(ScanManager.DECODE_DATA_TAG) ?: return
            val declaredLength = intent.getIntExtra(ScanManager.BARCODE_LENGTH_TAG, raw.size)
            val type = intent.getByteExtra(ScanManager.BARCODE_TYPE_TAG, 0)
            val value = intent.getStringExtra(ScanManager.BARCODE_STRING_TAG)
                ?: raw.copyOf(declaredLength.coerceIn(0, raw.size)).toString(Charsets.UTF_8)
            onValidatedScan(value, type)
        }
    }

    override fun onStart() {
        super.onStart()
        check(scanner.openScanner()) { "Scanner could not be opened" }
        // Confirm the broadcast-output constant in the SDK version you ship.
        check(scanner.switchOutputMode(0)) { "Output mode could not be set" }
        registerReceiver(decodeReceiver, IntentFilter(ScanManager.ACTION_DECODE))
        receiverRegistered = true
    }

    override fun onStop() {
        scanner.stopDecode()
        if (receiverRegistered) unregisterReceiver(decodeReceiver)
        receiverRegistered = false
        scanner.closeScanner()
        super.onStop()
    }

    private fun onValidatedScan(value: String, type: Byte) {
        // Route a sanitized domain event; do not log sensitive barcode values.
    }
}

ScanManager validation checklist

Attach this record to the approved application and device baseline.

1. 01

   SDK version and SHA-256 recorded

2. 02

   Device SKU, OS and firmware recorded

3. 03

   Scanner opens and closes repeatedly

4. 04

   Output mode read or confirmed

5. 05

   Receiver lifecycle matches active UI

6. 06

   Raw, string, length and type extras checked

7. 07

   All required symbologies tested

8. 08

   Long, damaged and rapid scans tested

9. 09

   Sleep, reboot and MDM kiosk mode tested

10. 10

    No sensitive barcode data logged

Frequently asked questions