Repository navigation
Troubleshooting
No scanner found. Switch the scanner on and check the USB cable (a hub reset can drop it; it happened during development). Press Look again. If macOS offers to install Rosetta for the vendor driver, accept it and relaunch EasyScan. Image Capture's daemon does not retry a failed driver launch by itself.
"The scanner is in use by another app." Vendor drivers such as Samsung's allow a single session. Quit Image Capture, Preview, or another copy of EasyScan. SANE and the Image Capture driver cannot hold the USB device at the same time either; EasyScan releases its own session after a minute of inactivity.
Everything stopped after a macOS upgrade. Vendor scanner modules in /Library/Image Capture/Devices are Intel-only and need Rosetta. When Rosetta is no longer available, install SANE (brew install sane-backends) and EasyScan switches to it on its own.
Color scans crash Image Capture but work in EasyScan. Expected. The driver scans in color; the Image Capture app is what crashes.
Diagnosing a driver that will not start. The useful log is the Image Capture device daemon:
log show --last 1h --predicate 'process == "icdd" AND eventMessage CONTAINS "launchModule"'A line ending in Launch Failed with NSCocoaErrorDomain code 256 means LaunchServices refused to start the module, typically because Rosetta is missing.
Scans land in an odd folder after running --selftest. They should not: the self-test restores your settings and never persists its temporary folder. If it ever does, choose the folder again with ⇧⌘D.