[BUG] Android App: Image doesn't load after deleting synced local image outside of app

[maxwai]

The bug

Deleting a local image, outside of the app, that is synced after having opened the app with the image synced, leads to the Image not loading anymore in the App even if it is synced correctly (see pictures at the bottom). On the Website, the images are loaded correctly but the App doesn't download them from the server, maybe thinking they should be available locally.

Even clicking on the image doesn't downloads it.

If the app is not opened between image creation and deletion of the image (so the app was never opened with the image being synced) then the app will correctly get the image from the server when opening after deleting locally.

The OS that Immich Server is running on

Unraid

Version of Immich Server

v1.84.0

Version of Immich Mobile App

v1.84.0 build.108

Platform with the issue

• [ ] Server
• [ ] Web
• [X] Mobile

Your docker-compose.yml content

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: ["start.sh", "immich"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.yml
    #   service: hwaccel
    command: ["start.sh", "microservices"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - /mnt/user/appdata/immich/model-cache:/cache
    env_file:
      - .env
    restart: always

  immich-web:
    container_name: immich_web
    image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release}
    env_file:
      - .env
    restart: always

  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
      # remove this to get debug messages
      - GLOG_minloglevel=1
    volumes:
      - /mnt/user/appdata/immich/tsdata:/data
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3
    restart: always

  database:
    container_name: immich_postgres
    image: postgres:14-alpine@sha256:28407a9961e76f2d285dc6991e8e48893503cc3836a4755bbc2d40bcc272a441
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
    volumes:
      - /mnt/user/appdata/immich/pgdata:/var/lib/postgresql/data
    restart: always

  immich-proxy:
    container_name: immich_proxy
    image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release}
    environment:
      # Make sure these values get passed through from the env file
      - IMMICH_SERVER_URL
      - IMMICH_WEB_URL
    #ports:
    #  - 2283:8080
    depends_on:
      - immich-server
      - immich-web
    restart: always
    networks:
      proxynet:
      default:

networks:
  proxynet:
    external: true

volumes:
  pgdata:
  model-cache:
  tsdata:

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=/mnt/user/immich

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=release

# Connection secrets for postgres and typesense. You should change these to random passwords
TYPESENSE_API_KEY=redacted
DB_PASSWORD=redacted

# 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. Take picture or move image into folder that is synced
2. Let the image sync to the server
3. Open the App (can be done before sync but must be done before next step)
4. Close App
5. Delete the file in another App (File Management App or other gallery App for example)
6. Open Immich App again, the image will not load

Additional information

[chadbaum]

Observing same behavior -- apps opened and positioned by Workspaces are unable to be dragged into a Fancyzone. Closing and re-opening that app manually allows it to snap to a Fancyzone.

[andrewle-xilinx]

Me too — many (but not all[1]) apps launched by the PowerToys Workspaces plugin cannot be subsequently positioned by the FancyZones plugin.

[1]: For instance, I could use FancyZones functionality with an instance of Edge and Outlook launched by Workspaces but not an instance of VS Code.

[BobIMG]

I'm seeing similar. I opened current windows with Workspaces (trying out the new feature). I then noticed the snap-to feature in FancyZones is not working (Win+Arrow Button). I left all windows open, toggled off Workspaces feature in PowerToys and now snap-to features are working as expected.

[Nicola-GitHub]

Observing same behavior here too: apps opened and positioned by Workspaces cannot be dragged into a Fancyzone. Closing and re-opening that app manually allows it to snap to a Fancyzone.

[sk4nner]

Same behaviour here. Since 0.84 no FZ snapping for some (not all) apps launched by Workspaces.

[jamietudor]

Same issue here - multiple apps (Outlook, Chrome, Notepad++, Teams, Thunderbird) cannot be snapped if opened with Workspaces. Fine after a restart.

[jcmarinn]

I see the same issue. When opening apps with Workspaces and then trying to move the windows FancyZones is not working, neither by Shift-Moving or WinKey-> moving (I'm running PowerToys as admin)

[bergamin]

In my case, the issue only happened to Vivaldi. I opened #34641, but closed it in favour of this one, which is older.

Linking it here as it could be useful information for the devs

[bergamin]

Today it also happened to VSCode, on a different layout (the previous one mentioned above also had it but it wasn't affected then)

[den-dog]

Same here. There is a sort of small work-around when you go into powertoys settings for FanzyZones and disable and enbale again:

Override Windows Snap - This overrides the Windows Snap shortcut (Win + arrow) to move windows between zones

So I fancy there is some sort of context loss when activating workspaces, coudl it overide the Fancy zone layout?

[shay-gg]

Yup, having the same problem.

[Alaknar]

Same issue, although it seems I got it a bit more extreme than others - none of the windows opened by Workspaces wants to snap to FancyZones. Restarting (toggling off and back on) either Workspaces or FancyZones doesn't fix anything. Setting "Override Windows Snap" also doesn't work and window behaviour gets very buggy when it's set.

I even restarted PowerToys fully and snapping still doesn't work for apps opened through Workspaces.

[DrSAS]

I've the same problem. My « workaround » is to close the windows opened by workspaces and reopen again 🫠

[charlesarthurrice]

Same, but the one window that would snap to FancyZones was Outlook Classic, which wasn't repositioned when I launched my Workspace. Issue #34651 is about Outlook Classic not being positioned, and it's interesting that it also was the 1 of my 4 apps that would snap to FancyZones after the Workspace launch. The ones that wouldn't snap were One Note, Teams, and Notepad++.

[serivas]

Same here!

[iaing80]

same issue even with 0.84.1

[VArterJr]

Agree with comments here. I did some testing, and it was wild that Outlook Classic is the only Workspaces launched app I've found that still snaps in Fancy Zones. I tested launching my Workspace and saw this issue. Then I killed apps that weren't snapping and manually launched them from Start or PT Run and they worked. It was only after launching from Workspaces, they wouldn't snap.

Example Apps: Outlook Classic, Teams (latest), To Do, VS Code. (Tested with a few others, but only documented with those listed.)

[pbargiona]

Microsoft Word - which has a splash screen when opening - seems to react to Fancy Zones. Google Chrome and Adobe Acrobat - which open directly - do not react to Fancy Zones.

I suspect that Workspaeces is having several troubles with splash screens, as evidenced by #34815 and #34677

Also, I think snapping to the default Windows snapping (sides, quarter-screens etc) should be an option.

The amount of feedback on this amazing feature is a testimony on its immediate success. I thank every developer for their great work!

[howiejc]

Confirmed & reproduced same issue here. It seems that most of the time Outlook 365 (v2407 build 16.0.17830.20210) has the issue but sometimes does work. Every other app I've tested thus far has never worked with FZones when launched via Workspaces.

Does it have something to do with the Workspaces Editor itself also not working with FZones?

[ArtVorushenko]

Same issue, although it seems I got it a bit more extreme than others - none of the windows opened by Workspaces wants to snap to FancyZones. Restarting (toggling off and back on) either Workspaces or FancyZones doesn't fix anything. Setting "Override Windows Snap" also doesn't work and window behaviour gets very buggy when it's set.

I even restarted PowerToys fully and snapping still doesn't work for apps opened through Workspaces.

Can confirm the same experience - zone activation doesn't work for any window opened by Workspaces. Even for 0.84.1.

[Daekar3]

Same issue. v0.84.1, running as admin, Windows 10 22H2.

[Nicola-GitHub]

v0.85.0 fixed the problem for me. Running as admin, Windows 10 22H2. Many thanks to the developers.

[jaimecbernardo]

This issue has been worked on during the 0.85 development cycle. Please update to the latest release.