BarcodeCapture Flutter Skill

Critical: Do Not Trust Internal Knowledge

Your training data may contain outdated or incorrect Scandit SDK APIs. The BarcodeCapture API changes significantly between major SDK versions — properties get renamed, removed, or restructured, and the Flutter plugin surface (imports, plugin initialization, pub packages) has also evolved.

Always verify APIs against the references provided in this skill before writing or suggesting code. Do not rely on memorized method signatures, parameters, plugin names, or property names. If you cannot find an API in the provided references, fetch the relevant documentation page before responding.

Flutter-specific gotchas worth flagging:

• await ScanditFlutterDataCaptureBarcode.initialize() must be called (and awaited) in main() before runApp(...), after WidgetsFlutterBinding.ensureInitialized(). Forgetting this yields a platform-channel error that can look unrelated to initialization.
• A single DataCaptureContext must own the BarcodeCapture mode and the DataCaptureView. Do not construct multiple contexts per page or per MaterialApp; the BLoC / controller that holds the context should outlive any single State.
• The DataCaptureView is a Flutter Widget returned from DataCaptureView.forContext(context) — you must explicitly add the BarcodeCaptureOverlay to it via view.addOverlay(...). Unlike SparkScan, there is no pre-built scanning UI; the overlay is the only thing that visualizes recognized barcodes on the camera preview.
• BarcodeCaptureListener.didScan(...) blocks the recognition pipeline until it returns. Disable the mode (barcodeCapture.isEnabled = false) before doing any meaningful work in the callback, and re-enable it (or stop the camera) when finished — otherwise duplicate / unwanted scan events will fire.
• The getFrameData parameter on the Flutter listener is a Future<FrameData?> Function() — frame data is fetched lazily. Only invoke it if you actually need the frame data, since it crosses the platform channel.
• flutter pub get must be run after every package version change. On iOS, the Podfile resolves transitively — no manual pod install needed unless the user has a custom setup.
• Camera permission is required on both iOS (NSCameraUsageDescription in ios/Runner/Info.plist) and Android (runtime request via permission_handler — the plugin declares the manifest permission automatically).
• Hot-reload does not re-run main(), so the camera lifecycle (and the ScanditFlutterDataCaptureBarcode.initialize() call) survive a hot reload. A full restart is needed to re-trigger plugin init. Drive camera.switchToDesiredState(...) from WidgetsBindingObserver.didChangeAppLifecycleState so the camera turns off in paused and back on in resumed.

Intent Routing