Claus Jørgensen
Claus Jørgensen
@BarredEwe it works 🚀
Even though you'll be doing binary releases, can we assume you'll still be including the [App Privacy Manifest](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files) ?
FYI, this was caused by a bug in Xcode that was fixed in Xcode 15.1 (rdar://13194758) However, this thread is very concerning as it was always a _warning_ in xcodebuild....
You can already use `path` instead of `url` to use local Swift Packages
Why does this default even exist? It causes Xcode to ignore `CODE_SIGN_IDENTITY` from xcconfig files...
Based on the output, it _should_ be possible to capture it: ``` ◇ Test run started. ↳ Testing Library Version: 94 (arm64-apple-ios13.0-simulator) ◇ Suite DemoAppTests started. ◇ Test "true should...
I can confirm we're seeing the same: without xcbeautify: ``` Testing started Test Suite 'Selected tests' started at 2024-09-23 11:26:17.705. Test Suite 'MyUnitTests.xctest' started at 2024-09-23 11:26:17.706. Test Suite 'MyUnitTests.xctest'...
We're also seeing issues in Xcode 16.3 with the `12.0.0` release (consumed via. Swift Package Manager) Downgrading to `11.6.0` fixed the issue for us.
Looks like `xcassets` folders are no longer included in the build targets, thus breaking pretty badly Edit: And maybe it's less obvious, but when `ASSETCATALOG_COMPILER_GENERATE_SWIFT_ASSET_SYMBOL_EXTENSIONS` is enabled (or `"generate-swift-asset-symbol-extensions" :...