Mac M1 FG crashes on load

[rhagelstrom]

Switching to test, FG crashes immediately and I have to delete the entire program and reinstall to get back to live.

[Moon Wizard]

This is the first I've heard of this. I checked the source control and the patch system; and that file exists in both. Also, the application runs on my MacBook Pro.

* Can you verify that the following file exists on your machine after updating to Test version?
"/Applications/SmiteWorks/Fantasy Grounds/FantasyGrounds.app/Content/Frameworks/UnityPlayer.dylib"

* Can you check that any antivirus/security solutions aren't quarantining any files?

Thanks,
JPG

[rhagelstrom]

I can reliable reproduce this error on my Mac by
Deleting /Applications/SmiteWorks
Installing with FGUWebInstall.pkg
Switch to test
Update

Curious however if I run the updater directly after that and do some flailing between updating test/live switching back and forth I was able to get test to run although I need to look into that further on why that happened.

Attached are my directory tree and my 3rd party developer exception GKE

[Moon Wizard]

I see that the file is listed in the correct location:
/Applications/SmiteWorks/Fantasy Grounds/FantasyGrounds.app/Content/Frameworks/UnityPlayer.dylib
Does it run when the file is in the correct location?

I'm not sure what the GKE is for.

JPG

[jharp]

13[Unnotarized Developer ID] P0 deny execute
anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] exists and certificate leaf[field.1.2.840.113635.100.6.1.13] exists and (certificate leaf[timestamp.1.2.840.113635.100.6.1.33] exists and certificate leaf[timestamp.1.2.840.113635.100.6.1.33] >= timestamp "20190408000000Z")

Interesting line in GKE. Although that is Google Kubernetes Engine (GKE) is integrated with Google Cloud’s Logging service. But perhaps you’ve never investigated your GKE logs, or Cloud Logging? Here’s an overview of how logging works in GKE, and how to configure, find, and interact effectively with the GKE logs stored in Cloud Logging.

[Moon Wizard]

I saw the error, but don't know why any Google-related log would have anything to do with whether the application was allowed to run. I expect something like the first error log, if the application is prevented from loading for some reason.

Regards,
JPG

[Ulric]

I think the issue is with Rossetta caching because I can solve the problem by restarting me Macbook. I never have to reinstall FGU when I get this bug.

[Moon Wizard]

@Ulric,

Thanks for the information. That's very informative.

I wonder why Rosetta wouldn't "reset" any information on an application, if the file/timestamp has changed.

Regards,
JPG

[UrsaTeddy]

This can be confirmed by myself ... but for me the problem only exists with any non-Live server.

You must restart the Macbook (I have an M1 Max) before attempting to run FGU - the Mac simply reports that it cannot open the program with an Ignore, Report, Retry option.

It is not a big deal, once you know it exists, however it can be daunting the first couple of times.

[Moon Wizard]

As I think I've mentioned in other threads, I'm not sure why Mac OS is doing this, and I can't seem to find any developer information on how to "reset" the OS caching for an app to prevent this. If you've come across anything related to this, I'd appreciate it so we can look into adding to updater.

Regards,
JPG

[Ulric]

After reading various blogs on how OAH aka Rosetta 2 operates. I don't see a way to force OAH to recache or delete the .aot files. These file reside in the SIP and the process to turn it off is more involved than a simple reboot. I recommend this blog https://ffri.github.io/ProjectChampollion/part1/ as it provides a good explanation and Part 2 covers attempts to reverse engineer Rosetta 2.

I am not currently having any problems switching between the LIVE and TEST servers. I am also not having any problems running updates on the LIVE and Test servers and the loading a campaign.

[Moon Wizard]

It only seems to occur when the files within the .app package are updated. (i.e. new builds of FG application) Currently, the changes in Test channel are ruleset only; so it wouldn't trigger.

Regards,
JPG

[Corsair31]

I encountered the same issue with my 14" MacBook Pro M1 (2021). I uninstalled FGU and reinstalled it and was able to start the app normally afterwards.

[Moon Wizard]

You only need to reboot to fix the issue, until we can figure out a fix.

Regards,
JPG

[Corsair31]

You only need to reboot to fix the issue, until we can figure out a fix.

Regards,
JPG

Understood. Thanks...

[Ulric]

It only seems to occur when the files within the .app package are updated. (i.e. new builds of FG application) Currently, the changes in Test channel are ruleset only; so it wouldn't trigger.

Regards,
JPG
Did you update any .app files in v4.3.2? I did not have a crash updating to the new test build on my M1 Mac.

[Moon Wizard]

I did; but I bet the difference was that the change in logo caused more files to be changed than normal which forced the Mac OS to rebuild more of the cached security references.

JPG