Question 68050 in IOS Swift Question posted in
The official documentation can be found here.

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

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.

Xcode simulator Error

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

Tags:

8

Answers


  1. 0

    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

    Login or Signup to reply.
  2. 0

    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.

    change this setting only for iOS Simulator

    Login or Signup to reply.
  3. 0

    Set debug under Build Active Architecture Only to Yes

    Login or Signup to reply.
  4. 0

    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

    img1

    Login or Signup to reply.
  5. 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..

    Login or Signup to reply.
  6. 0

    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 excitable

    uncheck this checkbox it will be ok!

    Login or Signup to reply.
  7. 0

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

    main_issue

    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.

    demo_scheme

    Click on Edit Scheme, located at the bottom.

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

    run_scheme

    Login or Signup to reply.
  8. 0

    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!

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search