Update nag refuses to go away

[TheDiscordian]

• OS: Windows
• 0.15.0

Describe the bug
Getting update nag, informs user to restart application to resolve. Upon restart, nag returns.

To Reproduce
Run 0.15.0, have application detect there's a new update.

Expected behavior
Upon restart new version is installed, old version gone, update nag gone.

Screenshots

Additional context

Reported to me by owocean: https://matrix.to/#/!gWiVYCURkxIapWZaGy:ipfs.io/$gMh0L6gUyOGnCVWGRL3Z7_9lBZfNwEk9spkpaxPO9w4?via=ipfs.io&via=matrix.org&via=privacytools.io

combined.log
error.log

[lidel]

I was not able to reproduce this: installed 0.15.0 on a single user, started ipfs desktop, clicked tray menu → "Check for updates", got the update notification, it got installed, Quit app via tray menu → Quit, started again, 0.15.1 runs as expected.
Mind that I'm not a Windows person and run this test on a borrowed laptop, so maybe I did something non-standard?

@TheDiscordian @owocean any thoughts on how to reproduce this? Any detail would be useful.

[owocean]

Not once did I run "Check for updates"
This all happened automatically.

[lidel]

Hm.. still not able to replicate. I cleaned C:\\{your-user-name}\AppData\...\IPFS Desktop and let v0.15.0 run until it picked up v0.15.1 and the update was smooth – after quitting, the new version installed and run ok.

You had some network error related to update checks as well (Error: net::ERR_FAILED|ERR_NAME_NOT_RESOLVED), which gave me an idea: perhaps there is a problem with an update file present on your machine (corrupted file/disk)?

@owocean are you able to replicate yourself?

1. Uninstall IPFS Desktop
2. Manually remove C:\\{your-user-name}\AppData\Roaming\IPFS Desktop (it is not removed by uninstall, but might include corrupted updates or some stale config)
3. Install IPFS-Desktop-Setup-0.15.0.exe in single user mode ("only this user") and wait until it picks up the update, and see if the issue comes back.

[TheDiscordian]

@TheDiscordian @owocean any thoughts on how to reproduce this? Any detail would be useful.

Unfortunately I don't experience this on Linux. I was hoping the report and logs would help uncover what went wrong.

[github-actions]

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

[github-actions]

This issue was closed because it is missing author input.

[lidel]

This is a recurring problem with electron autoupdates.
Similar issue was recently fixed on macOS: #1980

👉 If anyone experiences this type of problem – apply a one-time manual update by installing a package for the latest release – this usually solves the problem.