OBLS-822 Disable DataWedge keystroke output for barcode inputs

[jmiranda]

Fixes the duplicate/doubled barcode value on scan (OBLS-822), a regression from the intent-based scan capture in #423.

Problem

A scan was delivered through two DataWedge channels at once:

• Intent output → useScanListener → onChange(value) (the path added in OBLS-822 Capture DataWedge scans via intent broadcast #423), and
• Keystroke output → the barcode typed into the focused field as key events.

Because keystroke typing is additive and the intent onChange replaces, the two concatenate: the scanned string is appended to itself. Confirmed on TC52 and TC53e — a scan of 4354210 submitted as 43542104354210, and ABP N60C IQ3980 as ABP N60C IQ3980ABP N60C IQ3980.

It did not reproduce on a TC20, which is the tell: the app never explicitly controlled keystroke output — configureProfileOnce() only sets the BARCODE and INTENT plugins (CONFIG_MODE: 'UPDATE'), leaving the Keystroke plugin at each device's default. So whether both channels fire (and whether they concatenate, which also depends on intent-vs-keystroke delivery timing) was left to per-device DataWedge state.

Fix

Explicitly control keystroke output so behavior is deterministic across devices. Keystroke output is a profile-wide setting (the OPENBOXES profile is associated with every activity) and can't be scoped to a single field, so it's toggled at runtime:

• Muted while any barcode input (useScanListener consumer) is active → the scan arrives only via the intent broadcast, never also typed into the field.
• Restored when no barcode input is active → plain inputs elsewhere can still be populated by scanning.

The active-consumer count is reference-counted so overlapping inputs (e.g. a screen input and a modal input during a dialog transition) keep it muted until the last one unmounts.

Manual keyboard entry is unaffected — keystroke_output_enabled controls only the scanner's keystroke emulation, not the soft keyboard.

Scope

• src/hooks/constant.ts — getKeystrokeOutputConfig(enabled) (KEYSTROKE plugin config).
• src/hooks/useScanListener.ts — reference-counted keystroke mute/restore around the existing intent subscription. No change to the subscription model otherwise.

Testing

Built locally (./gradlew assembleRelease) and sideloaded to a TC52: the doubling is gone — scans on the Inbound Sortation screen now apply the value once. Manual typing into scan fields still works.

🤖 Generated with Claude Code

---

Generated by Claude Code

[Copilot]

Pull request overview

This PR addresses duplicated/doubled barcode values on Zebra devices by explicitly managing DataWedge’s Keystroke output at runtime, ensuring scans are delivered only through the existing intent broadcast path while scan listeners are active.

Changes:

• Adds a DataWedge KEYSTROKE plugin config generator (getKeystrokeOutputConfig) to toggle keystroke_output_enabled.
• Updates useScanListener to reference-count active scan consumers and mute/unmute keystroke output when consumers mount/unmount.
• Keeps the intent-based scan subscription model from #423, adding keystroke control around it.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
src/hooks/useScanListener.ts	Adds reference-counted keystroke mute/restore around the existing DataWedge intent listener.
src/hooks/constant.ts	Adds KEYSTROKE plugin config builder used to toggle DataWedge keystroke output.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.