"The package contains the wrong number of relationships for relationship type 'http://schemas.microsoft.com/sharepoint/2012/app/relationships/package-manifest'. Expected: '1'. Actual: '0'."

[PChinari]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

None

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser version
• SPFx version
• Node.js version
• etc

Describe the bug / error

When I try to upload the package in sharepoint manage apps I get the error saying" "The package contains the wrong number of relationships for relationship type 'http://schemas.microsoft.com/sharepoint/2012/app/relationships/package-manifest'. Expected: '1'. Actual: '0'." .

Steps to reproduce

Expected behavior

It should upload the package successfully in sharepoint.

[Ashlesha-MSFT]

Hello @PChinari,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
If you don’t receive a reply within two working days, please use this escalation form to escalate.

[Ashlesha-MSFT]

@PChinari,
From the error message and the package contents, it appears that the file may have been modified outside of the standard SPFx build process. In several cases we’ve seen, the issue occurs when the .sppkg file is manually zipped, or when both a .zip and .sppkg version of the package exist and the wrong one is uploaded. Although an .sppkg is technically a ZIP format, modifying or re-archiving it externally can remove required relationships—such as the package-manifest reference—leading to the “Expected: ‘1’, Actual: ‘0’” error.

Could you please try reproducing this using a clean, unmodified .sppkg generated directly from your SPFx solution (without re-zipping or packaging it manually)? This will help confirm whether the package was altered somewhere in the process.

You may also find this related issue helpful: #7450

Let us know what you find, and we’ll be happy to assist further.