VS Code Terminal is running using Rosetta 2 on Apple M1

[gabimoncha]

• VS Code Version: 1.54.0-insider
  Commit: a699ffa
• OS Version: macOS Big Sur 11.2.1 (20D74) on Mac mini m1

Steps to Reproduce:

1. Open VS Code Terminal
2. Type arch in VS Code Terminal

The expected output should be arm64 the same as when you type arch in the standalone Terminal.

Does this issue occur when all extensions are disabled?: Yes/No
Yes

[Adam2Marsh]

Are there any updates on this issue? Lost a couple of weeks when I didn't realise the terminal was running in the wrong arch.

Thanks.

[guilhermeKodama]

I have a similar issue but I want to accomplish the opposite. I want vscode to use the terminal with Rosetta on and not off

[gabimoncha]

Then this is the wrong issue. Have you tried opening VS Code with Rosetta?

[mikehardy]

Noticed this myself - this is important because some things can't compile yet on apple silicon (e.g., react-native-google-signin/google-signin#948) so at least temporarily I need to #ifndef __arm64__ out chunks of code while building an iOS app.

As long as VSCode Terminal is running under Rosetta 2 it means I can't compile from inside VSCode easily (the symbol is not defined, and then the compile fails) - compiling in Terminal outside VSCode works.

[jersearls]

Anyone have a solution to this? Is there a setting in VScode to not emulate x86 in the terminal?