View Full Version : FGU crash on macOS Monterey 12.6 M1 after the update
Valyar
October 18th, 2022, 20:06
FGU crashes on the M1, Monterey 12.6. after the release today.
Some of the meaningful text from the error reporting:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: Fantasy Grounds [2324]
Path: /Applications/SmiteWorks/*/FantasyGrounds.app/Contents/MacOS/Fantasy Grounds
Identifier: unity.SmiteWorks.Fantasy Grounds
Version: 1.0 (0)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2022-10-18 22:04:26.2524 +0300
OS Version: macOS 12.6 (21G115)
Report Version: 12
Anonymous UUID: 7C2495FE-4613-52FF-F0FB-EAB85C5BD280
Time Awake Since Boot: 1500 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace DYLD, Code 1 Library missing
Library not loaded: '@executable_path/../Frameworks/UnityPlayer.dylib'
Referenced from: '/Applications/SmiteWorks/*/FantasyGrounds.app/Contents/MacOS/Fantasy Grounds'
Reason: tried: '' (code signature does not cover entire file up to signature), '' (no such file), '' (no such file)
(terminated at launch; ignore backtrace)
spoonhead
October 18th, 2022, 20:08
FGU fails to launch after updating on intel based Mac running 12.6.
No crash report though.
Log files attached
Moon Wizard
October 18th, 2022, 20:25
Please reboot your Mac completely. We have heard issues from others where the Mac is not resetting the application cache when the application files change; but that a reboot usually fixes.
Regards,
JPG
vaughnlannister
October 18th, 2022, 20:25
Same problem on my mac
spoonhead
October 18th, 2022, 20:51
Please reboot your Mac completely. We have heard issues from others where the Mac is not resetting the application cache when the application files change; but that a reboot usually fixes.
Regards,
JPG
Seems to have worked.
Moon Wizard
October 18th, 2022, 20:52
The file reported in the OP report is showing as part of the update in the patch system; so my only guess is that library is not being seen after initial update by the Mac for some reason. A reboot should fix.
I'm not sure why the file being updated does not reset whatever application caching that Mac OS is doing; but haven't been able to find any specific information on similar issues.
Regards,
JPG
dsaraujo
October 18th, 2022, 21:19
I also had silent crashes on MacOS and rebooting fixed the issue for me as well.
Valyar
October 18th, 2022, 21:40
Reboot fixes indeed. Stupid Apple.
Moon Wizard
October 18th, 2022, 22:55
Yeah, I tried to do some Internet searches today to see if I could find anything from a developer perspective, but instead I got pages and pages of generic "what to do if your apps crash" with generic fixes for end users.
If anyone comes across any information on intra-application file replacement and commands to reset application/security caches on Mac OS, please let me know.
Regards,
JPG
Reg
October 19th, 2022, 03:06
I have an Intel Mac with 12.6 and also have this issue
Rebooting has NOT solved this issue for me.
I have restored to the previous version, but now cannot join the rest of my groups who have updated.
What info do you need to help sort this out?
sirkerry
October 19th, 2022, 03:49
Please reboot your Mac completely. We have heard issues from others where the Mac is not resetting the application cache when the application files change; but that a reboot usually fixes.
Regards,
JPG
Thanks, that fixed the issue on my Intel Mac.
Moon Wizard
October 19th, 2022, 03:57
We simply provide a Intel x64 build for Mac OS. That build runs on both Intel-based Macs, and Apple Silicon-based Macs (using their Rosetta engine). I'm running on an Intel-based MacBook Pro here without issue.
In almost all cases, there is a crash report that usually gets generated when it crashes; but rarely has any interesting data other than saying a library is not being found. Either updating Rosetta on M1 Macs or rebooting the machine has fixed this issue.
In rare cases, we have had 1 or 2 reports in the past where the Mac will crash after using multiple monitors due to a Unity engine bug that we don't have any control over. You can try deleting the Preferences file while FG is not running, and try again.
"~/Library/Preferences/unity.SmiteWorks.Fantasy Grounds.plist"
Otherwise, we'll need the Player.log file from the Unity engine immediately after you try to run:
"~/Library/Logs/SmiteWorks/Fantasy Grounds/Player.log"
Regards,
JPG
Reg
October 19th, 2022, 04:14
Update - its working now
What I was doing wrong was using a restored copy of my Smiteworks folder in Application to run the updater again AFTER the reboot and the problem would just repeat.
The reboot works when it is done AFTER the crash and then just updating again
This might save some other Mac users some stress.
Moon Wizard
October 19th, 2022, 06:13
Thanks for letting us know. Hopefully, I'll eventually find a useful piece of information on this issue and how to address; but I haven't found it yet due to all the noise on the Internet related to this kind of issue for end users.
Regards,
JPG
jaharmi
October 20th, 2022, 12:58
If Smiteworks has any Apple developer technical support incidents available, that might be one route to get assistance on this. I think developer accounts get two incidents, but I'm not sure of the current situation.
Powered by vBulletin® Version 4.2.1 Copyright © 2026 vBulletin Solutions, Inc. All rights reserved.