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

Crash when running checkForUpdates() #2560

Closed
YoavGro opened this issue May 12, 2024 · 2 comments · Fixed by #2561
Closed

Crash when running checkForUpdates() #2560

YoavGro opened this issue May 12, 2024 · 2 comments · Fixed by #2561

Comments

@YoavGro
Copy link

YoavGro commented May 12, 2024

Description of the problem

Crash from user on checkForUpdates()

Assertion failed: (_driver == nil), function -[SPUUpdater checkForUpdatesWithDriver:updateCheck:installerInProgress:], file SPUUpdater.m, line 698.

Do you use Sandboxing in your app? No

Version of Sparkle.framework in the latest version of your app 2.6.2

Version of Sparkle.framework in the old version of app that your users have (or N/A) 2.6.2

Sparkle's output from Console.app

Don't know, this was from crash report

Steps to reproduce the behavior

N/A

[The more information provided and pasted verbatim, the easier it will be to diagnose an issue. If you can provide the affected application/binary and XML feed to reproduce an issue, share them]

@zorgiepoo
Copy link
Member

zorgiepoo commented May 12, 2024

Do you have backtraces of all the threads? Is everything Sparkle related on the main thread? Do you only call checkForUpdates based on user initiation?

zorgiepoo added a commit that referenced this issue May 12, 2024
Make sure we don't perform a background update check when a user update check was initiated. This may have regressed from #2295.

Also replaces an assert with an error log if the _driver already exists.

Fixes #2560
zorgiepoo added a commit that referenced this issue May 12, 2024
Make sure we don't perform a background update check when a user update check was initiated. This may have regressed from #2295.

Also replaces an assert with an error log if the _driver already exists.

Fixes #2560
@zorgiepoo
Copy link
Member

zorgiepoo commented May 12, 2024

I believe I found a rare potential race in #2561. I also replaced the assert with a log here to fix this.

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

Successfully merging a pull request may close this issue.

2 participants