Skip to content

fix: QR scanner regression — use native getUserMedia#71

Open
BitHighlander wants to merge 1 commit intodevelopfrom
fix/qr-scanner-getUserMedia
Open

fix: QR scanner regression — use native getUserMedia#71
BitHighlander wants to merge 1 commit intodevelopfrom
fix/qr-scanner-getUserMedia

Conversation

@BitHighlander
Copy link
Copy Markdown
Collaborator

Summary

  • Replaced broken ffmpeg/RPC camera pipeline with browser-native getUserMedia API
  • Camera now streams directly to a <video> element — no backend involvement
  • File upload fallback only shown when camera hardware is genuinely unavailable

What broke

The ffmpeg-based camera (spawned from Bun, streamed base64 frames over RPC) was failing silently and falling back to a drag-and-drop file upload UI — useless for QR scanning.

Test plan

  • Open Send form, click QR scan icon — camera should activate immediately
  • Point camera at a wallet QR code — should decode and populate address
  • Cancel button stops camera and closes overlay
  • "Use image file instead" link switches to file upload fallback

…canning

The ffmpeg/RPC approach was failing silently and falling back to a
drag-and-drop file upload, which is unusable for QR scanning. Now uses
the browser's native getUserMedia API directly in the WebView.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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