How to develop auto-update for MacOS application in Objective C? [closed]
up vote
0
down vote
favorite
I have a desktop MacOS app written in Objective-C.
I want to add this functionality:
I assume that somewhere on a server sits new app version xx.1.1.dmg
- app shows that an update is available
- user agrees to update
- app downloads the update
- app prompts user to agree to install & restart the app
- magic happens
QUESTIONs:
A. Is there a framework to start the download, display the progress and then update the running application or do I have to implement all this?
The update process of many applications look like very similar so it seams like some shared functionality is used.
B. Once you have the update archive on local drive. How to you "replace" the old app with the new one. Do you "just" unpack the archive over the existing app folder? This could be problematic because of open files.
C. How do you force app restart?
D. Is there a way to schedule "after-app-quit" actions which would solve the issues described in B? Could these actions also include the new app start?
objective-c xcode macos installation auto-update
closed as too broad by rckoenes, El Tomato, dandan78, user6655984, Willeke Nov 8 at 16:45
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
I have a desktop MacOS app written in Objective-C.
I want to add this functionality:
I assume that somewhere on a server sits new app version xx.1.1.dmg
- app shows that an update is available
- user agrees to update
- app downloads the update
- app prompts user to agree to install & restart the app
- magic happens
QUESTIONs:
A. Is there a framework to start the download, display the progress and then update the running application or do I have to implement all this?
The update process of many applications look like very similar so it seams like some shared functionality is used.
B. Once you have the update archive on local drive. How to you "replace" the old app with the new one. Do you "just" unpack the archive over the existing app folder? This could be problematic because of open files.
C. How do you force app restart?
D. Is there a way to schedule "after-app-quit" actions which would solve the issues described in B? Could these actions also include the new app start?
objective-c xcode macos installation auto-update
closed as too broad by rckoenes, El Tomato, dandan78, user6655984, Willeke Nov 8 at 16:45
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a desktop MacOS app written in Objective-C.
I want to add this functionality:
I assume that somewhere on a server sits new app version xx.1.1.dmg
- app shows that an update is available
- user agrees to update
- app downloads the update
- app prompts user to agree to install & restart the app
- magic happens
QUESTIONs:
A. Is there a framework to start the download, display the progress and then update the running application or do I have to implement all this?
The update process of many applications look like very similar so it seams like some shared functionality is used.
B. Once you have the update archive on local drive. How to you "replace" the old app with the new one. Do you "just" unpack the archive over the existing app folder? This could be problematic because of open files.
C. How do you force app restart?
D. Is there a way to schedule "after-app-quit" actions which would solve the issues described in B? Could these actions also include the new app start?
objective-c xcode macos installation auto-update
I have a desktop MacOS app written in Objective-C.
I want to add this functionality:
I assume that somewhere on a server sits new app version xx.1.1.dmg
- app shows that an update is available
- user agrees to update
- app downloads the update
- app prompts user to agree to install & restart the app
- magic happens
QUESTIONs:
A. Is there a framework to start the download, display the progress and then update the running application or do I have to implement all this?
The update process of many applications look like very similar so it seams like some shared functionality is used.
B. Once you have the update archive on local drive. How to you "replace" the old app with the new one. Do you "just" unpack the archive over the existing app folder? This could be problematic because of open files.
C. How do you force app restart?
D. Is there a way to schedule "after-app-quit" actions which would solve the issues described in B? Could these actions also include the new app start?
objective-c xcode macos installation auto-update
objective-c xcode macos installation auto-update
edited Nov 13 at 16:49
asked Nov 7 at 13:01
PerfectGamesOnline.com
1,17011321
1,17011321
closed as too broad by rckoenes, El Tomato, dandan78, user6655984, Willeke Nov 8 at 16:45
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as too broad by rckoenes, El Tomato, dandan78, user6655984, Willeke Nov 8 at 16:45
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes