The situations that actually happen, grouped by where you see them.
Tap Open Opensolr Photos. This happens when Android has not verified the app link yet, right after installing, or with a debug build.
The sign-in must finish within 15 minutes, on the phone that started it. Tap Sign in with Opensolr again.
The account's API key changed or the account is not active. Sign in again; your index is untouched.
Every phone uses one index. Delete an index you no longer use in the control panel, or upgrade, then tap Try again.
This phone's index belongs to a different account. Sign in with that account, or delete the index from it first.
The index took longer than usual to reload. Wait a minute and tap Try again, or run a Force Re-Sync.
Open the Sync screen. If a sync is running, they are on their way. Otherwise check the photo's folder is ticked under Folders being indexed, then Force Re-Sync.
Only one sync runs at a time. It finishes on its own; follow it on the Sync screen.
New photos wait for next month's allowance or an upgrade. Everything already indexed stays searchable.
The index is over a limit of the plan and Opensolr closes it until it is back under. Upgrade, or wait for the monthly bandwidth reset.
The index had disappeared from the account and was created again. It refills on its own, from the phone's cache, without AI requests for photos read before.
They could not be decoded on the phone or were refused by the reader, usually damaged files or unusual formats. They are tried again at every Re-Sync.
The plan does not include vector search, or this month's AI requests are used up. The note above the results says which.
The photo has no GPS data, or photo-location access was not allowed when it was indexed. Allow it in Android settings; photos indexed from then on carry their place.
It was deleted or moved. The next Re-Sync removes it from the index.
Still stuck? Account and plan questions go to opensolr.com/contact; problems with the app itself belong on GitHub issues.