Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags
(+1)

I downloaded the macOS version but it won't launch. :-(

macOS says,

“Port Valley [the 2022 DEMO]” is damaged and can’t be opened. You should move it to the Trash.

I thought it might be a code signature problem, so I checked that out:

$ codesign --verify --verbose=10 Port\ Valley\ \[the\ 2022\ DEMO\].app
--prepared:/Users/benzado/Downloads/Port Valley [the 2022 DEMO][macOS]/Port Valley [the 2022 DEMO].app/Contents/PlugIns/lib_burst_generated.bundle
--validated:/Users/benzado/Downloads/Port Valley [the 2022 DEMO][macOS]/Port Valley [the 2022 DEMO].app/Contents/PlugIns/lib_burst_generated.bundle
--prepared:/Users/benzado/Downloads/Port Valley [the 2022 DEMO][macOS]/Port Valley [the 2022 DEMO].app/Contents/Frameworks/libMonoPosixHelper.dylib
--validated:/Users/benzado/Downloads/Port Valley [the 2022 DEMO][macOS]/Port Valley [the 2022 DEMO].app/Contents/Frameworks/libMonoPosixHelper.dylib
--prepared:/Users/benzado/Downloads/Port Valley [the 2022 DEMO][macOS]/Port Valley [the 2022 DEMO].app/Contents/Frameworks/UnityPlayer.dylib
--validated:/Users/benzado/Downloads/Port Valley [the 2022 DEMO][macOS]/Port Valley [the 2022 DEMO].app/Contents/Frameworks/UnityPlayer.dylib
--prepared:/Users/benzado/Downloads/Port Valley [the 2022 DEMO][macOS]/Port Valley [the 2022 DEMO].app/Contents/Frameworks/libmonobdwgc-2.0.dylib
--validated:/Users/benzado/Downloads/Port Valley [the 2022 DEMO][macOS]/Port Valley [the 2022 DEMO].app/Contents/Frameworks/libmonobdwgc-2.0.dylib
Port Valley [the 2022 DEMO].app: a sealed resource is missing or invalid
file added: /Users/benzado/Downloads/Port Valley [the 2022 DEMO][macOS]/Port Valley [the 2022 DEMO].app/Contents/PlugIns/Steamworks.NET.txt

Moving that Steamworks.NET.txt file outside the app bundle fixes the code signing issue, but macOS continues to display the same message when I try to launch it.

I'm on a MacBook Air (M1, 2020) running macOS 11.6.1 (20G224).

(2 edits)

Hey, sorry for that!

I've just tested a fix with 2 different macs and it should be fixed now, please let me know if that works for you!

____

Edit: Indeed, this seems to be caused by a Unity bug when signing macOS builds. 

I manually made some changes to bypass their signature, but the game now asks for a security check before opening it the first time (System Preferences -> Security & Privacy)… Annoying, but at least it seems to run now.

I'll keep an eye on this.

(+1)

Thanks, the new build works. Now I get the warning about the developer not being recognized, but that's to be expected if you're not part of Apple's Developer ID program ($$$). Using ctrl-click to open the app works just fine. Thanks again for the quick turnaround.