The add-on seems to set file permissions and/or hold onto handles so the add-on cannot be updated without disabling/unloading.
I have seen many support requests for this specific issue, but haven’t really seen this being tracked anywhere. I know the workaround is there (shift, disable/enable add-on), but it can be a barrier for new/inexperienced users, evidenced by the amount of messages
Possible solution: if local version < most up-to-date version, ask user if they want to update during initialization so no resources/handles get loaded and block the update process
I know for sure that I experienced this myself around 1/31 and 2/1 when two updates were released in a short span since I remembered having to do the workaround twice. I have seen various messages on Slack, reddit, here, etc.
It is actually more of a silent error for the issue I was describing.
You go to “Tools → Add-ons”, and it’ll go through the update process, but the update failed silently. If you click check for updates again, the same add-on, AnkiHub, will again ask you to update.
It is actually more of a silent error for the issue I was describing.
You go to “Tools → Add-ons”, and it’ll go through the update process, but the update failed silently. If you click check for updates again, the same add-on, AnkiHub, will again ask you to update.
In the new add-on version that was just released these silent errors will not be silent anymore. Anki will show an error message when it happens and we will get automatic error reports. This will enable us to fix the cause of these errors in a future update.
Keep in mind that the changes will only have effect on updates after the current one (because the add-on update needs to be installed before it can have any effect).
