package:version:create fails with "Unknown Error" when dependent package includes ExperienceBundle

[gsbasso]

Summary

When a package includes an experiences folder (and associated source), attempting to create a new version of any other package that has a dependency on the package that includes experiences source will fail with Unknown Error.

Steps To Reproduce:

Have attached a project that reproduces the issue but can also follow the steps listed below.

1. Create a package that includes an ExperienceBundle site. In the attached project this is the oba package.
2. Create another package that depends on the first package. In the attached project this is the baq package. The content of the second package does not matter, and specifically does not need to include another ExperienceBundle site, although in the attached project the dependent package does include a second site.

Expected result

Creation of new version of dependent package succeeds.

Actual result

Creation of new package version fails with error: Unknown Error
It should go without saying that this error message has absolutely no value.

System Information

Powershell 5

{
"cliVersion": "sfdx-cli/7.162.0",
"architecture": "win32-x64",
"nodeVersion": "node-v16.16.0",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.3.1 (core)",
"@oclif/plugin-not-found 1.2.6 (core)",
"@oclif/plugin-plugins 1.10.11 (core)",
"@oclif/plugin-update 1.5.0 (core)",
"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
"@oclif/plugin-which 1.0.4 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.0 (core)",
"alias 2.1.0 (core)",
"apex 1.1.0 (core)",
"auth 2.2.3 (core)",
"community 2.0.0 (core)",
"config 1.4.14 (core)",
"custom-metadata 2.0.0 (core)",
"data 2.1.1 (core)",
"generator 2.0.2 (core)",
"info 2.0.1 (core)",
"limits 2.0.1 (core)",
"org 2.0.7 (core)",
"salesforce-alm 54.6.4 (core)",
"schema 2.1.1 (core)",
"sfdx-cli 7.162.0 (core)",
"signups 1.2.0 (core)",
"source 2.0.11 (core)",
"telemetry 2.0.0 (core)",
"templates 55.0.0 (core)",
"trust 2.0.1 (core)",
"user 2.1.0 (core)"
],
"osVersion": "Windows_NT 10.0.19042"
}

Additional information

UnknownError.zip

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[git2gus]

This issue has been linked to a new work item: W-11564806

[github-actions]

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.

[shetzel]

Per the metadata coverage report, ExperienceBundle is not supported by 1GP or 2GP, but has limited unlocked packaging support. https://developer.salesforce.com/docs/metadata-coverage/59

@gsbasso - Can you confirm that you are creating an unlocked package (without a namespace) with the ExperienceBundle?

[gsbasso]

Per the metadata coverage report, ExperienceBundle is not supported by 1GP or 2GP, but has limited unlocked packaging support. https://developer.salesforce.com/docs/metadata-coverage/59

@gsbasso - Can you confirm that you are creating an unlocked package (without a namespace) with the ExperienceBundle?

Hi @shetzel ,

Yes, this would have been attempted on unlocked packages without a namespace.
At present all our ExperienceBundle source (we have 3 sites now) is not part of any package (unlocked or otherwise). We just deploy explicitly as needed.

Thanks.