Xcode Question posted in
Whether you're new to Xcode or an experienced developer, our archive has everything you need to know about this integrated development environment (IDE). From basic functionalities to advanced features, our archive covers a wide range of Xcode-related questions and answers. Browse our archive now and find solutions to your Xcode questions, and take your app development skills to the next level

Xcode – Tons of errors due to set arm64 in Excluded Architectures in iOS 14.2 simulators

first of all disclaimer: I’m using Mac Mini with Apple Silicon M1.

I have set arm64 in Excluded Architectures due to the known error in Xcode 12:

The linked framework ‘XXXXXX’ is missing one or more architectures
required by this target: arm64.

Since I changed that the simulator’s console (only in iOS 14) prints tons of errors when started, regarding wrong hash simulator:

[db] LSSchemaConfigureForStore failed with error Error
Domain=NSOSStatusErrorDomain Code=-10817 "(null)"
UserInfo={_LSFunction=_LSSchemaConfigureForStore,
ExpectedSimulatorHash={length = 32, bytes = 0xc853fe2e 5309ad0b
8579253e 7b507c34 … edcdfbe3 457f74e4 }, LSLine=405,
WrongSimulatorHash={length = 32, bytes = 0x762c6c62 f729dcd9 f2ce6d7b
bb9aec8d … d11ece5a 5fc731a0 }}

Anyone else having this problem? Regards.

Tags:

3

Answers


  1. 0

    I had a somewhat different but similar issue when building on M1 MBP with Xcode running with Rosetta. Some of Apple’s APIs fail and together with failing there is this error printed to the console.

    In my opinion this is some kind of a simulator bug and it is present as of Xcode 12.3. Maybe 12.4 solves it, but I did not try.

    Anyway, what solved it for me was to download iOS 13.7 simulator runtime.

    enter image description here

    enter image description here

    And then create a new simulator using this iOS version:

    enter image description here

    If this solution worked for you but you must have iOS 14, you can try other 14.x version. Maybe it’s an issue only with the latest.

    Login or Signup to reply.
  2. 0

    You can get rid of these loggings by adding OS_ACTIVITY_MODE = disable to the Environment Variables’s Arguments.

    Product -> Edit Schema -> Run -> Arguments

    Login or Signup to reply.
  3. 0

    For me, I saw these errors using React Native after ejecting from expo. Specifically, running expo run:ios (more info). I see no such errors after stopping that initial session and running another again, right after, using npm run ios.

    Seems like the normal npm-run command starts a simulator with the correct architecture. However, the final step in the expo run:ios process does not.

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

Back To Top
Search