Sparkle

Multiple Users, Fast User Switching

Asked by John Brayton

I wonder if there are any suggested strategies for dealing with app updates while another user is logged in (via Fast User Switching) and using the same application?

As near as I can tell, most apps just let the other user continue to use the application and do so without difficulty, but are there any significant issues with that?

Question information

Language:
English Edit question
Status:
Solved
For:
Sparkle Edit question
Assignee:
No assignee Edit question
Solved by:
Grant
Solved:
Last query:
Last reply:
Revision history for this message
Hofman (cmhofman) said : 		#1

I'd say there are indeed issues with that, because the resources (and anything in the bundle) changes, which can lead to any problem including crashes. The app therefore needs to be relaunched after updating. However AFAIK there's no clearway to do that for some other user (or some other process for that matter). Nota that this has nothing to do with Sparkle in particular, it just applies to any updating process including manual updating. So the suggested strategy us to make sure that you never do that, and when you do, make sure that the other users relaunch the app.

Revision history for this message
Best Grant (gerickson) said : 		#2

I tackled this problem by setting a kqueue on the bundle folder and bundle executable. Whenever I detect a change, I check the bundle versions and then flag a warning if they are different. For daemons/agents, I quit and let launchd bring things back up. For user interface applications, the user performs the action.

Revision history for this message
John Brayton (jbrayton) said : 		#3

Thanks Grant, that solved my question.