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
MOBILE:
A few days ago, archived images started to show up as "not synced" (strikethrough cloud).
The images in question also don't show up in the archive anymore, but rather in the normal timeline.
WEB:
The archived images show up as archived, even the ones that show up as not synced on mobile.
I think this started after the release that contains #7822
# The location where your uploaded files are stored
UPLOAD_LOCATION=./library
# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release
# Connection secret for postgres. You should change it to a random password
DB_PASSWORD=XXX
# The values below this line do not need to be changed###################################################################################
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich
REDIS_HOSTNAME=immich_redis
Reproduction steps
1. Look at archive on mobile. See that there are images missing.
2. Find images in"normal" timeline. See that they are marked as not synced
3. Try to upload the images to get them to a synced state.
4. See that nothing happens.
5. Check on the Web Interface and see that all missing archived images show up in the archive.
Additional information
No response
The text was updated successfully, but these errors were encountered:
The bug
MOBILE:
A few days ago, archived images started to show up as "not synced" (strikethrough cloud).
The images in question also don't show up in the archive anymore, but rather in the normal timeline.
WEB:
The archived images show up as archived, even the ones that show up as not synced on mobile.
I think this started after the release that contains #7822
The OS that Immich Server is running on
Ubuntu 20.04.6
Version of Immich Server
v1.98.2
Version of Immich Mobile App
v1.98.2
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Additional information
No response
The text was updated successfully, but these errors were encountered: