View Full Version : FGU crashing
Abrahel Lunanegra
May 16th, 2021, 08:54
Hi guys,Iv been having this issue since the last update. (Mac Mini m1 chip,16 gb ram)
żAny idea what,s going on?
Your are doing a great job
Thanks
Process: Fantasy Grounds [993]
Path: /Applications/SmiteWorks/*/FantasyGrounds.app/Contents/MacOS/Fantasy Grounds
Identifier: unity.SmiteWorks.Fantasy Grounds
Version: ???
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: Fantasy Grounds [993]
User ID: 501
Date/Time: 2021-05-16 09:50:52.056 +0200
OS Version: macOS 11.3.1 (20E241)
Report Version: 12
Anonymous UUID: 9BF8B458-2A3A-4CAC-42A9-5B7632C92DCA
Sleep/Wake UUID: F9C1F6F4-0FA0-425D-864E-5B89A9B6223C
Time Awake Since Boot: 1600 seconds
Time Since Wake: 800 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: EXC_ARM_BREAKPOINT at 0x00007ffdffe0b360 (brk 1)
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [993]
Application Specific Information:
rosetta error: /var/db/oah/63b8ff35a4bc93e2da17585c4ea5ae7f225c3b5f3c7ebcea01 6bd32f0f335c15/90e9bb1782fcf5841462b29a7a5a0a64562d61ddc96d79a998 fb36f10ada2a7e/Fantasy Grounds.aot: attachment of code signature supplement failed: 3
Thread 0 Crashed:
0 runtime 0x00007ffdffe0b360 0x7ffdffdb8000 + 340832
1 runtime 0x00007ffdffe0b3ac 0x7ffdffdb8000 + 340908
2 runtime 0x00007ffdffdc6004 0x7ffdffdb8000 + 57348
3 runtime 0x00007ffdffdc754c 0x7ffdffdb8000 + 62796
4 runtime 0x00007ffdffdc7044 0x7ffdffdb8000 + 61508
5 runtime 0x00007ffdffdb92a0 0x7ffdffdb8000 + 4768
6 dyld 0x0000000200a95000 0x200a95000 + 0
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000003 x2: 0x000000000000003c x3: 0x000000000000002c
x4: 0x0000000000000303 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x000000000000236b
x8: 0x00007ffdffe38000 x9: 0x0000000000000000 x10: 0x00007ffdffe2ec5d x11: 0x0000000000000000
x12: 0x00007ffdffe226e0 x13: 0x00007ffdffe226d0 x14: 0x00007ffdffe1da76 x15: 0x0000000000000020
x16: 0xffffffffffffffe1 x17: 0x00007ffdffe0f7e4 x18: 0x000000030537a063 x19: 0x00007ffdffe2eb78
x20: 0x000000030537a718 x21: 0x00000001007dd000 x22: 0x0000000000000103 x23: 0x00000001007dd000
x24: 0x0000000000000003 x25: 0x0000000000000001 x26: 0x0000000305379b70 x27: 0x00007ffdffdb8000
x28: 0x0000000000000001 fp: 0x0000000305378910 lr: 0xe4457ffdffe0b358
sp: 0x00000003053788f0 pc: 0x00007ffdffe0b360 cpsr: 0x60000000
far: 0x00007ffdffe39000 esr: 0xf2000001
Binary Images:
0x200a95000 - 0x200b30fff dyld (851.27) <7EAA668B-F906-3BAA-A980-139BBE6E8766> /usr/lib/dyld
0x7ffdffdb8000 - 0x7ffdffe2bfff +runtime (203.42) <A7DF9462-ECE5-3ED4-8C57-BC56BA4793EA> /Library/Apple/*/runtime
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=1328K resident=0K(0%) swapped_out_or_unallocated=1328K(100%)
Writable regions: Total=18.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=18.8M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
STACK GUARD 56.0M 1
Stack 8176K 1
VM_ALLOCATE 10.5M 1
VM_ALLOCATE (reserved) 32K 1 reserved VM address space (unallocated)
__DATA 288K 4
__DATA_CONST 32K 1
__LINKEDIT 272K 4
__TEXT 1088K 2
mapped file 4.7G 8
=========== ======= =======
TOTAL 4.8G 23
TOTAL, minus reserved VM space 4.8G 23
Model: Macmini9,1, BootROM 6723.101.4, proc 8:4:4 processors, 16 GB, SMC
Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin
Memory Module: LPDDR4
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Apr 2 2021 00:48:12 version 18.52.1.2.7.8.116 FWID 01-9f7b4413
Bluetooth: Version 8.0.4d18, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
USB Device: USB 3.1 Bus
USB Device: USB 3.1 Bus
USB Device: USB 3.0 Bus
USB Device: webcam
USB Device: RODE NT-USB
Thunderbolt Bus: Mac mini, Apple Inc.
Thunderbolt Bus: Mac mini, Apple Inc.
Moon Wizard
May 17th, 2021, 04:59
The error looks like an issue with the Rosetta engine on the M1 Mac. We haven't heard any other reports, so it doesn't appear to be a general issue.
Can you try renaming the SmiteWorks directory in your user folder; un-installing FG; and re-installing with the default settings from the web site?
There is not much information online about this error, so the only thing I can find was something about directory access. I'm hoping that a fresh install will clear it up.
Thanks,
JPG
matjam
May 17th, 2021, 06:54
Moon, it might be something to do with Big Sur and application signatures.
attachment of code signature supplement failed: 3
Seeing the same error in people reporting issues with other applications running stuff under big sur. There might need to be some fix in the build done...
https://community.cypress.com/t5/Knowledge-Base-Articles/Eclipse-IDE-for-ModusToolbox-Quits-Unexpectedly-on-macOS-Big-Sur/ta-p/275586 is interesting, maybe there's some attr that needs to be cleared because the code was updated and there's some signature saved somewhere? Apple have changed this stuff so much the last few years it's hard to keep track of all the edge cases.
Moon Wizard
May 17th, 2021, 18:16
That's the error that I saw as well; but it appears to be a relatively new issue given the lack of information. I saw one random report on Google of changing folder attributes; so that's why I recommended a full re-install into the default location.
There is nothing specific to making builds for Mac OS (Intel chips) that we have available via the Unity build that affects the Rosetta behaviors.
Regards,
JPG
digirigawa
May 18th, 2021, 19:12
It's likely caused by some automatically installed system data / security update. You probably have it enabled in "Software Updates > Advanced" section in your Mac. I have and FGU crashes just like posted above - yet it worked fine couple days ago.
tcrowbar
May 20th, 2021, 15:24
I am having the same problem when I updated my FGU on my Mac M1 computer. I did the suggested "renaming the SmiteWorks directory in your user folder; un-installing FG; and re-installing with the default settings from the web site". That worked initially but 8 hours later its not working again. FantasyGrounds.app quit unexpectedly when I try to open it. It says "File can't be found" when I try to reopen it too. The file does appear to be there when I checked.
Is there a fix for this yet?
I am going to try to reinstall it again but it doesn't make sense to have to reinstall it literally every time I try to use the program!
Process: Fantasy Grounds [30119]
Path: /Applications/SmiteWorks/*/FantasyGrounds.app/Contents/MacOS/Fantasy Grounds
Identifier: unity.SmiteWorks.Fantasy Grounds
Version: ???
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: Fantasy Grounds [30119]
User ID: 501
Date/Time: 2021-05-20 09:17:06.440 -0500
OS Version: macOS 11.3.1 (20E241)
Report Version: 12
Anonymous UUID: B7748007-711C-1A6A-1B69-CF8511EC64FE
Sleep/Wake UUID: 3E52AF8B-68CC-47EE-B7C3-F5695014DCB0
Time Awake Since Boot: 760000 seconds
Time Since Wake: 25000 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: EXC_ARM_BREAKPOINT at 0x00007ffdfffb3360 (brk 1)
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [30119]
Application Specific Information:
rosetta error: /var/db/oah/63b8ff35a4bc93e2da17585c4ea5ae7f225c3b5f3c7ebcea01 6bd32f0f335c15/f009345f363cd8dabef6c7aaa712150d860301ad30ae4274cd f4c6b43172da32/Fantasy Grounds.aot: attachment of code signature supplement failed: 3
Thread 0 Crashed:
0 runtime 0x00007ffdfffb3360 0x7ffdfff60000 + 340832
1 runtime 0x00007ffdfffb33ac 0x7ffdfff60000 + 340908
2 runtime 0x00007ffdfff6e004 0x7ffdfff60000 + 57348
3 runtime 0x00007ffdfff6f54c 0x7ffdfff60000 + 62796
4 runtime 0x00007ffdfff6f044 0x7ffdfff60000 + 61508
5 runtime 0x00007ffdfff612a0 0x7ffdfff60000 + 4768
6 ??? 0x0000000000000003 0 + 3
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000003 x2: 0x000000000000003c x3: 0x000000000000002c
x4: 0x0000000000000303 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x000000000000236b
x8: 0x00007ffdfffe0000 x9: 0x0000000000000000 x10: 0x00007ffdfffd6c5d x11: 0x0000000000000000
x12: 0x00007ffdfffca6e0 x13: 0x00007ffdfffca6d0 x14: 0x00007ffdfffc5a76 x15: 0x0000000000000020
x16: 0xffffffffffffffe1 x17: 0x00007ffdfffb77e4 x18: 0x0000000309dc1053 x19: 0x00007ffdfffd6b78
x20: 0x0000000309dc1708 x21: 0x0000000102cbc000 x22: 0x0000000000000103 x23: 0x0000000102cbc000
x24: 0x0000000000000003 x25: 0x0000000000000001 x26: 0x0000000309dc0b60 x27: 0x00007ffdfff60000
x28: 0x0000000000000001 fp: 0x0000000309dbf900 lr: 0xaf65fffdfffb3358
sp: 0x0000000309dbf8e0 pc: 0x00007ffdfffb3360 cpsr: 0x60000000
far: 0x00007ffdfffe1000 esr: 0xf2000001
Binary Images:
0x202ffd000 - 0x203098fff dyld (851.27) <7EAA668B-F906-3BAA-A980-139BBE6E8766> /usr/lib/dyld
0x7ffdfff60000 - 0x7ffdfffd3fff +runtime (203.42) <A7DF9462-ECE5-3ED4-8C57-BC56BA4793EA> /Library/Apple/*/runtime
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=1328K resident=0K(0%) swapped_out_or_unallocated=1328K(100%)
Writable regions: Total=18.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=18.8M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
STACK GUARD 56.0M 1
Stack 8176K 1
VM_ALLOCATE 10.5M 1
VM_ALLOCATE (reserved) 32K 1 reserved VM address space (unallocated)
__DATA 288K 4
__DATA_CONST 32K 1
__LINKEDIT 272K 4
__TEXT 1088K 2
mapped file 4.7G 8
=========== ======= =======
TOTAL 4.8G 23
TOTAL, minus reserved VM space 4.8G 23
Model: MacBookPro17,1, BootROM 6723.101.4, proc 8:4:4 processors, 16 GB, SMC
Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin
Memory Module: LPDDR4
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Apr 2 2021 00:48:12 version 18.52.1.2.7.8.116 FWID 01-9f7b4413
Bluetooth: Version 8.0.4d18, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: USB3.1 Hub
USB Device: USB2.1 Hub
USB Device: Yeti Stereo Microphone
USB Device: HD Pro Webcam C920
USB Device: USB 3.1 Bus
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thunderbolt Bus: MacBook Pro, Apple Inc.
LordEntrails
May 20th, 2021, 15:48
Check your security. It sounds like your security software is quarantining the program after it runs once. It probably sees it having outside computer connections and so thinks it's a security threat. Whitelist FG or add it to your exclusions. Depending upon how "smart" your security software is, you might have to do this every time you update the FG program (not DLC).
Abrahel Lunanegra
May 24th, 2021, 09:07
Hi guys. After deleting everything and fresh-installing it seemed to work fine until today. Same issue with rosetta....
Moon Wizard
May 24th, 2021, 17:54
As mentioned above, it looks like Rosetta was updated in a way that causes incompatibilities. I'm not sure why it changes from working to non-working over the course of days; it seems like it should either work or not work.
I would report in the Rosetta support channels.
Regards,
JPG
Moon Wizard
May 24th, 2021, 18:00
Also, from other posts I've read online, it could be that the M1 version of Big Sur is somehow quarantining the files, which can cause issues. Something to do with a "com.apple.quarantine" flag on downloaded files...
I'm not familiar enough with Mac OS to know how to prevent that or disable. Perhaps some sort of firewall setting on Big Sur?
Regards,
JPG
zeletrik
May 25th, 2021, 17:20
FYI, I also faced the issue with an M1 mac, on macOS 11.3.1. Today I updated to 11.4 and the issue is gone so far.
Moon Wizard
May 25th, 2021, 17:45
Thanks for letting us know.
Regards,
JPG
Abrahel Lunanegra
May 25th, 2021, 20:59
Update:
Working ok after the MacOs update 11.4 though the "update" button is highlighted in red no matter how many times you update it....
MisterUrth
May 26th, 2021, 01:06
I am also having this issue, but I'm still running 11.3.1. Gonna update to 11.4 and see how it goes.
charmov
May 26th, 2021, 03:06
Updating to 11.4 big sur seems to have fixed it for me. i hadn't logged on in about 2 weeks and today i got the above message error. i upgraded big sur and now it's AOK.
MisterUrth
May 26th, 2021, 03:16
Yes, 11.4 fixed it for me too! :D
charmov
May 29th, 2021, 04:30
Upon trying to start fantasy grounds unity today, i am experiencing the same issue. I can't even open FGU, it immediately takes me to the error page.
charmov
May 29th, 2021, 16:23
Upon trying to start fantasy grounds unity today, i am experiencing the same issue. I can't even open FGU, it immediately takes me to the error page.
An uninstall followed by a fresh re-install seems to have resolved the issue for now.
Abrahel Lunanegra
June 5th, 2021, 19:46
Same issue again.....
charmov
June 5th, 2021, 19:49
Same issue again.....
It happens to me just a couple of days ago. I had to uninstall and reinstall again. I think something with the updater was causing big Sur m1 to crash. It's working now for me. Hopefully a reinstall helps you. If not maybe contact them directly?
LordEntrails
June 5th, 2021, 22:13
Same issue again.....
This lacks any details that would actually be useful for us to be helpful to you. If needed, please see the link in my signature of default types of things you can include to help us help you.
BrouH
October 14th, 2021, 18:24
Hello, I'm having a similar crashing issue, apparently because of Rosetta (I'm on a M1 Macbook Pro). I first had this issue around the time this thread was created, but doing a big system update I had pending solved it. Lately, I had been having these crashes again, but keeping my OS up to date and separately launching the FGU updater and doing the updates solved it.
This time, everything is up to date, and re-installing FGU like what has been suggested here doesn't change a thing.
I'm on MacOS Big Sur 11.6.
Here's the crash log:
Process: Fantasy Grounds [1729]
Path: /Applications/SmiteWorks/*/FantasyGrounds.app/Contents/MacOS/Fantasy Grounds
Identifier: unity.SmiteWorks.Fantasy Grounds
Version: ???
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: Fantasy Grounds [1729]
User ID: 501
Date/Time: 2021-10-14 19:22:06.352 +0200
OS Version: macOS 11.6 (20G165)
Report Version: 12
Anonymous UUID: 2A496966-0753-2714-762A-A98A7C6AA313
Time Awake Since Boot: 1700 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: EXC_ARM_BREAKPOINT at 0x00007ffdffe26d38 (brk 1)
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [1729]
Application Specific Information:
rosetta error: /var/db/oah/223263137464320_223263137464320/36471f0dde6f34d5535c8cb65bd7ec269da092e7b69ad25479 80c654064f8986/Fantasy Grounds.aot: attachment of code signature supplement failed: 3
Thread 0 Crashed:
0 runtime 0x00007ffdffe26d38 0x7ffdffe0a000 + 118072
1 runtime 0x00007ffdffe26d80 0x7ffdffe0a000 + 118144
2 runtime 0x00007ffdffe166e4 0x7ffdffe0a000 + 50916
3 runtime 0x00007ffdffe17df4 0x7ffdffe0a000 + 56820
4 runtime 0x00007ffdffe175ec 0x7ffdffe0a000 + 54764
5 runtime 0x00007ffdffe0e440 0x7ffdffe0a000 + 17472
6 dyld 0x000000020292b000 0x20292b000 + 0
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000003 x2: 0x000000000000003c x3: 0x000000000000002c
x4: 0x0000000000000303 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x000000000000229b
x8: 0x00007ffdffe46000 x9: 0x0000000000000000 x10: 0x00007ffdffe3c094 x11: 0x0000000000000000
x12: 0x00000000ffffffff x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x00007ffdffe2d758
x16: 0xffffffffffffffe1 x17: 0x00007ffdffe367b6 x18: 0x000000030916d013 x19: 0x00007ffdffe3bfd0
x20: 0x000000030916ca18 x21: 0x0000000102743000 x22: 0x0000000000000004 x23: 0x0000000102743000
x24: 0x0000000000000003 x25: 0x0000000000000001 x26: 0x000000030916cb30 x27: 0x000000020292b000
x28: 0x0000000309175900 fp: 0x000000030916b910 lr: 0x00007ffdffe26d30
sp: 0x000000030916b8f0 pc: 0x00007ffdffe26d38 cpsr: 0x60000000
far: 0x00007ffdffe3bfd0 esr: 0xf2000001
Binary Images:
0x20292b000 - 0x2029c6fff dyld (852.2) <0CC19410-FD43-39AE-A32A-50273F8303A4> /usr/lib/dyld
0x7ffdffe0a000 - 0x7ffdffe39fff runtime (203.58) <BBDCFB04-7B39-3FDE-90D3-A6E55EE628E7> /usr/libexec/rosetta/runtime
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=1048K resident=0K(0%) swapped_out_or_unallocated=1048K(100%)
Writable regions: Total=18.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=18.8M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
STACK GUARD 56.0M 1
Stack 8176K 1
VM_ALLOCATE 10.5M 1
VM_ALLOCATE (reserved) 44K 2 reserved VM address space (unallocated)
__DATA 288K 4
__DATA_CONST 32K 1
__LINKEDIT 272K 4
__TEXT 816K 2
mapped file 4.7G 8
=========== ======= =======
TOTAL 4.8G 24
TOTAL, minus reserved VM space 4.8G 24
Model: MacBookPro17,1, BootROM 6723.140.2, proc 8:4:4 processors, 16 GB, SMC
Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin
Memory Module: LPDDR4
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Aug 18 2021 22:48:53 version 18.50.40.11.7.8.123 FWID 01-3ed0e3a2
Bluetooth: Version 8.0.5d7, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: USB 3.1 Bus
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thunderbolt Bus: MacBook Pro, Apple Inc.
Thanks for any kind of help or suggestion you might have! I'm the DM for a campaign and the players are somewhat close to the end :( I'm gonna get fireballed :D
tcrowbar
October 14th, 2021, 19:28
I've continued to have this problem for months. Frankly it's disappointing to see the issue continue for 6 months now. At this point my fix is I make a backup of the Applications/SmiteWorks/Fantasy Grounds folder before I do a software update to FG or turn off my computer. The problem seems to happen after an update to the software or the computer is restarted. The "fix" is to copy the backed up Fantasy Grounds folder over the new updated folder. When you do that you can open the FantasyGrounds.app again. Never do an update right before your game starts and start up your fantasy grounds hours before your game and leave it open. That's my suggestion. Would be great if it got fixed through.
BrouH
October 14th, 2021, 20:12
Thanks, I'll start doing that once FG works once more!
Yeah it's very disappointing, FG (+ official D&D products I bought) costs quite a bit of $$ for something that might refuse to work randomly. After my current campaign, if the problem persists I'll definitely consider moving to something else... It's hard enough to have me and my players available often enough, if the software isn't reliable I don't think I'll have much of a choice :(
Trenloe
October 14th, 2021, 20:27
This thread has been a mixture of updates fixed my issues, now it's back again, now it's not - and also suggestions from people (check quarantined files, flags, etc.) without any further feedback from some users. It hasn't got to the bottom of the issue and today's post from @BrouH is the first post in this thread for over 4 months. Without SmiteWorks knowing there are continual issues then they don't know there are issues... I know it's frustrating having issues. If you're having issues please keep working with the suggestions from FG devs and community members on the forums - provide feedback to those suggestions, work with the SmiteWorks team so that they can try to identify the issue/s and hopefully fix them for everyone.
BrouH
October 14th, 2021, 20:35
Yeah I'll try to keep this post updated with any successes/failures, but I only have @tcrowbar's suggestion left to try and it's a workaround, not a real fix. Hopefully a real solution will arrive sometime.
I guess we aren't that many using FGU on macOS and fewer to post here about these serious issues. I do keep my fingers crossed. FG most definitely saved the day for me during this pandemic by allowing me and my friends to actually play some TTRPG, I wouldn't move to another platform unless it's the only viable option for my games and I sure hope I can keep using it for a long time.
Moon Wizard
October 14th, 2021, 22:49
There is definitely less Mac users than Windows users in general, but we haven't gotten any recent reports of this issue until now. Every time that we've encountered this issue, the user has completed a pending system update, and everything is working again.
You can even see in the error you pasted that Rosetta is not accepting the certificate for some reason; which is beyond our control.
Application Specific Information:
rosetta error: /var/db/oah/223263137464320_223263137464320/36471f0dde6f34d5535c8cb65bd7ec269da092e7b69ad25479 80c654064f8986/Fantasy Grounds.aot: attachment of code signature supplement failed: 3
Regards,
JPG
tcrowbar
October 15th, 2021, 02:12
Yeah I'll try to keep this post updated with any successes/failures, but I only have @tcrowbar's suggestion left to try and it's a workaround, not a real fix. Hopefully a real solution will arrive sometime.
I guess we aren't that many using FGU on macOS and fewer to post here about these serious issues. I do keep my fingers crossed. FG most definitely saved the day for me during this pandemic by allowing me and my friends to actually play some TTRPG, I wouldn't move to another platform unless it's the only viable option for my games and I sure hope I can keep using it for a long time.
Oh another suggestion is if you are having the problem and haven't actually made a manual backup of the folder you can try to do a "time machine" recovery of the folder Applications/SmiteWorks/Fantasy Grounds to when you know it was working. I've had to do that. Another thing you can do is if you have a second mac with a working fantasy grounds you can make a copy of the folder and bring it to the mac with the non working fantasy grounds. I've done that before too. Luckily I've had two macs. Through all this I came to the conclusion to not update much and not turn off the computer much and make a backup copy of the folder Applications/SmiteWorks/Fantasy Grounds. I actually make a copy of the folder every time I backup so I have backup folders named Fantasy Grounds 1, Fantasy Grounds 2, Fantasy Grounds 3, etc, etc for every day I've decided to do an update. Before I've done the update of course. Maybe that's overkill.
Yeah I understand I suppose I should be reporting problems every time I have them but it's been fairly consistent and I don't want to be a complainer that reports constantly that I have the same problem.
Moon Wizard
October 15th, 2021, 04:57
I just wish there was something obvious related to Rosetta that we could do; since it seems to be a problem specifically with M1 Macs and Rosetta implementation. Since our build is for Intel Macs, and it's supposed to run seamlessly on M1 Macs via Rosetta; I'm not sure why the M1 Macs are modifying the files so they don't work on updates.
Regards,
JPG
BrouH
October 15th, 2021, 07:04
Thanks everyone for your answers. I'll look into the Time Machine trick as well!
I understand that Rosetta is to blame, though I have to say I don't understand much about the crash report.
I'll add that I update my mac manually, but I haven't been careful about that since it was actually something that would solve the crash issue for me, not trigger it (from my small experience). FG worked well a few days ago when I did some prep and I haven't done any update since (none were available to me). So... Rosetta seems to get updates and changes without my validation.
BronzeDodger
October 15th, 2021, 08:22
Shot in the dark in case SW hasn't had the bad luck to run into this (I don't know MACs at all, but ran into cert errors on iOS devices and have been trying to figure out how/if a user can safely workaround it). It does impact MACs as well but I don't know if the dots connect to FGU or not - so purely a "in case this helps" post.
https://sslmate.com/blog/post/apples_new_ct_policy
BronzeDodger
October 18th, 2021, 15:58
Another nugget - again not sure if it applies to FGU specifically but Apple devices not accepting certs from Let's Encrypt is a known issue (so just in case it's broader and FGU uses a similar type of cert thought I'd share this).
https://developer.apple.com/forums/thread/134146
Moon Wizard
October 18th, 2021, 16:23
We don't use certificates from "Let's Encrypt", and the references you posted are for server side certificates not code signing certificates which is the Rosetta issue.
Regards,
JPG
tcrowbar
October 21st, 2021, 00:58
Just because you wanted us to report when it happens. I was going to start my traveller game tonight and it happened again. Pulled in a copy that I backed up last night and it works again.
Moon Wizard
October 21st, 2021, 04:37
I have no idea why the MacOS keeps killing it; and I'm no Mac expert. We're going to need some help identifying why the MacOS gatekeeper/security or emulation software keeps failing.
Regards,
JPG
jaharmi
July 25th, 2022, 15:06
There seem to be a similar issue encountered on an Apple Silicon device with the macOS Ventura beta (https://www.fantasygrounds.com/forums/showthread.php?74547-Fantasy-Grounds-Unity-immediately-crashes-in-macOS-Ventura&p=657346). The posted gists look like some of the other problems that have been previously posted here.
Since these existing problems and the reported crash on macOS Ventura beta may be related to the same ongoing but sporadic problem, it makes sense to report it with Apple's Feedback app. Anyone can open the Feedback Assistant and submit a report using their own Apple ID about any current or beta version of macOS (https://support.apple.com/guide/feedback-assistant/welcome/mac). Anyone who does so could post their Feedback ID here or in the macOS Ventura beta thread (https://www.fantasygrounds.com/forums/showthread.php?74547-Fantasy-Grounds-Unity-immediately-crashes-in-macOS-Ventura&p=657346).
I'm not sure if any of the posts involve this problem on an Intel Mac.
On the SmiteWorks end, if the company has a paid developer account — which it appears to, given the Developer ID (https://developer.apple.com/support/developer-id/) signature on Fantasy Grounds Unity — then the company could elect to submit a Technical Support Incident for code level support (https://developer.apple.com/support/technical/). Each developer account starts with two TSIs per year. This might help get to the bottom of the problem, particularly if it involves code signing and/or Rosetta's Intel translation.
I understand that it may not be the highest priority issue for SmiteWorks. If it affects Apple Silicon devices, though, it stands to reason it's only going to get more common as more of those devices are sold and replace Intel Macs. This probably needs to be weighed against the timeline for an Apple Silicon native of Unity and FGU and the overall number/percentage of Macs used for FGU.
Moon Wizard
July 25th, 2022, 18:38
Again, closing this thread as it's a year old, and I responded in the other thread.
JPG
Powered by vBulletin® Version 4.2.1 Copyright © 2026 vBulletin Solutions, Inc. All rights reserved.