jelum 17 Posted May 2, 2023 Share Posted May 2, 2023 Hi, I'm developing a plugin to update video metadata from 3rd party site. To the plugin, I added functionality to auto-update. After some time I noticed that the plugin switched off from the library and currently I'm not able to understand the reason for this. Code for the plugin update: var package = new PackageVersionInfo() { name = Plugin.PluginKey, versionStr = "1.123", classification = PackageVersionClass.Release, description = release.body, requiredVersionStr = "4.7.9", sourceUrl = "https://valid_url", checksum = checksum, targetFilename = DLL_NAME, infoUrl = null, runtimes = "netcore" }; try { await _installationManager.InstallPackage(package, true, progress, cancellationToken).ConfigureAwait(false); _logger.Info("Plugin installed successfully"); progress.Report(100d); } The question - why after a plugin update it switched off from the library? Link to comment Share on other sites More sharing options...
rbjtech 4342 Posted May 2, 2023 Share Posted May 2, 2023 Probably best to post this question here : https://emby.media/community/index.php?/forum/47-developer-api/ Link to comment Share on other sites More sharing options...
Luke 37272 Posted May 2, 2023 Share Posted May 2, 2023 Hi, what do you mean by switched off? Link to comment Share on other sites More sharing options...
jelum 17 Posted May 2, 2023 Author Share Posted May 2, 2023 (edited) Hi, like below, before an update everything was turned on - I'm using the plugin, but after an update - the usage was switched off Edited May 2, 2023 by jelum Link to comment Share on other sites More sharing options...
Luke 37272 Posted May 2, 2023 Share Posted May 2, 2023 This looks normal to me. Newly installed metadata providers are always off by default, and users have to enable them on the libraries that they want. Link to comment Share on other sites More sharing options...
jelum 17 Posted May 2, 2023 Author Share Posted May 2, 2023 But the metadata provider was enabled before an update, why the system disabled it? I'm using the same name, targetFilename, only the plugin itself, version, checksum, and sourceUrl changed: var package = new PackageVersionInfo() { name = Plugin.PluginKey, versionStr = "1.123", classification = PackageVersionClass.Release, description = release.body, requiredVersionStr = "4.7.9", sourceUrl = "https://valid_url", checksum = checksum, targetFilename = DLL_NAME, infoUrl = null, runtimes = "netcore" }; Link to comment Share on other sites More sharing options...
Luke 37272 Posted May 2, 2023 Share Posted May 2, 2023 OK, I don't know, sorry, I can't think of anything that would have caused it to be disabled. There have not been any updates in recent memory that have changed library options. Link to comment Share on other sites More sharing options...
jelum 17 Posted May 2, 2023 Author Share Posted May 2, 2023 Thanks, I'll continue investigation 1 Link to comment Share on other sites More sharing options...
jelum 17 Posted May 2, 2023 Author Share Posted May 2, 2023 @Luke, what is the role of guid in plugin updates? Link to comment Share on other sites More sharing options...
Luke 37272 Posted May 2, 2023 Share Posted May 2, 2023 To match the plugin up with the entries in our plugin catalog. Link to comment Share on other sites More sharing options...
jelum 17 Posted May 2, 2023 Author Share Posted May 2, 2023 only in the plugin catalog or the system runtime? can I, using this guid, claim that this is the same plugin during an update? Link to comment Share on other sites More sharing options...
Luke 37272 Posted May 2, 2023 Share Posted May 2, 2023 I really don't know what you're asking or trying to hint at, but the primary function for the guid is the catalog. Link to comment Share on other sites More sharing options...
jelum 17 Posted May 2, 2023 Author Share Posted May 2, 2023 I want to prove to the system, that this is the same plugin and doesn't need to disable it on a library Link to comment Share on other sites More sharing options...
Solution jelum 17 Posted May 2, 2023 Author Solution Share Posted May 2, 2023 Solution: use Guid and don't use a checksum var package = new PackageVersionInfo() { guid = Plugin.PluginGuid, name = Plugin.PluginName, versionStr = release.tag_name, classification = PackageVersionClass.Release, description = release.body, requiredVersionStr = "4.7.9", sourceUrl = release.assets[0].browser_download_url, //checksum = checksum, targetFilename = DLL_NAME, infoUrl = release.html_url, runtimes = "netcore" }; Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now