Xcode 27 beta: "Missing package product" for a Swift Package in a registry

Question

Created 2w

Replies 5

Boosts 2

Participants 3

I have a project that builds fine in macOS 26 with Xcode 26. On macOS 27 b4 and Xcode beta, the same project can't build because of a framework that should be pulled from a Swift Package from a package-registry (named Registry, for example below), hosted on JFrog. I have the registry set up and have the token in keychain. The resolution of the packages works. But when I build, I get error like this:

error: Missing package product 'Registry.Package_Package.Package' (in target 'Target' from project 'Project') . The real package should just be 'Registry.Package'.

Any help with that? Is it a bug?

Answer 1

DTS Engineer OP

Apple

2w

Thanks for the post.

The title says Xcode 27 but the description says Xcode 26 with macOS 27?

Xcode 26 is incorrectly concatenating the scope, package name, and product name when generating the internal build graph nodes, resulting in a target it can't find on macOS 27 beta 4?

Or is Xcode 27 beta 4 and that’s a regression from Xcode 26 to a new Xcode 27 beta? If that’s the case it is highly recommended to file a bug with. Include the exact error message and the mangled name (Registry.Package_Package.Package), as it clearly points the Xcode/SPM team to a string-parsing or serialization bug in the registry integration for the new build system.

Once you open the bug report, please post the FB number here for my reference.

If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why?

Albert  WWDR

Answer 2

jnitro OP

2w

Filed as FB24035409.

The post description said that Xcode 26 and macOS 26 work well but macOS 27 and Xcode beta (so Xcode 27 beta) don't work.

So the problem is only on the 27 train (macOS and Xcode), both beta 4 currently.

Answer 3

DTS Engineer OP

Apple

2w

@jnitro Thanks for providing the bug number.

You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label "Resolution." We're unable to share any updates on specific reports on the forums.

For more details on when you'll see updates to your report, please see What to expect after submission.

Albert  WWDR

Answer 4

choli@ub OP

1w

Hey, same issue here, our team wants to get ready for Xcode 27, unfortunately, this is blocking us and we cannot build. Also, is there any way we can see the progress of the bug mentioned above?

Answer 5

DTS Engineer OP

Apple

1w

@choli@ub Thanks for the post.

Please file a bug as my post above and post the number so I can track it.

Albert  WWDR