v0.24.5

[simulot]

This release aims to resolve the persistent Internal Server Error issue. Using user logs, I have identified the following causes for these errors:

Motion Picture Movie Errors

The MVIMG*.jpg file contains an embedded MP4 used by Immich for moving images. For compatibility, smartphones also create a MP4 file. Immich extracts the embedded MP4 file and stores it. When the MP4 is uploaded, Immich detects it as a duplicate, occasionally causing a server-side error during metadata updates by Immich-go. This error halted Immich-go.

This issue is resolved by ignoring MVIM*.MP4 files.

Duplicated Files with Different Names

Immich-go does not detect multiple copies of the same file with different names. It attempts to upload each copy, and Immich identifies the duplication. This scenario was not properly handled by Immich-go, leading to repeated tagging attempts. Although not critical, this sometimes results in an internal error, leaving some photos untagged.

A temporary patch has been applied to address this issue while awaiting a more robust solution.

Next Steps

I am awaiting user reports confirming the problem's resolution. If errors persist, please run Immich-go with the options --log-level=DEBUG --api-trace and set Immich's log level to DEBUG. Additionally, set the immich's environment variable IMMICH-LOG-LEVEL to debug (read more here).

Thank you for your support.

• 2500+ ⭐
• 34K+ downloads

Changelog

• a55850b feat: add status constants for asset management created, duplicate, replaced
• c25529d feat: add test cases and sample data for handling duplicate files during upload
• ef09237 feat: update upload and replace asset functions to return duplicate status and avoid tagging assets several time fixes: Fail to bulk tag assets #784
• 40b01f6 fix: change error log to warning when UI mode initialization fails
• 68730fb fix: ignore MVIMG files to prevent upload errors Fixes Fail to update MVIMG*.MP4 #786

---

This discussion was created from the release v0.24.5.