You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using sharp in our Publii app. We have got reports that the latest release of our app is not working on macOS Catalina 10.15.7.
The non-working version of app uses sharp v.0.31.2 while the latest working version uses sharp v.0.30.5
So I assume that something has been broken between these versions.
The app crashes during start and suggests sending report to Apple. I will also add that I have received information that the app perfectly works on macOS 11., 12. and 13.* both on Intel and M1 chips.
Can I ask if it seems to be a sharp-related issue?
In the report to Apple I have found such things:
Time Awake Since Boot: 7500 seconds
Time Since Wake: 4700 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x4] Symbol missing
Dyld Error Message:
Symbol not found: _pthread_jit_write_protect_supported_np
Referenced from: /Applications/[Publii.app/Contents/Resources/app.asar.unpacked/node_modules/sharp/build/Release/../.././vendor/8.13.3/darwin-x64/lib/libvips-cpp.42.dylib](http://publii.app/Contents/Resources/app.asar.unpacked/node_modules/sharp/vendor/8.13.3/darwin-x64/lib/libvips-cpp.42.dylib)
Expected in: /usr/lib/libSystem.B.dylib
Hi,
We are using sharp in our Publii app. We have got reports that the latest release of our app is not working on macOS Catalina 10.15.7.
The non-working version of app uses sharp v.0.31.2 while the latest working version uses sharp v.0.30.5
So I assume that something has been broken between these versions.
The app crashes during start and suggests sending report to Apple. I will also add that I have received information that the app perfectly works on macOS 11., 12. and 13.* both on Intel and M1 chips.
Can I ask if it seems to be a sharp-related issue?
In the report to Apple I have found such things:
The text was updated successfully, but these errors were encountered: