Mobile App does not correctly handle the selected backup folder, if it is/becomes empty.

[monkeyotg]

The bug

If I empty the selected backup folder on my mobile phone, then Immich App will kick this folder out of the backup folder list.
Like the screenshots show in the below.

Now "Camera" is selected and there are 4 photos in it.

Then I have deleted all the photos in "Camera"

even you can't select a folder as backup folder if it is currently empty.

The OS that Immich Server is running on

Docker Desktop on Windows

Version of Immich Server

v1.97.0

Version of Immich Mobile App

v1.97.0

Platform with the issue

• Server
• Web
• Mobile

Your docker-compose.yml content

nothing special, default version with customized port number

Your .env content

nothing special, default version with customized path

Reproduction steps

1.just delete all the photos in the selected backup folder

Additional information

This bug is not just introduced recently, it exists already long time. But I can't remember the start-point.

[melvinsh]

+1 on iOS. I regularly empty my photos app and this behaviour is not good. My current workaround is to always keep one photo in the album.

[monkeyotg]

+1 on iOS. I regularly empty my photos app and this behaviour is not good. My current workaround is to always keep one photo in the album.

I do the same 😁😅

[sadorowo]

i also have this issue.

[alextran1502]

Alright, will fix 😁

[deverton]

I'm still seeing this issue on Android using Immich v1.113.1. It also seems to turn off the foreground and background backup settings completely when the underlying folder is removed from the file system.

[sadorowo]

can confirm.

[caetanoange]

still having the same issue on Android :(

[jdrewsteiner]

Still experiencing this on Android with app version 1.121.0 build .168, server version 1.121.0

[shalamigri]

Why was this closed? I can confirm that this problem is still present on my android phone.

[Arnoud-B]

Can confirm this is also still an issue on iOS.

[nchevsky]

The fix was reverted in #15461. This issue should've been reopened when that reversal was merged. 😞 Issue reopened!

[pjolivon]

+1