Upon further experimentation I've discovered that you must set fileSize to 0 to make the BAURLDownload function as expected. Setting it to -1, or slightly different filesize will yield a download failure. So setting both fileSize to 0 and essential to false is required to download assets that you don't have a proper filesize for.

Using swift enums in C++ isn't an issue, and it indeed does that weird'ish naming for the cases. What bothers me is that the Swift functions that I define that take a C++ enum or enum class just don't get interop at all. If the function is a global function, I get the // Unavailable in C++: Swift global function 'swiftFunctionWithCppEnum(_:)'. comment in the generate header. What's worse is that if the function is member for a Swift class, it just gets ommitted entirely without any indication that it is not compatible. It just doesn't show up at all in the generate Swift header. Upon further reading the C++ interop documentation I came across this: If I understand it correctly, this indicates that it actually should work? But it clearly doesn't.

Most likely a related issue, we've been trying to get 'Any iOS Simulator Device' destinations to only build for arm64. We want to do this because the libraries we develop and use in iOS apps rely on AVX instructions on x86_64 platforms. Building such libraries on Mac devices is getting increasingly complicated, as you can't buy Intel based Mac's anywhere, which you need to run x86_64 MacOS binaries that utilize AVX instructions. Rosetta doesn't solve anything in our case due to these AVX instructions that it can't translate to arm64. I've created a support ticket for this: FB16398099

I'm also running into this issue. Xcode is just ignoring the .ssh/config file where the correct key exchange algorithms to use are listed. Unbelievable that this issue is still not fixed :(. For SPM integration I can only recommend configure to use the user configured git for this, which does respect .ssh/config. You can do this by executing this in a terminal: defaults write com.apple.dt.Xcode IDEPackageSupportUseBuiltinSCM YES I haven't found an equivalent preference to tell Xcode to use user configured git client for everything. For when Apple engineers would be reading this, details can be found https://devblogs.microsoft.com/devops/ssh-rsa-deprecation/