John Othwolo

I can confirm that this happens on the latest nightly build on Mojave 10.14.2.

I believe this can be solved by adding the following to the CmakeLists.txt: ` set_target_properties(vita3k PROPERTIES LINK_FLAGS "-rpath @executable_path/Resources/") ` according to [this](https://blog.krzyzanowskim.com/2018/12/05/rpath-what/)

@negamalireid The problem might here [a3aa6a6](https://github.com/Vita3K/Vita3K/commit/c9e25ec8904982ca662340700597266e30804ef3#diff-c2714bb72c4019858eab3c81e9453c72443e347bb1b62ce9b962ef188069019bR135-R139). Though I don't see how a conditional statement could've messed things up. @strikersh could you check it out? UPDATE: Turns out the release dates...

Same problem in Mojave. Both Chrome and Safari.

You could compile the kernel using patches from [this version](https://github.com/Shaneee/Mojave_AMD_XNU). I can't create DarwinBuild patches because I don't know how the build-system works.

Updated link [ftp://ftp-osl.osuosl.org/pub/libpng/src/libpng16/libpng-1.6.34.tar.xz](http://ftp-osl.osuosl.org/pub/libpng/src/libpng16/libpng-1.6.34.tar.xz)

I believe that's an issue for the Whatsapp team to solve...or is it? According to the XDA, the apps check the build.prop for the device info. This file is located...

The shell can be used to change the properties, but it's limited (used it) but I think it has the setprop tool (no sure its of name).

Can somebody please diagnose the crashes on OS X, half of the apps that "WORK" actually crash, even angry birds! IDK much of how the runtime works, no matter how...

I really despise the fact that there isn't a response.