Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 1
    The executable file is a plain-text bash script. It is NOT Intel binary. Commented Mar 14, 2023 at 19:21
  • The executable would be Chrome Commented Mar 14, 2023 at 19:27
  • 1
    @Allan This issue occurs even if the only files in the bundle are the plist and shell script. Somehow MacOS is throwing the x86 flag on scripts. Commented Aug 3, 2024 at 17:11
  • Agreed. Although this answer is "common sense", it's not correct. Something about Rosetta 2's detection is broken for scripted launchers. developer.apple.com/forums/thread/761342 Commented Aug 6, 2024 at 14:59
  • Slight update, @kyle-berezin 's proposed LSArchitecturePriority seems to fix this, but only for new installs. Once Rosetta 2 has inferred Intel for a scripted Application launcher, it never seems to forget this. Reported to Apple as FB14684491. Hopefully they'll consider fixing this although the sentiments from the developer forum suggest otherwise. Commented Aug 6, 2024 at 16:01