Error: Device not found error. while things seem to still working

Open
#1,986 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust, tauri

Research direction

Start by reproducing the startup behavior in the Cap desktop app on macOS Tahoe using the reported version and check the device-detection path that emits the “Device not found” message. Confirm whether recording still initializes successfully; done means the false error no longer appears when the recorder works, with the existing reproduction steps covered by a regression test if the relevant test location is found.

Written by the indexing model from the issue text.

Description

bug
Description

when i turn on cap.so desktop app, no error message should pop up but I keep on getting this message even though i can still record

Reproduction
  1. I open up cap.so
  2. Immediately get this error:
Image
Additional Context
  • Cap version: Version 0.5.3 (0.5.3)
  • Operating system, version: Macbook air M4 Version Tahoe 26.5.1
  • Device (optional):
Dominant language
Rust
Stars
25k
Forks
2.4k
Avg merge
1d 8h
Merged PRs (30d)
676

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CapSoftware/Cap

All issues in CapSoftware/Cap

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.