You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently Apple are now requiring separate framwork binaries for iOS Release (ARM) and iOS Simulator (x86).
The KST framework binary is a "fat" binary that contains both which is no longer supported/allowed.
This change was introduced by Apple in Xcode 12.
See the stackoverflow questions/answers here and here for more information on this.
From one of the answers on stackoveflow:
I'm afraid that this is actually the correct error and the framework shouldn't contain iOS and iOS Simulator code at the same time. Apple tries to force us to use XCFrameworks for this purpose. They started it in XCode 11 and just tightened up the restrictions.
The only correct way to resolve this is to rebuild the framework as an XCFramework. Which is easy to do:
The text was updated successfully, but these errors were encountered:
I reached out to you privately, @Seoras , but we are taking a peek at this now, along with several critical updates for both iOS and Android. Feel free to update and submit a Pull Request for the benefit of everyone. Thanks!
Apparently Apple are now requiring separate framwork binaries for iOS Release (ARM) and iOS Simulator (x86).
The KST framework binary is a "fat" binary that contains both which is no longer supported/allowed.
This change was introduced by Apple in Xcode 12.
See the stackoverflow questions/answers here and here for more information on this.
From one of the answers on stackoveflow:
The text was updated successfully, but these errors were encountered: