[GH-ISSUE #71] The Skin Manager goes back to version 1.5.0.0 after installing latest 2.0.1 #37

Closed
opened 2026-05-06 13:14:07 +02:00 by BreizhHardware · 10 comments

Originally created by @vinayakv22 on GitHub (Jul 4, 2024).
Original GitHub issue: https://github.com/danieladov/jellyfin-plugin-skin-manager/issues/71

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?

Originally created by @vinayakv22 on GitHub (Jul 4, 2024). Original GitHub issue: https://github.com/danieladov/jellyfin-plugin-skin-manager/issues/71 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?
Author
Owner

@naterfute commented on GitHub (Jul 31, 2024):

+1

<!-- gh-comment-id:2260084956 --> @naterfute commented on GitHub (Jul 31, 2024): +1
Author
Owner

@vinayakv22 commented on GitHub (Aug 5, 2024):

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

<!-- gh-comment-id:2268883765 --> @vinayakv22 commented on GitHub (Aug 5, 2024): 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
Author
Owner

@samrg123 commented on GitHub (Aug 5, 2024):

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).

<!-- gh-comment-id:2269722582 --> @samrg123 commented on GitHub (Aug 5, 2024): 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).
Author
Owner

@iamLazyCode commented on GitHub (Aug 7, 2024):

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

<!-- gh-comment-id:2273455662 --> @iamLazyCode commented on GitHub (Aug 7, 2024): > 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
Author
Owner

@WickedSquirrel commented on GitHub (Aug 14, 2024):

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

<!-- gh-comment-id:2289141309 --> @WickedSquirrel commented on GitHub (Aug 14, 2024): > > 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
Author
Owner

@igiffrekt commented on GitHub (Sep 4, 2024):

Please fix it, same issue here

<!-- gh-comment-id:2328410230 --> @igiffrekt commented on GitHub (Sep 4, 2024): Please fix it, same issue here
Author
Owner

@igiffrekt commented on GitHub (Sep 4, 2024):

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

<!-- gh-comment-id:2328411181 --> @igiffrekt commented on GitHub (Sep 4, 2024): > 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
Author
Owner

@markalex2209 commented on GitHub (Nov 4, 2024):

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.

<!-- gh-comment-id:2455697096 --> @markalex2209 commented on GitHub (Nov 4, 2024): 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.
Author
Owner

@danieladov commented on GitHub (Nov 4, 2024):

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

<!-- gh-comment-id:2455891898 --> @danieladov commented on GitHub (Nov 4, 2024): Hi, I've just released a new version, it should be working now
Author
Owner

@markalex2209 commented on GitHub (Nov 5, 2024):

Yep, after update correct version is loaded:
image
Also, image is showing up now)
image

Thank you!

<!-- gh-comment-id:2456329105 --> @markalex2209 commented on GitHub (Nov 5, 2024): Yep, after update correct version is loaded: ![image](https://github.com/user-attachments/assets/5c0780a7-3dc2-403b-9c01-c18108eba047) Also, image is showing up now) ![image](https://github.com/user-attachments/assets/4e47abb1-f45e-4ee4-86b1-3dc9d29eb5cc) Thank you!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/jellyfin-plugin-skin-manager#37
No description provided.