Resolve missing or unexpected results
Start with the message and coverage notes in the app. They distinguish “nothing matched” from “this part could not be checked.”
A provider is missing or a preview is unexpected
- Confirm that you inspected the intended file and check its type in File and UTI Details.
- Review Discovery Coverage. Grant the relevant Applications folder or add the provider’s location through Discovery Folders.
- Use Refresh (Command-R) after installations, updates, removals, or permission changes.
- Read the candidate’s Info details. A broad or ambiguous declaration may not establish which component is responsible.
If a Quick Look preview still fails, a declaration match alone cannot diagnose the renderer’s failure. The inspector does not switch providers, enable them, run their code, or reset macOS’s Quick Look cache.
A folder, recent item, or Reveal action is unavailable
Select a file again with File → Open…. Reselect a discovery root with Re-grant… or Discovery Folders → Add Folder…. Check that the item still exists and that your account can read it. A saved bookmark cannot restore a deleted file or override macOS access restrictions.
Reveal is enabled only when the app has a supported access route. A displayed app identifier or candidate path does not itself grant permission to read that location.
Spotlight metadata is empty or reports another type
Some attributes are unavailable for some files. Compare the evidence in UTI Details with Spotlight’s reported type. Try Refresh, then use a scoped search if you need another check. Empty attributes or a mismatch do not prove that an index is broken. This app does not force reindexing or expose semantic-index readiness.
The on-device model is unavailable
- Use Check Model after choosing a search folder.
- Read the availability reason. Apple Intelligence must be supported and enabled, and the model must be ready on the Mac.
- Review Apple Intelligence settings in macOS System Settings if appropriate. Language, region, asset readiness, and other system conditions can affect availability.
- Use Metadata text search or a supported date query while it is unavailable.
The app’s macOS 26 and Apple silicon requirements do not by themselves guarantee model availability. Apple’s model availability information.
Search is slow, returns nothing, or seems incomplete
- Wrong search area: choose the folder that actually contains the files. The app does not search the entire Mac automatically.
- Slow processing: start with a smaller folder. Long documents, many files, and OCR can take time. Use Cancel if you want to stop.
- Coverage gaps: review read errors, unsupported formats, locked files, and model/content failures. A selected result can be based on partial evidence.
- Unexpected interpretation: inspect the search stages, simplify the question, or try a known filename or phrase in Metadata text search.
- Unexpected “latest” result: inspect the returned dates. Use “created” if you intended creation time, or request an explicit number. Missing dates cannot be guessed.
- Model/context error: try a shorter question. Removing an app-level query limit does not remove the model’s finite context or safety rules.
- Cancelled search: results and coverage may be incomplete. Run the search again to complete it. Copy preserves the incomplete status.
A Spotlight query failure does not stop the filesystem fallback. Results can therefore come from files that were not returned by the index. Conversely, missing results are not proof that a file is unindexed.
Send a useful bug report
Contact support@losko.de. Include the app version, macOS version, what you tried, the expected result, and the error or relevant report section. Mention the search mode and whether the operation completed. Review copied paths and document information before sharing; include a sample file only if you want to share it.