BUG? Update via Package Manager Doesn’t Delete Old Plugin

Hi @jordi.pujol,

I’m experiencing an issue where an old version of a plugin does not get properly uninstalled when updating via the Package Manager. And then the user runs into the duplicated GUID issue. The plugin can only be installed through the Package Manager, so a manual installation is not the cause of the issue.

Is this likely a problem with my plugin, or could it be a bug? The plugin structure looks like this — does anything seem wrong (aside from the same logo appearing three times :slightly_smiling_face:)?

I think this is a Windows issue, as I haven’t experienced it on Mac. Could this maybe be related to the files being locked, because the plugin is open on update?

Best,
Johan

@will can you take a look at this?

1 Like

Hi, @will.

I’ve done some more debugging, and it looks like the issue is that version 0.1.6 does not uninstall properly. So the problem is not related to the update itself, but rather to the uninstall step. Version 0.1.7 uninstalls correctly.

I think I may have been a bit sloppy with disposing of resources when Rhino shut down in version 0.1.6. This has now been fixed, so it’s likely that this is a bug on my side rather than a Rhino issue. Does this sound plausible to you?

Sorry for the inconvenience.

Best,
Johan

1 Like

I have run into this issue myself, and worked it back to spelling or case errors in the name of my plugin or similar mismatches in my manifest file.

Even if the guid of the plugin is the same, a minor difference in the naming will cause both versions to be installed and loaded - causing conflict.

Cheers

DK

1 Like