p.s., as you can probably tell, my app still uses 3.4.6, but I get the same problem when trying 4.0.5.1.
Critical problem on OS X SierraSolved
Hi Sam/Wyatt, I hope you guys can help me with this ASAP. I'm experiencing a problem that's preventing my users from installing my app on OS X Sierra.
In my Installer, with elevated privileges, I run a very simple C executable at the end of installation which looks like this:
int main (int argc, const char * argv[]){ CheckAndSavePKey(0, TA_SYSTEM); result = UseTrial(TA_SYSTEM); return result;}
The problem is that this causes the installation to fail. On earlier OS X versions, there were no problems with this code and everything worked great.
For the sake of testing, I ran the above executable directly from the command line in Sierra, and I got this message:
objc[584]: Objective-C garbage collection is no longer supported.
In the Console log, this appears to cause a crash in Sierra.
I don't get this message or crash on earlier versions of OS X.
Any thoughts? PLEASE HELP!!! 🙂
We're going to look into this.
A colleague forwarded me this:https://support.apple.com/en-us/HT204899
Could it be that the TA_SYSTEM flag tries to put some files into /System? Just a guess. But maybe this is why things are failing.
If so, I'd appreciate any help in getting around this ASAP. Thanks.
Hmm, maybe that's not it. Changing to TA_USER still causes the problem.
TurboActivate, TurboFloat, and TurboFloatServer are all built with the "optional gc" flag (meaning Garbage Collection *is not used*, however our libraries will load in apps that use garbage collection).
Long story short: recompile your app to not use garbage collection.
Google "Objective-C garbage collection is no longer supported" for a long list of articles and forum posts describing how to fix the compilation of your app to not use the garbage collector.