Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

aardi030

5
Posts
A member registered Nov 16, 2020

Recent community posts

Two more tests incl. 1.56:

(1) I tried another method, namely `tar -xzf ./NewPixatool_157.zip`, which will definitely work, if the original archive has been properly created, but this yields the same results as before. So the problem lies somewhere at the source, e.g. an old version of 7zip used to create the zip archive, or maybe the original framework was already broken at the time that you built the macOS app bundle.

(2) Also tried v1.56, and this one works just fine, but it also has an older framework, where the files are arranged differently (without symbolic links and with the executable in the root directory), which is what you would expect in some generic macOS bundles, but not in an actual framework bundle.

So my suggestion, if you want to use the regular framework format (v1.57) with symbolic links, would be to check the original framework you're using when building the macOS app bundle, and if the symbolic links and executable bits are already broken in that framework, replace it with a working copy, and then use tgz (tar-gzip) or tbz (tar-bzip2) as the archive format. (Bzip2 will have better compression than gzip.) This would also eliminate any potential unarchiving problems on Linux systems.

Another thing I noticed are the version and Bundle ID keys in the respective Info.plist files. NewPixaTool needs "1.57" as the CFBundleShortVersionString, and PixaTool needs "1.35". (The bundle versions, i.e. 1.0.0.0 and 1.0.25 can remain.) The CFBundleIdentifier keys need to have different values, namely (for example) "io.nwjs.nw.NewPixaTool" and "io.nwjs.nw.PixaTool"… otherwise you'll have two programs or processes with the same Bundle ID, and that's not a nice thing to do to macOS and its users. ;)

(1 edit)

I have fixed it now. All the binaries had lost the executable bit, which you can remedy with chmod u+x foo, and all the symbolic links in the framework had been destroyed, which you can recreate with ln -s foo bar. I also tried unzipping the original archive in several ways, with macOS Archive Utility, MacPaw's The Unarchiver, Keka, with unzip in Terminal etc., and it always unzipped fine, but still resulted in the above broken app bundle. It seems that the initial error was made when zipping the app, which I assume was not done with the proper tools or settings.

Oh, I think I see what happened… the symbolic links from the framework's root directory to the nested code got completely messed up.

Just bought PixaTool, but version 1.57 (newpixatool) crashes at launch on macOS 10.15.7.

Crash report: https://pastebin.com/siPNny63

When I run the executable directly in Terminal I get the following error message:

https://pastebin.com/vq9iYp1r

Not sure what the problem is… something with the framework, it seems.