Releases: imagegenius/docker-immich
v1.136.0-ig406
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.136.0 - 69420 stars release
Caution
BREAKING CHANGES
IMMICH_MEDIA_LOCATION (#19995)
Note: if you DO NOT have IMMICH_MEDIA_LOCATION in your .env file, or if it is set to a path that starts with a / (absolute path), THIS BREAKING CHANGE DOES NOT APPLY TO YOU. Users of the all-in-one image (e.g., the unraid app) for instance are not affected.
If you have a custom IMMICH_MEDIA_LOCATION environment variable set to a relative path, you will have to do the following process:
- Stop Immich (
docker compose stop): - Update Immich (
docker compose pull) - Update the environment variable to an absolute path, for example:
-IMMICH_MEDIA_LOCATION=./my-library
+IMMICH_MEDIA_LOCATION=/usr/src/app/my-library
- Start Immich (
docker compose up -d --force-recreate) - After the server successfully starts up, connect to it (
docker exec ``*-it*`` immich_server /bin/sh) and runimmich-admin change-media-location. When prompted, enter the appropriate values. For example:
docker exec -it immich_server /bin/sh
$ immich-admin change-media-location
...
? Enter the previous value of IMMICH_MEDIA_LOCATION: ./my-library
? Enter the new value of IMMICH_MEDIA_LOCATION: /usr/src/app/my-library
Previous value: ./my-library
Current value: /usr/src/app/my-library
Changing database paths from "my-library/*" to "/usr/src/app/my-library/*"
? Do you want to proceed? [Y/n] y
Matching database file paths were updated successfully! 🎉
You may now set IMMICH_MEDIA_LOCATION=/usr/src/app/my-library and restart!
Background/Motivation
Relative paths have implied ambiguity, as they depend on the current working directory to resolve correctly, leading to issues like (#4465). This change removes this ambiguity and sets up the project to transition away from files living at /usr/src/app/upload entirely. Currently, the upload folder lives at /usr/src/app/upload/upload, which is very confusing… for everyone. This change opens to door for a future migration to something like IMMICH_DATA=/data, which a more sensible setup.
API Key changes (#20113)
Note: This change may affect the use of third-party applications, such as ImmichGo, ImmichKios, or ImmichFrame.
This release includes a change to how API Keys work, specifically when used with routes that don’t require a specific permission. Previously, a scoped API Key could access these routes, but they will now throw a forbidden error. Routes without a declared scope now implicitly require the “all” permission.
Highlights
Welcome to release v1.136.0. This midsummer release is the culmination of the team's labor of love for the Immich community, featuring the introduction of a new timeline and sync mechanism in beta mode, Android widgets, and one of the last breaking changes we want to make before reaching the stable release milestone. Let’s dive right into it.
- Beta mode for the new timeline, sync, and upload mechanism
- Android widgets
- iOS widget improvements
- Deep links
Beta timeline, sync, and upload mechanism
Note
This is only supported when both the server and the mobile app are updated to v1.136.0
This is a series of work that has been happening for months under the hood, from the changes in the database query engine, server’s queries, and support logic, to integrating a whole new database on the mobile app, and rewriting almost all aspects of the mobile app, you can now try the new timeline with data sync mechanism, and upload rework by go to the App Settings > Toggle the Beta timeline button. After toggling, you will be directed to a screen where data migration is executed automatically. You can then proceed to the new experience.
You can distinguish the beta timeline from the old one by the beta symbol next to the Immich logo in the app bar.
Why?
Over the past year, the major complaints we've received from users have primarily centered around the mobile app. The app simply doesn't feel premium or responsive—it's often janky and takes too long to become usable when first opened, especially when you have a large number of albums. Users can't even view their local albums unless they've selected them as backup targets. Our technical debt in the data structure has created some truly frustrating behaviors, like forcing users to re-upload everything (only to have it rejected by the server) when they switch phones and end up with a different device ID. Or local photos and videos don’t show up until they are all hashed, which could take a while.
We've realized we can't honestly call the application stable or confidently recommend it to everyone until we resolve these fundamental problems. We genuinely want this app to be excellent. We want the user experience to be seamless and delightful—we want you to feel genuinely happy when you open Immich to browse through your precious memories.
What’s new?
Data sync
- The data sync is now running in a background thread, separate from the UI thread. This means that during data synchronization, the app will remain smooth to browse.
- The data sync speed should be improved drastically. The data is being streamed to the mobile app instead of being sent there in a single large chunk. This will help users with a massive library.
- The calculation of which data needs to be retrieved from the server is now performed on the server, rather than being calculated by the mobile app previously. This means lower CPU usage on the mobile app and quicker incremental sync.
- The mobile app will now retrieve data from the server and maintain similar database tables within the app. This restructuring enables better offline operation and supports more complex usage behaviors.
Timeline/Display experience
- The new timeline has been rewritten from the ground up to enhance scrolling and dragging behavior, making it easier for you to navigate the timeline.
- The detail viewer is now more interactive, allowing you to scroll between photos or videos when the bottom detail sheet is opened.
- The album views and other collection views are more lively, featuring a parallax effect to make your album/collection feel alive with mesmerizing animation.
- You can now view all albums on the device, regardless of which album you have selected as the target for backing up. You can view them in the `Library > On this device` section. For users who want to select individual assets to back up to the server, they can perform that operation from here.
Upload
- The upload mechanism has been rewritten from the ground up.
- Upload is now handled by the OS, allowing for a better background upload operation. Instead of handling the uploading ourselves, we are now placing the photos and videos in a queue, which will run continuously when the Immich app is opened in the foreground and for a few minutes after it is put into the background. Then the OS will take over and start pulling tasks from the queue, handling the upload process by itself.
- Starting the upload progress is now invoked from a toggle button
- Uploads are now running in parallel . The new upload detail page displays which assets are being uploaded and whether they are experiencing issues or stuck. You can tap on each item to see exactly which asset is causing the problem.
- On Android, there is no longer a virtual
Recentsalbum that includes all assets. Instead, there is a button to select all albums for backup. - In the backup album selection screen, you can now search for the album you want to back up.
Expectations of the beta version of the mentioned mechanisms
- The app should be very smooth to browse around during the initial login and subsequent app openings.
- Collections (favorite, archived, locked folder, etc.) and album views should make you feel nice, cozy, and delighted.
- Background queuing of newly taken photos is not yet implemented. We will start working on this next.
- Some views are not yet ported over to the new implementation, such as, but not limited to
- People view
- Map view
- Some mechanisms are still missing from the previous implementation, such as, but not limited to
- Add to album from multi-selection
- Album sync when uploading
- There are still some buggy behaviors/animations we will be ironing out in the coming days.
How can you help us?
- Use the beta timeline and the new upload rework.
- Report any bugs and weirdness you experience on GitHub’s issue tracker
[beta] <your-title-here>as the title - Reach out and provide direct feedback on Discord
- Feedback from iCloud users is greatly appreciated
Android Widgets
This is a follow-up to one of our most requested features: Home sc...
Contributors
Assets 2
openvino-v1.136.0-ig105
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.136.0 - 69420 stars release
Caution
BREAKING CHANGES
IMMICH_MEDIA_LOCATION (#19995)
Note: if you DO NOT have IMMICH_MEDIA_LOCATION in your .env file, or if it is set to a path that starts with a / (absolute path), THIS BREAKING CHANGE DOES NOT APPLY TO YOU. Users of the all-in-one image (e.g., the unraid app) for instance are not affected.
If you have a custom IMMICH_MEDIA_LOCATION environment variable set to a relative path, you will have to do the following process:
- Stop Immich (
docker compose stop): - Update Immich (
docker compose pull) - Update the environment variable to an absolute path, for example:
-IMMICH_MEDIA_LOCATION=./my-library
+IMMICH_MEDIA_LOCATION=/usr/src/app/my-library
- Start Immich (
docker compose up -d --force-recreate) - After the server successfully starts up, connect to it (
docker exec ``*-it*`` immich_server /bin/sh) and runimmich-admin change-media-location. When prompted, enter the appropriate values. For example:
docker exec -it immich_server /bin/sh
$ immich-admin change-media-location
...
? Enter the previous value of IMMICH_MEDIA_LOCATION: ./my-library
? Enter the new value of IMMICH_MEDIA_LOCATION: /usr/src/app/my-library
Previous value: ./my-library
Current value: /usr/src/app/my-library
Changing database paths from "my-library/*" to "/usr/src/app/my-library/*"
? Do you want to proceed? [Y/n] y
Matching database file paths were updated successfully! 🎉
You may now set IMMICH_MEDIA_LOCATION=/usr/src/app/my-library and restart!
Background/Motivation
Relative paths have implied ambiguity, as they depend on the current working directory to resolve correctly, leading to issues like (#4465). This change removes this ambiguity and sets up the project to transition away from files living at /usr/src/app/upload entirely. Currently, the upload folder lives at /usr/src/app/upload/upload, which is very confusing… for everyone. This change opens to door for a future migration to something like IMMICH_DATA=/data, which a more sensible setup.
API Key changes (#20113)
Note: This change may affect the use of third-party applications, such as ImmichGo, ImmichKios, or ImmichFrame.
This release includes a change to how API Keys work, specifically when used with routes that don’t require a specific permission. Previously, a scoped API Key could access these routes, but they will now throw a forbidden error. Routes without a declared scope now implicitly require the “all” permission.
Highlights
Welcome to release v1.136.0. This midsummer release is the culmination of the team's labor of love for the Immich community, featuring the introduction of a new timeline and sync mechanism in beta mode, Android widgets, and one of the last breaking changes we want to make before reaching the stable release milestone. Let’s dive right into it.
- Beta mode for the new timeline, sync, and upload mechanism
- Android widgets
- iOS widget improvements
- Deep links
Beta timeline, sync, and upload mechanism
Note
This is only supported when both the server and the mobile app are updated to v1.136.0
This is a series of work that has been happening for months under the hood, from the changes in the database query engine, server’s queries, and support logic, to integrating a whole new database on the mobile app, and rewriting almost all aspects of the mobile app, you can now try the new timeline with data sync mechanism, and upload rework by go to the App Settings > Toggle the Beta timeline button. After toggling, you will be directed to a screen where data migration is executed automatically. You can then proceed to the new experience.
You can distinguish the beta timeline from the old one by the beta symbol next to the Immich logo in the app bar.
Why?
Over the past year, the major complaints we've received from users have primarily centered around the mobile app. The app simply doesn't feel premium or responsive—it's often janky and takes too long to become usable when first opened, especially when you have a large number of albums. Users can't even view their local albums unless they've selected them as backup targets. Our technical debt in the data structure has created some truly frustrating behaviors, like forcing users to re-upload everything (only to have it rejected by the server) when they switch phones and end up with a different device ID. Or local photos and videos don’t show up until they are all hashed, which could take a while.
We've realized we can't honestly call the application stable or confidently recommend it to everyone until we resolve these fundamental problems. We genuinely want this app to be excellent. We want the user experience to be seamless and delightful—we want you to feel genuinely happy when you open Immich to browse through your precious memories.
What’s new?
Data sync
- The data sync is now running in a background thread, separate from the UI thread. This means that during data synchronization, the app will remain smooth to browse.
- The data sync speed should be improved drastically. The data is being streamed to the mobile app instead of being sent there in a single large chunk. This will help users with a massive library.
- The calculation of which data needs to be retrieved from the server is now performed on the server, rather than being calculated by the mobile app previously. This means lower CPU usage on the mobile app and quicker incremental sync.
- The mobile app will now retrieve data from the server and maintain similar database tables within the app. This restructuring enables better offline operation and supports more complex usage behaviors.
Timeline/Display experience
- The new timeline has been rewritten from the ground up to enhance scrolling and dragging behavior, making it easier for you to navigate the timeline.
- The detail viewer is now more interactive, allowing you to scroll between photos or videos when the bottom detail sheet is opened.
- The album views and other collection views are more lively, featuring a parallax effect to make your album/collection feel alive with mesmerizing animation.
- You can now view all albums on the device, regardless of which album you have selected as the target for backing up. You can view them in the `Library > On this device` section. For users who want to select individual assets to back up to the server, they can perform that operation from here.
Upload
- The upload mechanism has been rewritten from the ground up.
- Upload is now handled by the OS, allowing for a better background upload operation. Instead of handling the uploading ourselves, we are now placing the photos and videos in a queue, which will run continuously when the Immich app is opened in the foreground and for a few minutes after it is put into the background. Then the OS will take over and start pulling tasks from the queue, handling the upload process by itself.
- Starting the upload progress is now invoked from a toggle button
- Uploads are now running in parallel . The new upload detail page displays which assets are being uploaded and whether they are experiencing issues or stuck. You can tap on each item to see exactly which asset is causing the problem.
- On Android, there is no longer a virtual
Recentsalbum that includes all assets. Instead, there is a button to select all albums for backup. - In the backup album selection screen, you can now search for the album you want to back up.
Expectations of the beta version of the mentioned mechanisms
- The app should be very smooth to browse around during the initial login and subsequent app openings.
- Collections (favorite, archived, locked folder, etc.) and album views should make you feel nice, cozy, and delighted.
- Background queuing of newly taken photos is not yet implemented. We will start working on this next.
- Some views are not yet ported over to the new implementation, such as, but not limited to
- People view
- Map view
- Some mechanisms are still missing from the previous implementation, such as, but not limited to
- Add to album from multi-selection
- Album sync when uploading
- There are still some buggy behaviors/animations we will be ironing out in the coming days.
How can you help us?
- Use the beta timeline and the new upload rework.
- Report any bugs and weirdness you experience on GitHub’s issue tracker
[beta] <your-title-here>as the title - Reach out and provide direct feedback on Discord
- Feedback from iCloud users is greatly appreciated
Android Widgets
This is a follow-up to one of our most requested features: Home sc...
Contributors
Assets 2
cuda-v1.136.0-ig111
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.136.0 - 69420 stars release
Caution
BREAKING CHANGES
IMMICH_MEDIA_LOCATION (#19995)
Note: if you DO NOT have IMMICH_MEDIA_LOCATION in your .env file, or if it is set to a path that starts with a / (absolute path), THIS BREAKING CHANGE DOES NOT APPLY TO YOU. Users of the all-in-one image (e.g., the unraid app) for instance are not affected.
If you have a custom IMMICH_MEDIA_LOCATION environment variable set to a relative path, you will have to do the following process:
- Stop Immich (
docker compose stop): - Update Immich (
docker compose pull) - Update the environment variable to an absolute path, for example:
-IMMICH_MEDIA_LOCATION=./my-library
+IMMICH_MEDIA_LOCATION=/usr/src/app/my-library
- Start Immich (
docker compose up -d --force-recreate) - After the server successfully starts up, connect to it (
docker exec ``*-it*`` immich_server /bin/sh) and runimmich-admin change-media-location. When prompted, enter the appropriate values. For example:
docker exec -it immich_server /bin/sh
$ immich-admin change-media-location
...
? Enter the previous value of IMMICH_MEDIA_LOCATION: ./my-library
? Enter the new value of IMMICH_MEDIA_LOCATION: /usr/src/app/my-library
Previous value: ./my-library
Current value: /usr/src/app/my-library
Changing database paths from "my-library/*" to "/usr/src/app/my-library/*"
? Do you want to proceed? [Y/n] y
Matching database file paths were updated successfully! 🎉
You may now set IMMICH_MEDIA_LOCATION=/usr/src/app/my-library and restart!
Background/Motivation
Relative paths have implied ambiguity, as they depend on the current working directory to resolve correctly, leading to issues like (#4465). This change removes this ambiguity and sets up the project to transition away from files living at /usr/src/app/upload entirely. Currently, the upload folder lives at /usr/src/app/upload/upload, which is very confusing… for everyone. This change opens to door for a future migration to something like IMMICH_DATA=/data, which a more sensible setup.
API Key changes (#20113)
Note: This change may affect the use of third-party applications, such as ImmichGo, ImmichKios, or ImmichFrame.
This release includes a change to how API Keys work, specifically when used with routes that don’t require a specific permission. Previously, a scoped API Key could access these routes, but they will now throw a forbidden error. Routes without a declared scope now implicitly require the “all” permission.
Highlights
Welcome to release v1.136.0. This midsummer release is the culmination of the team's labor of love for the Immich community, featuring the introduction of a new timeline and sync mechanism in beta mode, Android widgets, and one of the last breaking changes we want to make before reaching the stable release milestone. Let’s dive right into it.
- Beta mode for the new timeline, sync, and upload mechanism
- Android widgets
- iOS widget improvements
- Deep links
Beta timeline, sync, and upload mechanism
Note
This is only supported when both the server and the mobile app are updated to v1.136.0
This is a series of work that has been happening for months under the hood, from the changes in the database query engine, server’s queries, and support logic, to integrating a whole new database on the mobile app, and rewriting almost all aspects of the mobile app, you can now try the new timeline with data sync mechanism, and upload rework by go to the App Settings > Toggle the Beta timeline button. After toggling, you will be directed to a screen where data migration is executed automatically. You can then proceed to the new experience.
You can distinguish the beta timeline from the old one by the beta symbol next to the Immich logo in the app bar.
Why?
Over the past year, the major complaints we've received from users have primarily centered around the mobile app. The app simply doesn't feel premium or responsive—it's often janky and takes too long to become usable when first opened, especially when you have a large number of albums. Users can't even view their local albums unless they've selected them as backup targets. Our technical debt in the data structure has created some truly frustrating behaviors, like forcing users to re-upload everything (only to have it rejected by the server) when they switch phones and end up with a different device ID. Or local photos and videos don’t show up until they are all hashed, which could take a while.
We've realized we can't honestly call the application stable or confidently recommend it to everyone until we resolve these fundamental problems. We genuinely want this app to be excellent. We want the user experience to be seamless and delightful—we want you to feel genuinely happy when you open Immich to browse through your precious memories.
What’s new?
Data sync
- The data sync is now running in a background thread, separate from the UI thread. This means that during data synchronization, the app will remain smooth to browse.
- The data sync speed should be improved drastically. The data is being streamed to the mobile app instead of being sent there in a single large chunk. This will help users with a massive library.
- The calculation of which data needs to be retrieved from the server is now performed on the server, rather than being calculated by the mobile app previously. This means lower CPU usage on the mobile app and quicker incremental sync.
- The mobile app will now retrieve data from the server and maintain similar database tables within the app. This restructuring enables better offline operation and supports more complex usage behaviors.
Timeline/Display experience
- The new timeline has been rewritten from the ground up to enhance scrolling and dragging behavior, making it easier for you to navigate the timeline.
- The detail viewer is now more interactive, allowing you to scroll between photos or videos when the bottom detail sheet is opened.
- The album views and other collection views are more lively, featuring a parallax effect to make your album/collection feel alive with mesmerizing animation.
- You can now view all albums on the device, regardless of which album you have selected as the target for backing up. You can view them in the `Library > On this device` section. For users who want to select individual assets to back up to the server, they can perform that operation from here.
Upload
- The upload mechanism has been rewritten from the ground up.
- Upload is now handled by the OS, allowing for a better background upload operation. Instead of handling the uploading ourselves, we are now placing the photos and videos in a queue, which will run continuously when the Immich app is opened in the foreground and for a few minutes after it is put into the background. Then the OS will take over and start pulling tasks from the queue, handling the upload process by itself.
- Starting the upload progress is now invoked from a toggle button
- Uploads are now running in parallel . The new upload detail page displays which assets are being uploaded and whether they are experiencing issues or stuck. You can tap on each item to see exactly which asset is causing the problem.
- On Android, there is no longer a virtual
Recentsalbum that includes all assets. Instead, there is a button to select all albums for backup. - In the backup album selection screen, you can now search for the album you want to back up.
Expectations of the beta version of the mentioned mechanisms
- The app should be very smooth to browse around during the initial login and subsequent app openings.
- Collections (favorite, archived, locked folder, etc.) and album views should make you feel nice, cozy, and delighted.
- Background queuing of newly taken photos is not yet implemented. We will start working on this next.
- Some views are not yet ported over to the new implementation, such as, but not limited to
- People view
- Map view
- Some mechanisms are still missing from the previous implementation, such as, but not limited to
- Add to album from multi-selection
- Album sync when uploading
- There are still some buggy behaviors/animations we will be ironing out in the coming days.
How can you help us?
- Use the beta timeline and the new upload rework.
- Report any bugs and weirdness you experience on GitHub’s issue tracker
[beta] <your-title-here>as the title - Reach out and provide direct feedback on Discord
- Feedback from iCloud users is greatly appreciated
Android Widgets
This is a follow-up to one of our most requested features: Home sc...
Contributors
Assets 2
noml-v1.136.0-ig319
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.136.0 - 69420 stars release
Caution
BREAKING CHANGES
IMMICH_MEDIA_LOCATION (#19995)
Note: if you DO NOT have IMMICH_MEDIA_LOCATION in your .env file, or if it is set to a path that starts with a / (absolute path), THIS BREAKING CHANGE DOES NOT APPLY TO YOU. Users of the all-in-one image (e.g., the unraid app) for instance are not affected.
If you have a custom IMMICH_MEDIA_LOCATION environment variable set to a relative path, you will have to do the following process:
- Stop Immich (
docker compose stop): - Update Immich (
docker compose pull) - Update the environment variable to an absolute path, for example:
-IMMICH_MEDIA_LOCATION=./my-library
+IMMICH_MEDIA_LOCATION=/usr/src/app/my-library
- Start Immich (
docker compose up -d --force-recreate) - After the server successfully starts up, connect to it (
docker exec ``*-it*`` immich_server /bin/sh) and runimmich-admin change-media-location. When prompted, enter the appropriate values. For example:
docker exec -it immich_server /bin/sh
$ immich-admin change-media-location
...
? Enter the previous value of IMMICH_MEDIA_LOCATION: ./my-library
? Enter the new value of IMMICH_MEDIA_LOCATION: /usr/src/app/my-library
Previous value: ./my-library
Current value: /usr/src/app/my-library
Changing database paths from "my-library/*" to "/usr/src/app/my-library/*"
? Do you want to proceed? [Y/n] y
Matching database file paths were updated successfully! 🎉
You may now set IMMICH_MEDIA_LOCATION=/usr/src/app/my-library and restart!
Background/Motivation
Relative paths have implied ambiguity, as they depend on the current working directory to resolve correctly, leading to issues like (#4465). This change removes this ambiguity and sets up the project to transition away from files living at /usr/src/app/upload entirely. Currently, the upload folder lives at /usr/src/app/upload/upload, which is very confusing… for everyone. This change opens to door for a future migration to something like IMMICH_DATA=/data, which a more sensible setup.
API Key changes (#20113)
Note: This change may affect the use of third-party applications, such as ImmichGo, ImmichKios, or ImmichFrame.
This release includes a change to how API Keys work, specifically when used with routes that don’t require a specific permission. Previously, a scoped API Key could access these routes, but they will now throw a forbidden error. Routes without a declared scope now implicitly require the “all” permission.
Highlights
Welcome to release v1.136.0. This midsummer release is the culmination of the team's labor of love for the Immich community, featuring the introduction of a new timeline and sync mechanism in beta mode, Android widgets, and one of the last breaking changes we want to make before reaching the stable release milestone. Let’s dive right into it.
- Beta mode for the new timeline, sync, and upload mechanism
- Android widgets
- iOS widget improvements
- Deep links
Beta timeline, sync, and upload mechanism
Note
This is only supported when both the server and the mobile app are updated to v1.136.0
This is a series of work that has been happening for months under the hood, from the changes in the database query engine, server’s queries, and support logic, to integrating a whole new database on the mobile app, and rewriting almost all aspects of the mobile app, you can now try the new timeline with data sync mechanism, and upload rework by go to the App Settings > Toggle the Beta timeline button. After toggling, you will be directed to a screen where data migration is executed automatically. You can then proceed to the new experience.
You can distinguish the beta timeline from the old one by the beta symbol next to the Immich logo in the app bar.
Why?
Over the past year, the major complaints we've received from users have primarily centered around the mobile app. The app simply doesn't feel premium or responsive—it's often janky and takes too long to become usable when first opened, especially when you have a large number of albums. Users can't even view their local albums unless they've selected them as backup targets. Our technical debt in the data structure has created some truly frustrating behaviors, like forcing users to re-upload everything (only to have it rejected by the server) when they switch phones and end up with a different device ID. Or local photos and videos don’t show up until they are all hashed, which could take a while.
We've realized we can't honestly call the application stable or confidently recommend it to everyone until we resolve these fundamental problems. We genuinely want this app to be excellent. We want the user experience to be seamless and delightful—we want you to feel genuinely happy when you open Immich to browse through your precious memories.
What’s new?
Data sync
- The data sync is now running in a background thread, separate from the UI thread. This means that during data synchronization, the app will remain smooth to browse.
- The data sync speed should be improved drastically. The data is being streamed to the mobile app instead of being sent there in a single large chunk. This will help users with a massive library.
- The calculation of which data needs to be retrieved from the server is now performed on the server, rather than being calculated by the mobile app previously. This means lower CPU usage on the mobile app and quicker incremental sync.
- The mobile app will now retrieve data from the server and maintain similar database tables within the app. This restructuring enables better offline operation and supports more complex usage behaviors.
Timeline/Display experience
- The new timeline has been rewritten from the ground up to enhance scrolling and dragging behavior, making it easier for you to navigate the timeline.
- The detail viewer is now more interactive, allowing you to scroll between photos or videos when the bottom detail sheet is opened.
- The album views and other collection views are more lively, featuring a parallax effect to make your album/collection feel alive with mesmerizing animation.
- You can now view all albums on the device, regardless of which album you have selected as the target for backing up. You can view them in the `Library > On this device` section. For users who want to select individual assets to back up to the server, they can perform that operation from here.
Upload
- The upload mechanism has been rewritten from the ground up.
- Upload is now handled by the OS, allowing for a better background upload operation. Instead of handling the uploading ourselves, we are now placing the photos and videos in a queue, which will run continuously when the Immich app is opened in the foreground and for a few minutes after it is put into the background. Then the OS will take over and start pulling tasks from the queue, handling the upload process by itself.
- Starting the upload progress is now invoked from a toggle button
- Uploads are now running in parallel . The new upload detail page displays which assets are being uploaded and whether they are experiencing issues or stuck. You can tap on each item to see exactly which asset is causing the problem.
- On Android, there is no longer a virtual
Recentsalbum that includes all assets. Instead, there is a button to select all albums for backup. - In the backup album selection screen, you can now search for the album you want to back up.
Expectations of the beta version of the mentioned mechanisms
- The app should be very smooth to browse around during the initial login and subsequent app openings.
- Collections (favorite, archived, locked folder, etc.) and album views should make you feel nice, cozy, and delighted.
- Background queuing of newly taken photos is not yet implemented. We will start working on this next.
- Some views are not yet ported over to the new implementation, such as, but not limited to
- People view
- Map view
- Some mechanisms are still missing from the previous implementation, such as, but not limited to
- Add to album from multi-selection
- Album sync when uploading
- There are still some buggy behaviors/animations we will be ironing out in the coming days.
How can you help us?
- Use the beta timeline and the new upload rework.
- Report any bugs and weirdness you experience on GitHub’s issue tracker
[beta] <your-title-here>as the title - Reach out and provide direct feedback on Discord
- Feedback from iCloud users is greatly appreciated
Android Widgets
This is a follow-up to one of our most requested features: Home sc...
Contributors
Assets 2
v1.135.3-ig405
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.135.3
- Fixed an issue where the database migration fails on some instances with a different default database name
What's Changed
🐛 Bug fixes
- fix(server): don't hardcode database name in migration by @dotlambda in immich-app/immich#19376
Full Changelog: immich-app/immich@v1.135.2...v1.135.3
Contributors
Assets 2
openvino-v1.135.3-ig104
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.135.3
- Fixed an issue where the database migration fails on some instances with a different default database name
What's Changed
🐛 Bug fixes
- fix(server): don't hardcode database name in migration by @dotlambda in immich-app/immich#19376
Full Changelog: immich-app/immich@v1.135.2...v1.135.3
Contributors
Assets 2
cuda-v1.135.3-ig110
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.135.3
- Fixed an issue where the database migration fails on some instances with a different default database name
What's Changed
🐛 Bug fixes
- fix(server): don't hardcode database name in migration by @dotlambda in immich-app/immich#19376
Full Changelog: immich-app/immich@v1.135.2...v1.135.3
Contributors
Assets 2
noml-v1.135.3-ig318
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.135.3
- Fixed an issue where the database migration fails on some instances with a different default database name
What's Changed
🐛 Bug fixes
- fix(server): don't hardcode database name in migration by @dotlambda in immich-app/immich#19376
Full Changelog: immich-app/immich@v1.135.2...v1.135.3
Contributors
Assets 2
v1.135.3-ig404
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.135.3
- Fixed an issue where the database migration fails on some instances with a different default database name
What's Changed
🐛 Bug fixes
- fix(server): don't hardcode database name in migration by @dotlambda in immich-app/immich#19376
Full Changelog: immich-app/immich@v1.135.2...v1.135.3
Contributors
Assets 2
openvino-v1.135.3-ig103
ImageGenius Changes:
change pgvecto.rs to VectorChord
immich Changes:
v1.135.3
- Fixed an issue where the database migration fails on some instances with a different default database name
What's Changed
🐛 Bug fixes
- fix(server): don't hardcode database name in migration by @dotlambda in immich-app/immich#19376
Full Changelog: immich-app/immich@v1.135.2...v1.135.3