Sorry, I did a little more digging on this. My best guess is that Apple is rejecting this because they think you are using a non-public API of their own.
The OpenJFX version of MemoryPressureHandlerCocoa.mm matches what appears to be the current WebKit version. [1] Older versions appear somewhat different. Including this… #if PLATFORM(IOS) || __MAC_OS_X_VERSION_MIN_REQUIRED >= 101000 [2][3] [3] seems to show where this code was actually introduced with the above included. It might be that for a Cocoa version it was thought that this compiler directive wasn’t needed but it actually still is? Anyhow, adding something similar now might achieve a no-op that would get past them flagging this as an error. ‘locate’ on my machine doesn’t seem to show the libcache.dylib mentioned anywhere other than Xcode and other developer locations. [1] https://github.com/WebKit/webkit/blob/main/Source/WTF/wtf/cocoa/MemoryPressureHandlerCocoa.mm [2] https://opensource.apple.com/source/WebCore/WebCore-7601.5.17/platform/cocoa/MemoryPressureHandlerCocoa.mm.auto.html [3] https://fossies.org/diffs/WebKit/r174650_vs_r189384/Source/WebCore/platform/cocoa/MemoryPressureHandlerCocoa.mm-diff.html > On Jun 6, 2024, at 6:41 PM, Michael Hall <mik3h...@gmail.com> wrote: > > Odd, but searching shows this used in a different places and nowhere does it > appear anyone has made any changes to the symbol referencing code. > It seems like some applications should of used this same code as-is. > Sort of strange. > I’m done with what digging I think I’m going to do. > > GL.
