debugserver is x86_64 binary running in translation, attached failed. Could not attach to pid :

Question

I just shifted my Xcode project from my Intel Mac to Apple M1 Chip. The code is compiled successfully on M1 Chip but once I tried to run it on simulator it shows the following error.

debugserver is x86_64 binary running in translation, attached failed.

I have checked the "Open using Rosettea" option for Xcode but it still not running M1 machine.

Hey! Did you find a solution to this? I'm having the same issue. The build won't succeed without using Rosetta and it will fail to attach if I use Rosetta. — Harshvardhan Arora, Aug 31 '22 at 07:32
@QaziAmmar were you able to solve this issue, I am having same but none of the answers helping. I am having Mac Intel machine and simulator is not getting attached to xcode in debug mode. — Mrunal, Nov 11 '22 at 12:55
Same here: https://stackoverflow.com/questions/74366053/xcode-14-is-not-getting-attached-to-simulator-in-debug-mode — Mrunal, Nov 22 '22 at 11:58

score 24 · Answer 1 · answered Aug 16 '22 at 06:59

24

I had a problem running watchOS simulator.

Solution that worked for me:

Quit Xcode
Right click on Xcode, press "Get Info"
Make sure that "Open using Rosetta" is not selected(see image)
Delete derived data(don't know if this is required)
Reopen Xcode and run your app

answered Aug 16 '22 at 06:59

stackich

3,607
3
17
41

1

I have mentioned in the question that I have tried with both while selecting and unselecting the "Open using Roseeta" its now working. – Qazi Ammar Aug 16 '22 at 07:10
ok, if it is working now, you can share your solution with others :D – stackich Aug 16 '22 at 08:04
1

No its not working for me with both scenarios – Qazi Ammar Aug 16 '22 at 12:39
1

then probably you mistyped `its now working.` instead of `its not working.` :D – stackich Aug 16 '22 at 15:39
yes its a typo. I have to type its not working – Qazi Ammar Aug 17 '22 at 14:34

score 14 · Accepted Answer · edited Mar 24 '23 at 22:31

14

With Mac M1 you could also exclude arm64 in your target

Target > Build Settings > Excluded Architectures --> add "arm64"

If an update isn’t available from the vendor, temporarily use the EXCLUDED_ARCHS build setting to exclude arm64 for the simulator SDK as shown in the figure below. Do not exclude arm64 for any other SDK.

edited Mar 24 '23 at 22:31

Arshad Shaik

1,095
12
18

answered Jul 12 '22 at 18:33

Thermech

4,371
2
39
60

"arm64e" was already there. However changing it into "arm64" did not solve the problem. – stackich Aug 16 '22 at 06:38
@Thermech if we exclude arm64 there will be any problem with the app ? – Arshad Shaik Mar 23 '23 at 11:23
@ArshadShaik To avoid any impact, you could exclude it only for iosSimulator like proposed by Apple here https://developer.apple.com/documentation/technotes/tn3117-resolving-build-errors-for-apple-silicon#Update-pre-compiled-libraries-from-vendors – Thermech Mar 23 '23 at 11:38

Diego Arena · Answer 3 · 2022-06-29T19:08:26.640

11

I was facing the same issue trying to open the Apple Watch Simulator, but I was able to fix it by disabling Rosetta in the xcode.

Mac M1 Xcode 13.4.1 WatchOs 8.5

edited Jun 29 '22 at 19:08

answered Jun 29 '22 at 18:50

Diego Arena

111
3

3

Once I uncheck the rosetta Xcode is not able to make a build. – Qazi Ammar Jul 01 '22 at 07:49

score 5 · Answer 4 · edited May 15 '23 at 17:27

5

Assuming its not solved yet, can you try the following and let us know -

Solution 1

It's an issue with authorization. Try this in the Terminal:

sudo DevToolsSecurity -enable

It may ask you to enter your mac password so kindly do that.

Solution 2

Edit Scheme -> Run -> Debug executable

uncheck this checkbox it will be ok!

edited May 15 '23 at 17:27

Ky -

30,724
51
192
308

answered Aug 24 '22 at 14:36

Bhishak Sanyal

89
1
5

second option worked for me. May I know what `Debug excitable` usually does? – ThinkAndCode Oct 20 '22 at 09:44
1

Uncheck `Debug executable` works for me. – Cuong Nguyen Nov 10 '22 at 06:48
1

The “Debug executable” checkbox specifies whether or not you want to run with the debugger enabled. Once running, you can use Debug > Attach to Process on a process that has been launched with debugging disabled if needed. #ThinkAndCode – Bhishak Sanyal Nov 17 '22 at 14:43
3

This is a bad idea. Your debugger will no longer work. – SmileBot Jun 14 '23 at 20:51

score 1 · Answer 5 · answered Oct 28 '22 at 10:38

1

I also updated Xcode to 14.0 and MacOS to Ventura, I was getting a similar message.

The problem for me was my team member accidentally selected "Wait for the executable to be launched" in our scheme settings. Changing it to "Automatically", worked for me.

Click on your scheme to reveal your schemes and scheme settings.

Click on Edit Scheme, located at the bottom.

Select the Run option on the left and select Automatically on the Launch section.

answered Oct 28 '22 at 10:38

Hem Poudyal

321
6
16

Any way to resolve this error while keeping "Wait for the executable to be launched" ticked? – David Chopin Dec 08 '22 at 16:10
Here I already had the setting adjusted to "Automatically" but still fails with the same error... – Isaac Mar 24 '23 at 11:09

score 0 · Answer 6 · answered Jul 14 '22 at 12:54

0

Set debug under Build Active Architecture Only to Yes

answered Jul 14 '22 at 12:54

Sube Barkhasbadi

1
1

score 0 · Answer 7 · answered Aug 24 '22 at 14:13

0

Sometimes I get this issue and the only way I could get it to work was to first run the app on terminal:

npx react-native run-ios

then reopen xcode and run it again..

answered Aug 24 '22 at 14:13

Yoannes Geissler

791
1
9
18

score 0 · Answer 8 · answered Apr 06 '23 at 08:06

Im using macOS M1 Pro, XCode 14.2

I had a problem running iOS simulator.

Solution that worked for me:

Solution 1 (uncheck Rosetta on Xcode 14.2)

Quit Xcode
Right click on Xcode, press "Get Info"
Make sure that "Open using Rosetta" is not selected(see image)
Delete derived data(don't know if this is required)
Reopen Xcode and run your app

Solution 2

Edit Scheme -> Run -> Debug executable

Check this checkbox

this works for me!

score 0 · Answer 9 · answered Jun 27 '23 at 23:55

0

If you have multiple versions of Xcode installed (including Xcode 14.3) you may need to perform the following song and dance:

https://stackoverflow.com/a/72946533/731285

answered Jun 27 '23 at 23:55

markshiz

2,501
22
28

debugserver is x86_64 binary running in translation, attached failed. Could not attach to pid :

9 Answers9