Skip to content
Phosor
Internal Beta

Common Problems

Beta Status

Phosor is currently in an Internal Beta stage. Features may change before the public release. Performance may occasionally be inconsistent depending on hardware, image formats, and library size. Unexpected bugs may still occur. Feedback from beta testers is highly appreciated.

This page covers common issues you may encounter while using Phosor and how to resolve them.

Photos Don't Appear After Opening a Folder

Symptom

You open a folder, but no photos appear in the viewer.

Possible Causes & Solutions

  1. Unsupported file formats
  2. Phosor only supports JPEG, PNG, WebP, TIFF, and certain RAW formats.
  3. See Supported Formats for the full list.

  4. Unsupported formats (HEIC, AVIF, BMP, GIF, etc.) are silently skipped.

  5. No supported files in the folder

  6. If the folder contains zero supported files, a notification appears and the previous source folder is preserved.

  7. Check the notification at the bottom of the screen.

  8. Permission issues

  9. Filesystem errors during traversal (e.g., permission denied on a subdirectory) are silently skipped.

  10. Ensure Phosor has read access to the folder and all subdirectories.

  11. Deeply nested folders

  12. Scanning very large folders (thousands of files) may take a few seconds.
  13. Wait for the scan to complete.

Symptom

Photos take a long time to load, or navigation stutters during rapid key presses.

Possible Causes & Solutions

  1. Large JPEG files
  2. Very large JPEG files may cause memory spikes.

  3. See Performance for details.

  4. Large RAW files

  5. Large or high-resolution RAW files may take longer to load.

  6. See Performance for details.

  7. Memory pressure

  8. Background memory use is automatically limited, but very large collections may still cause slowdowns.
  9. See Performance for mitigation strategies.

Categories Reset After Restart

Symptom

Your category names, colors, keybindings, and output folders are gone after restarting Phosor.

Cause

Category configuration is not persisted between sessions. Each launch starts with two default categories.

Known limitation

This is a current limitation. Persisting category configuration is planned. See the Roadmap for details.

Undo/Redo Not Working

Symptom

Undo or redo doesn't seem to do anything.

Possible Causes & Solutions

  1. During Execute
  2. Undo and redo are blocked during the Execute (move) operation.

  3. Wait for the move to complete, then try again.

  4. No actions to undo

  5. Only sorting actions (assign and clear flag) are recorded.

  6. Navigation is not recorded in the undo history.

  7. History limit reached

  8. The undo history supports up to 100 entries.

  9. Older actions are discarded after 100 entries.

  10. New folder opened

  11. The undo history is cleared when a new folder is opened.

Toast Notifications Not Appearing

Symptom

No toast notifications appear at the bottom of the screen.

Possible Causes & Solutions

  1. Development mode
  2. Debug toasts (prefixed with "[DEBUG]") are only visible in development mode.

  3. Regular toasts should always appear.

  4. Single toast at a time

  5. Only one toast is visible at a time. New toasts replace the current one.
  6. If you're sorting rapidly, you may not see individual toasts.

Symptom

A modal dialog appears but doesn't respond to keyboard input.

Possible Causes & Solutions

  1. Focus trapping
  2. Tab navigation is trapped within the modal for accessibility.
  3. Press Tab or Shift+Tab to navigate between buttons.

  4. Press Enter to confirm or Escape to cancel.

  5. Queued modals

  6. Only one modal is visible at a time. Additional requests are queued.
  7. Dismiss the current modal to see the next one.

See Also