Does this match your problem?
- The indexed-photo counter stops changing for an extended period.
- The app exits while building a large library index.
- A later run appears to pause around a similar count.
- The phone becomes warm and iOS slows or interrupts the work.
Likely causes
Memory pressure
Core ML image encoding is demanding, especially with tens of thousands of assets. Public issues #41 and #47 document crashes on unusually large libraries.
Low Power Mode or thermal pressure
The current index screen explicitly asks users to disable Low Power Mode for more than 300 pending photos. iOS can also reduce sustained work when the device is hot.
Checkpoint work
The current source appends accumulated embeddings periodically. A pause near a checkpoint is not automatically a deadlock; storage work can take time on a very large index.
One repeatable asset or system condition
If every run fails at the same visible photo or count, capture that evidence. Do not delete the original merely to test a theory.
Recovery steps, in order
Wait for a real stall
Keep Queryable in the foreground and avoid interacting with the index screen. A brief pause while saving a checkpoint is expected; look for a counter that remains unchanged for an unusually long interval.
Reduce resource pressure
Connect the iPhone to power, turn off Low Power Mode, let the device cool, confirm there is free storage, and close memory-heavy apps before the next attempt.
Resume from the app
If Queryable has closed or the screen explicitly says it is stuck, reopen it and start the remaining index. The app compares the library with saved embedding identifiers and queues only items it still considers unindexed.
Do not reinstall first
Reinstalling removes the local index and forces the whole library through the expensive first pass again. Preserve the existing checkpoint unless support confirms that the index itself is corrupt.
Record a repeatable failure
Note the iPhone model, iOS version, approximate library size, free storage, iCloud Optimize Storage setting, displayed count, last visible image type, and whether the crash repeats after cooling and closing other apps.
When to report it
If three clean retry attempts fail at the same point, open a GitHub issue or email support with the recorded environment and an iOS crash log if available. Do not attach private photos; describe dimensions and media type instead.
Common questions
Will restarting lose the whole Queryable index?
Completed checkpoints are saved locally, so restarting should not require every successfully persisted item to be encoded again. The unfinished portion can repeat.
Should I keep the screen on?
Yes. The current app disables the idle timer during active indexing and asks the user not to operate the screen until completion.
Is there a published maximum library size?
No fixed maximum is stated. Real limits depend on the device, available memory, storage, asset mix and iOS behavior; very large libraries remain an area with open reports.
Evidence used for this guide
This page is based on the current public source and real support reports. Issue reports describe specific devices and versions; they are evidence of observed failures, not proof that every device has the same cause.