-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Searching for images in a certain time range does not produce desired images #15151
Comments
Can you please post:
|
Server log during the request:
JSON data of one of the assets:
Partner/sharing: |
Maybe unrelated, but a search for "takenAfter" translates it to a "fileCreatedAt" constraint in a db search immich/server/src/utils/database.ts Line 34 in 8d836ae
I guess this is swapped with "createdAfter" which is translated to "createdAt", which I assume from the context to refer to when the image was taken, but more likely "createdAfter" refers to the file creation date immich/server/src/utils/database.ts Line 31 in 8d836ae
This would not be noticed on setups where the two dates coincide, which is quite frequently the case and only not the case for older images transferred from another system. |
Can you post some of the assets from the screenshot above so we can reproduce and troubleshoot? Please zip them up when you do, thank you! |
The bug
When using the search to select images taken between 1/1/2018 and 1/1/2019, the search shows no result
However, when I navigate to some month in 2018, I clearly find images in immich that are taken in this time range.
This behaviour is either very unintuitive or buggy.
The OS that Immich Server is running on
Ubuntu 24.04
Version of Immich Server
v1.124.0
Version of Immich Mobile App
latest
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
No response
Additional information
All images are in external storage. My other users also report that images without date tag are mixed into ranges incorrectly though I could not reproduce this bevhaviour in my account so far.
The text was updated successfully, but these errors were encountered: