Replies: 1 comment
-
The most recommended path is updating inside of your main app, rather than from an embedded helper. The user can use your application while the update is prepared to being installed, and it's best integrated / tested path.
No, not with your setup.
There might be issues with a running app being replaced, particularly if the helper app shows UI / shows a window / is in the dock. Since you said you ensure the main app is already terminated, one approach you could try is setting the applicationBundle to your helper app, set the host bundle as you have it to the main app, set SURelaunchHostBundle in your main app's Info.plist, and maybe set SUBundleName too (though I think Another approach is to copy the helper app outside of the main app bundle. |
Beta Was this translation helpful? Give feedback.
-
I have a scenario where my main application (MainApp.app) includes a helper application (Helper.app) within its bundle:
/Applications/MainApp.app/Contents/Helpers/Helper.app
The
Helper.app
integrates Sparkle and is responsible for updatingMainApp.app
. SinceHelper.app
is bundled insideMainApp.app
, when an update is performed, bothMainApp.app
andHelper.app
should be updated together.Before triggering the update, I ensure that
MainApp.app
has already exited. Then, I initiate the Sparkle update process inHelper.app
as follows:I have the following questions:
Helper.app
be terminated during the update process?Helper.app
is not terminated, will replacingMainApp.app
(which containsHelper.app
) work correctly, or could there be issues due to the running process?I appreciate any insights or recommendations. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions