{"id":25992,"date":"2019-07-17T16:21:31","date_gmt":"2019-07-17T20:21:31","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=25992"},"modified":"2019-07-17T16:21:31","modified_gmt":"2019-07-17T20:21:31","slug":"go64-finds-32-bit-apps","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/07\/17\/go64-finds-32-bit-apps\/","title":{"rendered":"Go64 Finds 32-bit Apps"},"content":{"rendered":"

St. Clair Software<\/a>:<\/p>\n

\n

macOS 10.15 Catalina<\/a> will not run 32-bit Mac applications. At all. Once you upgrade to Catalina, those apps won’t even launch<\/a>. <\/p>\n

To prepare, I wrote Go64<\/a>, a free application that scans your system for 32-bit apps and shows them all in one place, with version and website information to make it easier to assess whether you need to update or look for an alternative.<\/p>

[…]<\/p>\n

As they say, the devil’s in the details, and dealing with the vagaries of what goes on inside<\/em> applications got interesting. Go64 leverages Spotlight to compile a list of executables, but then does a deep dive into each 64-bit application to check for any helper apps, frameworks, services or plugins that might not<\/em> be 64-bit. While I knew this could be an issue, Howard’s work highlighted just how common it is to have a mix of executables bundled within apps. Most of the time, it’s just for expediency, and developers do the proper juggling to run the correct one, but how’s a user to know? So Go64 does a bunch of checks to look for common methods, and if it still can’t make sense of things, errs on the safe side and flags the app with a little caution icon.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n