Closed yurikoles closed 3 years ago
Hey @yurikoles ,
Thanks for raising this. The problem is that you cancel the execution during installation. That leaves the metadata unsynced with the current state. It might be related to this: https://github.com/buo/homebrew-cask-upgrade/issues/57
We currently backup the metadata, then install the app itself and then if the installation was successful, delete the "old" metadata. If the installation fails, then we restore the backed-up metadata so that it works fine afterwards.
When you cancel the installation it ends up in a state when there are no metadata for the app even though it is installed and therefore brew cask
doesn't know that it is installed.
I hope that make sense.
Hey @yurikoles
After I changed the installation mechanism from a custom one to using reinstall
command, this doesn't seem to an issue any more.
Feel free to reopen the issue if you still encounter this.
I often encounter that a large cask that I don't plan to use will be upgraded. But uninstalling cask after it's download started is seems to be impossible.