Skip to content

fix(android/camera): call Kotlin setters explicitly so auto scan works on napi runtime - #744

Merged
farfromrefug merged 1 commit into
mainfrom
fix/740-auto-capture-not-working
Oct 19, 2026
Merged

farfromrefug merged 1 commit into
mainfrom
fix/740-auto-capture-not-working

Conversation

@farfromrefug

Copy link
Copy Markdown
Collaborator

Summary

Testing

  • Verified on an Android device: auto capture fires with a still document.
  • yarn svelte-check / eslint not run (tooling not installed in the dev checkout). iOS not tested (code path unchanged).
  • Not verified: plugin-nativeprocessor/CropView.ts assigns colors / fillPaint the same way on Android and may be affected; left out of this PR.

Refs #740

…s on napi runtime

Property assignment on Kotlin objects is a silent no-op on the quickjs-ng
napi runtime (reads work), so the auto scan handler was never wired to the
processor. Use set<Name>() on Android, keep property assignment on iOS.

Refs #740

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@farfromrefug
farfromrefug marked this pull request as ready for review October 19, 2026 18:07
@farfromrefug
farfromrefug merged commit 3c90fbb into main Oct 19, 2026
1 check passed
@farfromrefug
farfromrefug deleted the fix/740-auto-capture-not-working branch October 19, 2026 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant