immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-07-25 14:00:45 +03:00
Code Issues 783 Packages Projects Releases 22 Wiki Activity

Backup on mobile stops when encountering unsupported formats instead of skipping them #4191

New Issue
Closed
opened 2026-02-05 09:51:07 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 09:51:07 +03:00
Owner
Copy Link

Originally created by @toorux on GitHub (Aug 31, 2024).

The bug

There are some .pic format photos in my iPhone album that cannot be backed up, and the app stops the backup process completely when encountering these photos. I have to delete the .pic format photos from my album to resume the backup, which is very inconvenient. Synology Photos automatically skips such files when it encounters this issue, which I believe is a more reasonable approach. Of course, I would prefer if the app could support the .pic format.

The OS that Immich Server is running on

Docker

Version of Immich Server

v1.113.0

Version of Immich Mobile App

v1.113.0

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

irrelevant

Your .env content

irrelevant

Reproduction steps

  1. Save a picture in pic format in a photo album
  2. Backup this album in the immich app
  3. When the backup reaches this pic, it will indicate that the format is not supported and stop the backup.

Relevant log output

No response

Additional information

No response

Originally created by @toorux on GitHub (Aug 31, 2024). ### The bug There are some .pic format photos in my iPhone album that cannot be backed up, and the app stops the backup process completely when encountering these photos. I have to delete the .pic format photos from my album to resume the backup, which is very inconvenient. Synology Photos automatically skips such files when it encounters this issue, which I believe is a more reasonable approach. Of course, I would prefer if the app could support the .pic format. ### The OS that Immich Server is running on Docker ### Version of Immich Server v1.113.0 ### Version of Immich Mobile App v1.113.0 ### Platform with the issue - [ ] Server - [ ] Web - [X] Mobile ### Your docker-compose.yml content ```YAML irrelevant ``` ### Your .env content ```Shell irrelevant ``` ### Reproduction steps 1. Save a picture in pic format in a photo album 2. Backup this album in the immich app 3. When the backup reaches this pic, it will indicate that the format is not supported and stop the backup. ### Relevant log output _No response_ ### Additional information _No response_
OVERLORD commented 2026-02-05 09:51:12 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Aug 31, 2024):

Can you help with the step to produce the .pic format?

@alextran1502 commented on GitHub (Aug 31, 2024): Can you help with the step to produce the .pic format?
OVERLORD commented 2026-02-05 09:51:16 +03:00
Author
Owner
Copy Link

@toorux commented on GitHub (Aug 31, 2024):

Can you help with the step to produce the .pic format?

@alextran1502 I'm not sure why the images in my photo album are in pic format, as they were saved through another app. If necessary, I can send you one, but I'll need your email address.

@toorux commented on GitHub (Aug 31, 2024): > Can you help with the step to produce the .pic format? @alextran1502 I'm not sure why the images in my photo album are in pic format, as they were saved through another app. If necessary, I can send you one, but I'll need your email address.
OVERLORD commented 2026-02-05 09:51:18 +03:00
Author
Owner
Copy Link

@Cohinem commented on GitHub (Aug 31, 2024):

This also happens to me. I would expect it to write the error and continue on with the backup at least.

This is me trying several times. different 'extension' but the same error. I can (and probably will) go and try to find these among tens of thousands of photos to rename them (to .jpg) and avoid the error. but it should really be fixed.

[Nest] 17  - 08/31/2024, 5:32:14 PM   ERROR [Api:AssetMediaService] Unsupported file type obfuscated.jpg_large
[Nest] 17  - 08/31/2024, 5:33:25 PM   ERROR [Api:AssetMediaService~gj3ca4rd] Unsupported file type obfuscated.jpg_large
[Nest] 17  - 08/31/2024, 5:34:02 PM   ERROR [Api:AssetMediaService~2bgzx03r] Unsupported file type obfuscated.jpg_large
[Nest] 17  - 08/31/2024, 5:34:20 PM   ERROR [Api:AssetMediaService] Unsupported file type obfuscated.jpg_large
@Cohinem commented on GitHub (Aug 31, 2024): This also happens to me. I would expect it to write the error and continue on with the backup at least. This is me trying several times. different 'extension' but the same error. I can (and probably will) go and try to find these among tens of thousands of photos to rename them (to .jpg) and avoid the error. but it should really be fixed. ``` [Nest] 17 - 08/31/2024, 5:32:14 PM ERROR [Api:AssetMediaService] Unsupported file type obfuscated.jpg_large [Nest] 17 - 08/31/2024, 5:33:25 PM ERROR [Api:AssetMediaService~gj3ca4rd] Unsupported file type obfuscated.jpg_large [Nest] 17 - 08/31/2024, 5:34:02 PM ERROR [Api:AssetMediaService~2bgzx03r] Unsupported file type obfuscated.jpg_large [Nest] 17 - 08/31/2024, 5:34:20 PM ERROR [Api:AssetMediaService] Unsupported file type obfuscated.jpg_large ```
OVERLORD commented 2026-02-05 09:51:20 +03:00
Author
Owner
Copy Link

@MattKayDev commented on GitHub (Sep 11, 2024):

I've had this happen as well.

The current work around is restarting backup manually, but that's not ideal.

@MattKayDev commented on GitHub (Sep 11, 2024): I've had this happen as well. The current work around is restarting backup manually, but that's not ideal.
OVERLORD commented 2026-02-05 09:51:22 +03:00
Author
Owner
Copy Link

@saqwerty commented on GitHub (Sep 16, 2024):

I got the the same one and It's blocking the backup process...
[Nest] 17 - 09/16/2024, 6:43:18 PM DEBUG [Api:LoggingInterceptort5ftov5j] GET /api/server/storage 200 0.38ms ::ffff:192.168.11.100
[Nest] 17 - 09/16/2024, 6:43:18 PM DEBUG [Api:LoggingInterceptorctilkrjp] GET /api/assets/device/876c5471dcdf3a27e48b78b4514d56b2bbfe27f1732b7e5d3f3ef5b4ab6f647a 200 54.55ms ::ffff:192.168.11.100
[Nest] 17 - 09/16/2024, 6:43:18 PM ERROR [Api:AssetMediaService0f6bwcdz] Unsupported file type IMG_20240409011411932
[Nest] 17 - 09/16/2024, 6:43:18 PM DEBUG [Api:LoggingInterceptor0f6bwcdz] POST /api/assets 201 0.92ms ::ffff:192.168.11.100
[Nest] 17 - 09/16/2024, 6:43:18 PM VERBOSE [Api:LoggingInterceptor0f6bwcdz] {"deviceAssetId":"3F885CE0-35A1-4DA7-9F80-73A25B49228D/L0/001","deviceId":"876c5471dcdf3a27e48b78b4514d56b2bbfe27f1732b7e5d3f3ef5b4ab6f647a","fileCreatedAt":"2024-04-08T17:14:11.000Z","fileModifiedAt":"2024-04-09T03:15:41.000Z","isFavorite":"false","duration":"0:00:00.000000"}
[Nest] 17 - 09/16/2024, 6:43:18 PM DEBUG [Api:GlobalExceptionFilter0f6bwcdz] HttpException(400): {"message":"Unsupported file type IMG_20240409011411932","error":"Bad Request","statusCode":400}

@saqwerty commented on GitHub (Sep 16, 2024): I got the the same one and It's blocking the backup process... [Nest] 17 - 09/16/2024, 6:43:18 PM DEBUG [Api:LoggingInterceptor~t5ftov5j] GET /api/server/storage 200 0.38ms ::ffff:192.168.11.100 [Nest] 17 - 09/16/2024, 6:43:18 PM DEBUG [Api:LoggingInterceptor~ctilkrjp] GET /api/assets/device/876c5471dcdf3a27e48b78b4514d56b2bbfe27f1732b7e5d3f3ef5b4ab6f647a 200 54.55ms ::ffff:192.168.11.100 [Nest] 17 - 09/16/2024, 6:43:18 PM ERROR [Api:AssetMediaService~0f6bwcdz] Unsupported file type IMG_20240409011411932 [Nest] 17 - 09/16/2024, 6:43:18 PM DEBUG [Api:LoggingInterceptor~0f6bwcdz] POST /api/assets 201 0.92ms ::ffff:192.168.11.100 [Nest] 17 - 09/16/2024, 6:43:18 PM VERBOSE [Api:LoggingInterceptor~0f6bwcdz] {"deviceAssetId":"3F885CE0-35A1-4DA7-9F80-73A25B49228D/L0/001","deviceId":"876c5471dcdf3a27e48b78b4514d56b2bbfe27f1732b7e5d3f3ef5b4ab6f647a","fileCreatedAt":"2024-04-08T17:14:11.000Z","fileModifiedAt":"2024-04-09T03:15:41.000Z","isFavorite":"false","duration":"0:00:00.000000"} [Nest] 17 - 09/16/2024, 6:43:18 PM DEBUG [Api:GlobalExceptionFilter~0f6bwcdz] HttpException(400): {"message":"Unsupported file type IMG_20240409011411932","error":"Bad Request","statusCode":400}
OVERLORD commented 2026-02-05 09:51:24 +03:00
Author
Owner
Copy Link

@loki29pl commented on GitHub (Feb 1, 2025):

I have the same issue, but I have pdf in iCloud photos database

@loki29pl commented on GitHub (Feb 1, 2025): I have the same issue, but I have pdf in iCloud photos database
OVERLORD commented 2026-02-05 09:51:25 +03:00
Author
Owner
Copy Link

@sladg commented on GitHub (Feb 18, 2025):

I'm seeing same issue on iPhone. Immich runs through like 20k of assets without issue and then starts failing on random assets when nearing the finish. It's couple of HEIC photos (tried to sync different albums and got different HEIC file names).

Server will throw following:

 [Nest] 7  - 02/17/2025, 9:33:28 PM   ERROR [Microservices:JobService] Unable to run job handler (thumbnailGeneration/generate-thumbnails): Error: Input file contains unsupported image format
 [Nest] 7  - 02/17/2025, 9:33:28 PM   ERROR [Microservices:JobService] Error: Input file contains unsupported image format
     at Sharp.toBuffer (/usr/src/app/node_modules/sharp/lib/output.js:163:17)
     at MediaRepository.decodeImage (/usr/src/app/dist/repositories/media.repository.js:54:68)
     at MediaService.generateImageThumbnails (/usr/src/app/dist/services/media.service.js:164:63)
     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
     at async MediaService.handleGenerateThumbnails (/usr/src/app/dist/services/media.service.js:114:25)
     at async JobService.onJobStart (/usr/src/app/dist/services/job.service.js:148:28)
     at async EventRepository.onEvent (/usr/src/app/dist/repositories/event.repository.js:130:13)
     at async Worker.processJob (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:394:28)
     at async Worker.retryIfFailed (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:581:24)
 [Nest] 7  - 02/17/2025, 9:33:28 PM   ERROR [Microservices:JobService] Object(2) {
   id: '1f840795-0be4-451b-9071-20ed3eeb3734',
   source: 'upload'
 }

Mobile client won't input any useful logs, it would just stop processing the remaining assets without any warnings/errors in log.

Is it possible for Immich to continue processing and do sth like blacklist for those files? So I can get list of those and remove them manually later from phone? Currently, I would have to tediously one-by-one find the offending file, try to delete, try to re-upload and wait for new file to fail it.

:/ any guidance/help is appreciated

running 1.126.1 and 1.126.1 build 194

@sladg commented on GitHub (Feb 18, 2025): I'm seeing same issue on iPhone. Immich runs through like 20k of assets without issue and then starts failing on random assets when nearing the finish. It's couple of HEIC photos (tried to sync different albums and got different HEIC file names). Server will throw following: ``` [Nest] 7 - 02/17/2025, 9:33:28 PM ERROR [Microservices:JobService] Unable to run job handler (thumbnailGeneration/generate-thumbnails): Error: Input file contains unsupported image format [Nest] 7 - 02/17/2025, 9:33:28 PM ERROR [Microservices:JobService] Error: Input file contains unsupported image format at Sharp.toBuffer (/usr/src/app/node_modules/sharp/lib/output.js:163:17) at MediaRepository.decodeImage (/usr/src/app/dist/repositories/media.repository.js:54:68) at MediaService.generateImageThumbnails (/usr/src/app/dist/services/media.service.js:164:63) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async MediaService.handleGenerateThumbnails (/usr/src/app/dist/services/media.service.js:114:25) at async JobService.onJobStart (/usr/src/app/dist/services/job.service.js:148:28) at async EventRepository.onEvent (/usr/src/app/dist/repositories/event.repository.js:130:13) at async Worker.processJob (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:394:28) at async Worker.retryIfFailed (/usr/src/app/node_modules/bullmq/dist/cjs/classes/worker.js:581:24) [Nest] 7 - 02/17/2025, 9:33:28 PM ERROR [Microservices:JobService] Object(2) { id: '1f840795-0be4-451b-9071-20ed3eeb3734', source: 'upload' } ``` Mobile client won't input any useful logs, it would just stop processing the remaining assets without any warnings/errors in log. Is it possible for Immich to continue processing and do sth like blacklist for those files? So I can get list of those and remove them manually later from phone? Currently, I would have to tediously one-by-one find the offending file, try to delete, try to re-upload and wait for new file to fail it. :/ any guidance/help is appreciated running 1.126.1 and 1.126.1 build 194
OVERLORD commented 2026-02-05 09:51:27 +03:00
Author
Owner
Copy Link

@Cohinem commented on GitHub (Feb 18, 2025):

Currently, I would have to tediously one-by-one find the offending file, try to delete, try to re-upload and wait for new file to fail it.

Thats exactly what I had to do. Anyway if it's just a certain extension then just search for all files with it (.png) for example in the files explorer and rename them all to a different supported extension.

@Cohinem commented on GitHub (Feb 18, 2025): > Currently, I would have to tediously one-by-one find the offending file, try to delete, try to re-upload and wait for new file to fail it. Thats exactly what I had to do. Anyway if it's just a certain extension then just search for all files with it (.png) for example in the files explorer and rename them all to a different supported extension.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#4191
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?