Hello I'm just having the exact same problem since a week and it is a nightmare! I tried everything locally (reformat, certificates approval) and nothing changed. Can I know who is your internet provider? The weird thing is if I delete all derived data I'm able to get packages but update almost always fails.. Thanks!

We found a solution and maybe it was a wrong pattern on our side at the beginning. To solve the solution we just added SPM support to our XCFramework by adding on its repository the Package.swift and expose the library that uses the XCFramework binary target like this: let package = Package( 		name: "Module", 		platforms: [ 				.iOS(.v11) 		], 		products: [ 				.library(name: "Module", targets: ["Module"]) 		], 		targets: [ 				.binaryTarget(name: "Module", path: "Module.xcframework") 		] ) Hope this can help :)

Hello @Ams1 we still have the problem and no answer from Apple on feedback assistant. I think you should also open a ticket maybe you'll have more luck? You can reference my opened ticket FB8781532 (at the moment opened with no similar reports).

For more information here is a link to a sample project demonstrating the issue: https://github.com/zocario/swiftpm_archive_binary_target

Thanks @kareman for the reply, I submitted a feedback to Apple with a sample project reproducing the issue. Did you send a bug report on your side too?

Thanks jeff97 for the details, I've filled a bug report (FB8089986) that you can see on open radar (I don't know why but I can't add the link it this post). We'll see - if by chance they answer - if this is a bug / known issue.. did you create a bug report on your side?

Hello, we have the same problem with Bundle.module not accessible when opening our xcodeproj but requires it for our CI and other convenience tools as SwiftLint. Did you guys find any solution / workaround? Still a little bit hard to know if this possibility was planned or not as Bundle.module is generated by SPM not Xcode.