-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Spotify) Package fails to finish if Spotify does not launch as expected #2314
Comments
It looks like the package is waiting for Spotify.exe to run, in order to kill it - we should possibly add logic to timeout after ~30-60 seconds (or some other agreed, reasonable time). That said, when I tested this by running We could still add a timeout to the logic, but at that point I'd say it was more enhancement than bug. |
Thanks for the reply, I tried to replicate it myself, but for some reason both the version mentioned here and a new one, installed just fine today. So my guess is, it was either timeout as you suggested, or some other not-persistent issue |
Issue seems to be when you already have Spotify installed but without using Chocolatey. I uninstalled the Spotify package from Chocolatey, located the already installed instance of Spotify on my PC and uninstalled it too. Can install correctly with Chocolatey after that. |
There is a PR up to fix that. |
Given all of the above, I think we can close this issue for now. If we find that it rears up again, we can add a timeout - but as the issue seems rather rare, I'd not say it's at all urgent. |
Chocolatey Version
2.2.2
Chocolatey License
None
Package Version
1.2.20.1218
Current Behaviour
the latest package is "acting up" again, I mean not running
.exe
file as it should. However, if I run it manually from the downloaded location:..\AppData\Local\Temp\chocolatey\spotify\
it updates successfullyExpected Behaviour
the package update smoothly on its own
Steps To Reproduce
Environment
Chocolatey Log
Anything else?
No response
The text was updated successfully, but these errors were encountered: