search

dmarmor / epichrome

An application and Chrome extension for creating web-based applications that work like standalone Mac apps.
GNU General Public License v3.0
855 stars 57 forks source link

App aborted with error: "Error launching engine: The application “Habitica Chrome.app” could not be launched because it is corrupt. The app may not have launched properly. If it did, the engine will not be properly cleaned up upon quitting." [main(665)] #307

Open icotext opened 3 years ago

icotext commented 3 years ago 
*[33664]HabiticaC540(545)/launchapp(2883): Error launching engine: The application “Habitica Chrome.app” could not be launched because it is corrupt.
![33664]HabiticaC540(665)/abortreport(1155)/abort(1093): Aborting: Error launching engine: The application “Habitica Chrome.app” could not be launched because it is corrupt. The app may not have launched properly. If it did, the engine will not be properly cleaned up upon quitting.
dmarmor commented 3 years ago

Hi @icotext, has this been happening with many of your apps, or was a a fluke that just happened once with one app? Thanks!

icotext commented 3 years ago

Once with one app as of now. Usually after upgrading it gracefully exits and says it cannot relaunch the app and I launch again and all is fine, but this time was an abort so that was not graceful.

Thanks, Dierk +1 (650) 353-2674 On Mar 26, 2021, 5:55 PM -0700, dmarmor @.***>, wrote:

Hi @icotext, has this been happening with many of your apps, or was a a fluke that just happened once with one app? Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

dmarmor commented 3 years ago

Hmm, so on updating an app to 2.4.x, it generally doesn't launch correctly the first time? If possible, I'd be interested to see a log of the update run you're describing. When an app updates, it should launch normally, and show an extra page with info about the update...

icotext commented 3 years ago

If you tell me how to pull the log I will try.

Thanks, Dierk +1 (650) 353-2674 On Mar 27, 2021, 6:10 PM -0700, dmarmor @.***>, wrote:

Hmm, so on updating an app to 2.4.x, it generally doesn't launch correctly the first time? If possible, I'd be interested to see a log of the update run you're describing. When an app updates, it should launch normally, and show an extra page with info about the update... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

dmarmor commented 3 years ago

The logs are found in ~/Library/Application Support/Epichrome/Apps/<AppID>/Logs. Ideally, what I'd love to see is if you could run an app that needs updating with debugging on, so I can get a full log of the update run. You'd do this from the terminal like this:

open <YourApp.app> --args --epichrome-debug

Thanks!

dmarmor commented 3 years ago

I'm going to try some different strategies with the launch code to see if I can prevent this from happening. Do these errors occur frequently for you, or is it only rarely?

icotext commented 3 years ago

Only after upgrade On Apr 30, 2021, 9:55 AM -0700, dmarmor @.***>, wrote:

I'm going to try some different strategies with the launch code to see if I can prevent this from happening. Do these errors occur frequently for you, or is it only rarely? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

dmarmor commented 3 years ago

Version 2.4.5 will be up shortly, and I've added a retry to the launch code, in the hope that if it hits this type of error it can just make a second attempt and launch successfully. If you continue to get launch errors after updating to 2.4.5, please let me know and I'll see if there are any other things I can try. Thanks!