Open simulator xcode 14 by Rosetta to fix scroll

Viewed 393

I just updated to xcode 14, and it seems the simulator can't run with Rosetta to fix scroll lag. Does anyone have a solution that can help me? thank you

This is photo can not open by Rosetta is here

Update: Thanks for all you guys help We have 2 solutions:

  1. (Recommended) James Risner and Manu 's solution: Force open simulator by terminal. First you need force quit simulator, than open it by terminal, keep the terminal when using simulator.
  2. Guillaume S 's solution: add new permissions admin/user for Xcode.app, Simulator.app, Simulator's Content file and Info.plist. Then, follow Guillaume S 's answer
3 Answers

I couldn't solve the problem with Guillaume's method - changing the rights and changing the info.plist of the Simulator.app doesn't change anything.

Here is a method that worked.

Open the terminal and type :

arch -x86_64 /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator

This forces the use of Rosetta.

Applications built with this Property List Key LSRequiresNativeExecution enabled forbid using Rosetta in launch services.

An excerpt from the Apple Documentaion:

... this key prevents the system from using the Rosetta translation process to execute the Intel portion of a universal app on Apple silicon.

A word of caution if using the simulator with Rosetta. There are known issues with the simulator, for example floating point exceptions do not work. So graphical apps may not work correctly.

You can force starting the simulator in Intel mode with Rosetta by use of this command:

arch -x86_64 /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator

sim

Thanks to James' answer above, I found a temporary fix.

Add user/system permissions to the Simulator.app inside Xcode.app, the Contents folder inside Simulator.app and the Info.plist file inside too and modify this Info.plist by adding the following keys:

Architecture priority array with 1 item (Intel (32-bit) by default)

Application requires native environment Boolean with NO as value.

Cleanup everything and rebuild/run and it should fix the scroll lag issue.

Thanks again James Risner for this.

Related