Platform/OS version:
iOS 13+ (not relevant for issue)
IDE version:
Xcode 14.2
Devices:
N/A
Any related GitHub issues:
Describe the bug
When upgrading to any version past 2.2.0 and trying to build the project on Xcode 14.2, the following error will occur cannot declare local computed variable in result builder which is emitting from the addition of /SwiftUIBackports/Sources/SwiftUIBackports/iOS/AutoCapitalization/AutoCapitalization.swift with this block of code
var type: SwiftUI.TextInputAutocapitalization {
...
}
Steps to reproduce
Try running any version past 2.2 of SwiftUIBackPorts on Xcode 14.2.
Expected behavior
SwiftUIBackports to build correctly
Screenshots
Additional context
I believe that this block of #if available code just needs to verify the swift version and this shouldn't be a problem anymore.
We're sadly blocked from moving to Xcode 14.3 at our company and a fix in a later version past 2.2 fixed an issue we were having elsewhere.
One of our developers had 14.3 on their computer and was working off that, but when it got to our build machines that are still running 14.2, this is when we saw it was failing.
General Information
Project version: 2.2.0+
Platform/OS version: iOS 13+ (not relevant for issue)
IDE version: Xcode 14.2
Devices: N/A
Any related GitHub issues:
Describe the bug
When upgrading to any version past 2.2.0 and trying to build the project on Xcode 14.2, the following error will occur
cannot declare local computed variable in result builderwhich is emitting from the addition of/SwiftUIBackports/Sources/SwiftUIBackports/iOS/AutoCapitalization/AutoCapitalization.swiftwith this block of codeSteps to reproduce
Try running any version past 2.2 of SwiftUIBackPorts on Xcode 14.2.
Expected behavior
SwiftUIBackports to build correctly
Screenshots
Additional context
I believe that this block of #if available code just needs to verify the swift version and this shouldn't be a problem anymore. We're sadly blocked from moving to Xcode 14.3 at our company and a fix in a later version past 2.2 fixed an issue we were having elsewhere. One of our developers had 14.3 on their computer and was working off that, but when it got to our build machines that are still running 14.2, this is when we saw it was failing.