Failed to build module, Apple Swift version 5.1.3 have features that aren't supported by this compiler, 'Apple Swift version 5.3.2

This error indicates that you have a binary named SciChart that was built with a previous version of the Swift compiler (5.1.3). Your current Xcode version has a newer compiler version (5.3.2) which is incompatible with the binary built by 5.1.3.

If SciChart is your code, you should rebuild it with Xcode 12.4. If SciChart is from a third-party vendor, they need to provide you with a version of their library that is built with Library Evolution enabled and contained in an XCFramework. Library Evolution is a build requirement for vendor libraries to ensure compatibility with future compiler versions; without it, this issue will occur with every Xcode update.

Dear edford! Thank you so much for the answer. But I have the same compiler Apple Swift version 5.3.2 on both laptops: Macbook Pro 2016 i5, Macbook Air 2020 M1. And the cause is not in the compile version, because my app builds with out any errors on intel's Macbook with the same compiler version, but on new M1 Macbook I get the error.

The real issue here is that pre-built binary libraries are required to be built with Library Evolution, as I stated. The compiler versions error is an example of a symptom that appears when this requirement is not met. If this library is from a vendor, please follow up with them about getting a version with Library Evolution enabled inside of an XCFramework.

There is a vendor library and today I tried to integrate version with Swift 5.3.2, but get another errors:
1) unable to load standard library for target arm-64-apple-ios9.0
2) Failed to build module ‘SciChart’ from its module interface, it may have been damaged or it may have triggered a bug in Swift compiler when it was produced.
I thought to speed up my work when bought new Macbook M1, but now I can not work on it, because my apps is not build on IOS. Maybe it is possible to downgrade Xcode version, that will build my app with vendor's library Swift version 5.1.3? And for me it is still not clear why Xcode with the same version 12.4 and the same Apple Swift version 5.3.2 on Macbook Pro 2016 i5 can build my app, but on Macbook Air 2020 M1 can not do it, why? What the difference?

When you contacted the vendor about getting an updated library that supports M1 Macs and addresses all of the issues I've outlined, what did they say?

Mr.Edford I have found the decision and it is so simple. I don't know why you did not tell me about this: open Xcode through Rosetta - Right click on Xcode in applications folder -> Get Info -> set Open with Rosetta to true. And thats it. No more pain! Thank you do much for your help)))

Using Xcode through Rosetta is not the right way of resolving this. You really need to talk to the library vendor about a build that supports Apple silicon Macs without needing Rosetta. What did they say when you asked them about this?

Same here. If you use Rosetta, it looks weird when you open xib files and can not constraint. It's not the right way. Just bought a M1 pro for ios development. Too disappointed. Want to sell it immediately. I have to switch rosetta for development and build. Suck!!

I got the new version of vendor's library with Swift compile version 5.3.2, but still can not build it, because have another types errors. And it is still so painy to use Xcode on new Mac M1 with out rosetta. Even if I want to add a new simulator, it is possible do it only with rosetta, with out it get the error:

Could not download and install IOS 12.0 Simulator. Failed to download package from ADC. There are no valid accounts registered with Xcode that have the ability to access this resource. Contact Apple Developer Program Support to resolve account access issues.

And I already connected my apple ID in Xcode, but still can not install a new simulator. It is very strange.

For this new error, please follow-up with Apple Developer Program Support using the Membership and Account option.

Had a similar problem when they removed Rosetta from the info, however found a work around.

In Xcode I cleaned build folder. Then Product -> Destination -> Destination Architectures -> Show Rosetta Destinations

Rebuild and it worked