You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've migrated to a new android phone using Samsung SmartSwith. All images were successfuly transfered to a new phone, however Immich shows all images outside default /DCIM/Camera folder under a single date bucket of the current date. Those are from /DCIM/Screenshots, /Pictures, /Snapseed, etc.
Backup is disabled, and backup album selected to Recent.
The OS that Immich Server is running on
Fedora 40
Version of Immich Server
v1.115.0
Version of Immich Mobile App
v1.115.0
Platform with the issue
Server
Web
Mobile
Your docker-compose.yml content
not relevant
Your .env content
not relevant
Reproduction steps
...
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
I don't think it's caused by file content, but attributes, probably file creation date in the filesystem.
I can reproduce this issue, I've deleted all app data and set it up again and those images appear in the same date bucket (yesterday).
The next thing is why those are shown anyway? I thought that only assets from selected backup folders should be shown. Wasn't the behaviour changed recently?
The bug
I've migrated to a new android phone using Samsung SmartSwith. All images were successfuly transfered to a new phone, however Immich shows all images outside default
/DCIM/Camera
folder under a single date bucket of the current date. Those are from/DCIM/Screenshots
,/Pictures
,/Snapseed
, etc.Backup is disabled, and backup album selected to
Recent
.The OS that Immich Server is running on
Fedora 40
Version of Immich Server
v1.115.0
Version of Immich Mobile App
v1.115.0
Platform with the issue
Your docker-compose.yml content
not relevant
Your .env content
Reproduction steps
...
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: