The Skin Manager goes back to version 1.5.0.0 after installing latest 2.0.1

Question

The Skin Manager goes back to version 1.5.0.0 after installing latest 2.0.1

Closed this issue a month ago · 10 comments

After installing the latest version 2.0.1 and restarting Jellyfin(to enable the plugin) the version goes to 1.5.0.0. Is jellyfin detecting it as higher version on the repo?

naterfute commented 4 months ago

+1

Answer 1 · 2024-08-05T11:48:56.000Z

The only solution that I found was to rename the 2.0.1 package to 1.5.0.0. it would show as 1.5.0.0 but you'll have the latest version

Answer 2 · 2024-08-05T19:04:22.000Z

Recommend moving this issue to a bug.
From some digging this issue is caused by an improperly built Jellyfin.Plugin.SkinManager.dll bundled in release version 2.0.1. The built dll still uses the old assembly version of 1.5.0.0 instead of 2.0.1.

When Jellfin loads the plugin at boot it uses the reported dll version instead of using the version in the Skin Manager meta.json file. This can results in broken references (such as a missing plugin image) which can be 'fixed' by changing the version in Skin Manager's meta.json file to 1.5.0.0 and creating a "Skin Manager_1.5.0.0" symbolic link that points to Skin Manager_2.0.1 in the jellyfin plugin folder ("/config/plugins" on Linux).

Answer 3 · 2024-08-07T13:18:24.000Z

Recommend moving this issue to a bug. From some digging this issue is caused by an improperly built Jellyfin.Plugin.SkinManager.dll bundled in release version 2.0.1. The built dll still uses the old assembly version of 1.5.0.0 instead of 2.0.1.

When Jellfin loads the plugin at boot it uses the reported dll version instead of using the version in the Skin Manager meta.json file. This can results in broken references (such as a missing plugin image) which can be 'fixed' by changing the version in Skin Manager's meta.json file to 1.5.0.0 and creating a "Skin Manager_1.5.0.0" symbolic link that points to Skin Manager_2.0.1 in the jellyfin plugin folder ("/config/plugins" on Linux).

can you please fix it

Answer 4 · 2024-08-14T15:40:15.000Z

Recommend moving this issue to a bug. From some digging this issue is caused by an improperly built Jellyfin.Plugin.SkinManager.dll bundled in release version 2.0.1. The built dll still uses the old assembly version of 1.5.0.0 instead of 2.0.1.
When Jellfin loads the plugin at boot it uses the reported dll version instead of using the version in the Skin Manager meta.json file. This can results in broken references (such as a missing plugin image) which can be 'fixed' by changing the version in Skin Manager's meta.json file to 1.5.0.0 and creating a "Skin Manager_1.5.0.0" symbolic link that points to Skin Manager_2.0.1 in the jellyfin plugin folder ("/config/plugins" on Linux).

can you please fix it

+1

Answer 5 · 2024-09-04T09:49:30.000Z

Please fix it, same issue here

Answer 6 · 2024-09-04T09:49:59.000Z

The only solution that I found was to rename the 2.0.1 package to 1.5.0.0. it would show as 1.5.0.0 but you'll have the latest version

Can you please tell me how did you do that exactly? Would nice to have a workaround until it's fixed

Answer 7 · 2024-11-04T21:03:30.000Z

AFAICT, issue is caused by the dll version inside of release 2.0.1 still being 1.5.0.0. I guess during release somehow older version of dll was published.

@danieladov, can you please bump the version and trigger new release?

P.S. Image for skin not showing up in the plugin manager also caused by this. Jellyfin tries to fetch image from /Plugins/e9ca8b8eca6d40e785dc58e536df8eb3/1.5.0.0/Image but gets 404. And /Plugins/e9ca8b8eca6d40e785dc58e536df8eb3/2.0.1/Image get image normally.

Answer 8 · 2024-11-04T23:14:10.000Z

Hi, I've just released a new version, it should be working now

Answer 9 · 2024-11-05T06:21:55.000Z

Yep, after update correct version is loaded:

Also, image is showing up now)

Thank you!