2023-11-08, 23:16
Thanks for the flowers
And thanks for helping figuring out such issues!
I think I now came to the core of the problem. Really nasty. Normally unique identifiers are used when processing loading attempts to differentiate the results and callbacks. The image cache did not do this and used the image's URL for this. But when two parallel load attempts of the same image was happening (e.g. one for the playlist thumb which shall be scaled down, and one for the NowPlaying which shall not be scaled) both were mixed up and the first started attempt won the race, resulting in saving the scaled down image. I now added a unique identifier like for other JSON API calls. Until now this seems to work even without any workaround.
The first test build will come after it got approved by Apple (new version number 1.13.1 requires a review). After some more tests I will then provide the real fix. In general this problem could have happened also for other situations where the same image-URL was used in different resolutions ...
Btw, during my tests I saw this problem multiple times even when starting movies from the movie database view.
And thanks for helping figuring out such issues!
I think I now came to the core of the problem. Really nasty. Normally unique identifiers are used when processing loading attempts to differentiate the results and callbacks. The image cache did not do this and used the image's URL for this. But when two parallel load attempts of the same image was happening (e.g. one for the playlist thumb which shall be scaled down, and one for the NowPlaying which shall not be scaled) both were mixed up and the first started attempt won the race, resulting in saving the scaled down image. I now added a unique identifier like for other JSON API calls. Until now this seems to work even without any workaround.
The first test build will come after it got approved by Apple (new version number 1.13.1 requires a review). After some more tests I will then provide the real fix. In general this problem could have happened also for other situations where the same image-URL was used in different resolutions ...
Btw, during my tests I saw this problem multiple times even when starting movies from the movie database view.