jellyfin / jellyfin-media-player

Jellyfin Desktop Client
GNU General Public License v2.0
2.87k stars 297 forks source link

Jellyfin Client 1.10.1 Crash on MacOS Ventura 13.6.3 #668

Open MorrisC2010 opened 1 month ago

MorrisC2010 commented 1 month ago

Translated Report (Full Report Below)

Process: Jellyfin Media Player [26978] Path: /Applications/Jellyfin Media Player.app/Contents/MacOS/Jellyfin Media Player Identifier: tv.jellyfin.player Version: 1.10.1 (1.10.1) Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501

Date/Time: 2024-05-27 13:29:15.9112 -0500 OS Version: macOS 13.6.3 (22G436) Report Version: 12 Anonymous UUID: CDC2283B-F2A8-1BFB-675E-E14BB97633C5

Sleep/Wake UUID: 1C396365-E0C5-4E1C-A4C4-85C687594A53

Time Awake Since Boot: 25000 seconds Time Since Wake: 349 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace DYLD, Code 4 Symbol missing Symbol not found: _$sSo13NSWindowLevela6AppKit01_cdD23NumericRawRepresentableACMc Referenced from: <2E98933C-5ADA-3FCB-97DE-95A140BA166D> /Applications/Jellyfin Media Player.app/Contents/Frameworks/libmpv.2.dylib (built for macOS 14.0 which is newer than running OS) Expected in: <956685F7-4174-3135-911D-CF52948CE09A> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (terminated at launch; ignore backtrace)

Currently upgrading to MacOS 14 to see if that fixes the issue but I would have preferred not to.

Sp9nky commented 1 month ago

same here on 13.6.7

rohankandwal commented 1 month ago

I got stuck with the ignore and download buttons not working so thought of upgrading to the latest version 1.10.1, this version crashes with same error as reported in this bug. However, if i download the old version 1.10.0 and move that to application directory, I get same crash in the older version as well. So, now I can't use new or old version.

mjpieters commented 1 month ago

This applies to macos 12.7.4 as well.

mjpieters commented 1 month ago

Right, as per this comment, 1.10.x requires macos 14 or newer when running on Apple silicon, so this is 'by design'. Sigh.

siggisigg commented 3 weeks ago

I have the same issue, does building from source work as a work around ?