Skip to content
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

Update after a new version of Squirrel gets stuck. #339

Closed
Cyral opened this issue May 10, 2015 · 4 comments
Closed

Update after a new version of Squirrel gets stuck. #339

Cyral opened this issue May 10, 2015 · 4 comments

Comments

@Cyral
Copy link

Cyral commented May 10, 2015

In my last application release, I updated the version of Squirrel.Windows, and pushed the update with no issues. It seems (as this has occurred twice), that the update after an update the updates Squirrel, causes the updater to become stuck. On the updated version of Squirrel, I pushed an update, which goes to from 33% to 69%, jumps back to 33%, and then gets stuck on 69%.

Last time this happened, I had to send a message to all clients with directions on how to manually update. Every update after this, using the same Squirrel version, worked fine, even the update to a newer version of Squirrel. It is the update after the newer version that causes issues.

I have tried editing the RELEASES file and deleting the delta, to force a full download, without any luck. Anyone got any ideas? If I can't solve this, everyone will be stuck on a version that is not able to update.

The SquirrelSetup.Log contains no information.

@amweiss
Copy link
Contributor

amweiss commented May 11, 2015

You're probably hitting the same problem as a few others of us.
See:
#329 #328

#331 fixed it for me.

@Cyral
Copy link
Author

Cyral commented May 11, 2015

So, once #331 is released, I should be able to use it to make a new release, upload that one, and use it for new installs, but all old versions are affected by the bug and will need to be manually re-installed with the new version?

@amweiss
Copy link
Contributor

amweiss commented May 11, 2015

If you are in the same situation as me, yes.

On Mon, May 11, 2015, 16:11 Cyral [email protected] wrote:

So, once #331 #331 is
released, I should be able to use it to make a new release, upload that
one, and use it for new installs, but all old versions are affected by the
bug and will need to be manually re-installed with the new version?


Reply to this email directly or view it on GitHub
#339 (comment)
.

@Thieum
Copy link
Contributor

Thieum commented May 3, 2019

@shiftkey fixed by #331. This can be closed.

@shiftkey shiftkey closed this as completed May 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants