Update dialog closes OBS

[zbang]

Hello,

Whether this is a bug of not, I'd still call it unexpected behavior and one that could easily cause a disruption.

Running 26.1.1 on windows 10.
When OBS starts or when Help->Check for Updates is pressed , the "New update available" window appears.
If there is an update, an "Update now" button will appear.
Clicking "Update now" will close OBS without further confirmation. (Windows may ask for a confirmation, but at that point, OBS is already closed.)

Also, it does not download the installer package as one might expect* which makes it impossible to use the same download on other local systems.
*well, I did, that's the usual behavior for many things; most often they fire a URL to the download page and expect the user to download & installed the update as time permits.

Suggested change-
Add a confirmation dialog after pressing "Update now" to inform the user than this will close OBS, allow them to cancel without affecting whatever OBS is currently doing.

Later,

z!

 

[R1CH]

The update appears on startup, the chances of something important being interrupted are very low. Similarly, if you're pressing "Check for updates" you're probably not in the middle of running a live stream.

 

[zbang]

True, but it's still unexpected and arguably-incorrect behavior - any user action that causes OBS to exit that isn't an explicit Exit command* should have a confirmation.
*I'd argue that File-Exit should too unless the entire state is saved, but that's a different matter

 

[AaronD]

The update appears on startup, the chances of something important being interrupted are very low. Similarly, if you're pressing "Check for updates" you're probably not in the middle of running a live stream.

I'd consider startup to already be inside of a "critical window", based on the (poor, but prevalent) assumption that everything still works. And so the streamer starts the PC at 6:55, starts OBS at 6:58, and starts a well-advertised stream at 7:00. Any interruptions to that are a massively big deal!

Yes, they're being foolhardy and reckless to not have it sitting there with everything running and known to be stable, far enough ahead of time to troubleshoot and fix it. But I've also seen it happen far too many times to keep track of, on a variety of different rigs for a variety of different purposes. And when something does go even slightly sideways, they panic and blame the gear.

I'd recommend moving the update request to when OBS *closes*. That's pretty much an unmistakable signal that its use is done for now. Likewise for system updates on shutdown only, but that's an OS thing, not OBS. It still doesn't suit *everyone*, as you might just scoop up everything and run out of the coffee shop, but for those that have stationary rigs, I don't see a problem.
Except at some point, you *will* have to test the anti-hacking patches to make sure they didn't break your stream...or a hacker will break it instead, because you didn't patch the hole that let him in.

Maybe people would be more willing to take the updates, if they weren't intrusive at the exact time that they're single-tasking something else?

Suggested change-
Add a confirmation dialog after pressing "Update now" to inform the user than this will close OBS, allow them to cancel without affecting whatever OBS is currently doing.

True, but it's still unexpected and arguably-incorrect behavior - any user action that causes OBS to exit that isn't an explicit Exit command* should have a confirmation.

Updating is a major operation. You're supposed to know that. Thus, clicking that button is already a confirmation. No need for a second one.

*I'd argue that File-Exit should too unless the entire state is saved, but that's a different matter

Saving the state is automatic, unless OBS crashes. So the answer to that is always yes. Again, no need to ask.