It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
If anyone else has been running into the issue where a completely fresh install of GOG Stardew Valley 1.6 or higher for Mac immediately crashes on launch I've found a solution. It appears to be related to the installer not creating a .config folder in your home directory if you don't already have one, and the Stardew app not being able to create it either because of Mac filesystem sandboxing. Once I went into terminal and used "mkdir .config" to manually create that folder Stardew successfully launched.
avatar
axodys: If anyone else has been running into the issue where a completely fresh install of GOG Stardew Valley 1.6 or higher for Mac immediately crashes on launch I've found a solution. It appears to be related to the installer not creating a .config folder in your home directory if you don't already have one, and the Stardew app not being able to create it either because of Mac filesystem sandboxing. Once I went into terminal and used "mkdir .config" to manually create that folder Stardew successfully launched.
You just saved me so much aggravation and time. You are my new hero. Thank you!
avatar
axodys: If anyone else has been running into the issue where a completely fresh install of GOG Stardew Valley 1.6 or higher for Mac immediately crashes on launch I've found a solution. It appears to be related to the installer not creating a .config folder in your home directory if you don't already have one, and the Stardew app not being able to create it either because of Mac filesystem sandboxing. Once I went into terminal and used "mkdir .config" to manually create that folder Stardew successfully launched.
You should probably report this to gog support if the installer is broken.
I just encountered this issue today with my Mac (which has never had Stardew installed on it before) and the freshly-downloaded offline installer.

I can confirm that adding a .config folder to my home directory, which previously did not have one, fixed the issue for me. Just wanted to comment that this issue and fix is unchanged a year later for anyone else experiencing it since these things often change with time.

(For anyone a little rusty on terminal commands, you can check if your home directory already has a .config folder by using "ls -a" and looking through the existing list of folders before using mkdir to create one.)