iOS 15, accelerate module, armv7, Xcode 13

Hi Team,

Attempting to build our app with Xcode 13 / iOS 15, and getting a fail during archive, appearing to come from within the accelerate module.

The two errors are:

/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/lib/swift/Accelerate.swiftmodule/armv7-apple-ios.swiftinterface:591:6: error: enum cases with associated values cannot be marked potentially unavailable with '@available'
  @available(macOS 12.0, iOS 15.0, tvOS 15.0, watchOS 8.0, *)
   ^

in a number of places, and the following one, once:

/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.0.sdk/usr/lib/swift/Accelerate.swiftmodule/armv7-apple-ios.swiftinterface:1:1: error: failed to build module 'Accelerate'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.5 (swiftlang-1300.0.17.216 clang-1300.0.18.1)', while this compiler is 'Apple Swift version 5.5 (swiftlang-1300.0.19.104 clang-1300.0.18.4)'). Please select a toolchain which matches the SDK.
// swift-interface-format-version: 1.0
^

This is Version 13.0 beta (13A5154h), doing a release build archive (dev build/run succeeds if that helps).

Any insights into whats going on would be great?

Cheers.

Up vote post of crafterm Down vote post of crafterm
12k views
Posted by
crafterm
Reply

  • If this error is due to kingfisher then you can try below approach. In order to resolve this issue I tried by changing the deployment target in Kingfisher from 8.0 to 11.0 and now I am able to run in the simulator.

    —
    VatsalRaval
Add a Comment

Apple Recommended

This thread contains several overlapping issues, some of which are resolved in the Xcode 13 RC, and others which are still present in the Xcode 13 RC. As a result of the overlapping issues, there are multiple error messages in this thread.

Generally speaking for the Xcode 13 RC, there are known issues specific to apps using libraries with a deployment target that still supports 32-bit iOS versions (iOS 10 or before), even if the app target only supports 64-bit iOS versions (iOS 11 and newer). To workaround this build error, move the library deployment target up to at least iOS 11.

These known issues and workarounds are also noted in the Xcode 13 Release Notes, under the Swift section.

Posted by
edford
Post not yet marked as solved Up vote reply of edford Down vote reply of edford
Post marked as Apple Recommended
Add a Comment

Replies

This thread contains several overlapping issues, some of which are resolved in the Xcode 13 RC, and others which are still present in the Xcode 13 RC. As a result of the overlapping issues, there are multiple error messages in this thread.

Generally speaking for the Xcode 13 RC, there are known issues specific to apps using libraries with a deployment target that still supports 32-bit iOS versions (iOS 10 or before), even if the app target only supports 64-bit iOS versions (iOS 11 and newer). To workaround this build error, move the library deployment target up to at least iOS 11.

These known issues and workarounds are also noted in the Xcode 13 Release Notes, under the Swift section.

Posted by
edford
Post not yet marked as solved Up vote reply of edford Down vote reply of edford
Post marked as Apple Recommended
Add a Comment

@edford It seems like this is happening again with Xcode 13.2 Beta 2, but not with Beta 1, or Xcode 13.2

The two SPM projects are targeting iOS 11 and up.

Posted by
nomspes
Up vote reply of nomspes Down vote reply of nomspes

  • Please file a bug report with an example project that is reproducing this using Xcode 13.2 beta 2, and post the FB number here. Thank you!

    —
    edford
Add a Comment