Sp-starter-kit: App Package Not Valid

Created on 23 May 2018 · 8Comments · Source: pnp/sp-starter-kit

Expected or Desired Behavior

To package the solution and upload the sharepoint package file to my app catalog.

Observed Behavior

Uploaded .sppkg file to app catalog, but Valid App Package column has value of No with Error in App Package also displayed on column value.

Steps to Reproduce

Inside Solution folder, install NPM and gulp, adjust the write-manifest.json to have a cdnBasePath value which is my sharepoint assets folder. run gulp bundle -ship, upload files from deploy folder to sharepoint asset folder. run gulp package-solution -ship. upload .sppkg file to app catalog.

Source

bergersj

Most helpful comment

I've now got this working, it was a tenant issue for me.

The API Management section of the new SharePoint Admin Portal was not showing for me, which is required for the AAD integration in SPFX to work, see https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-aadhttpclient#manage-permission-requests

My tenant was on targeted release for specific users, I changed this to everyone and after 5-10 mins the API Management section appeared. I was then able to successfully upload the package to the App Catalog and deploy. (Admin Portal -> Settings -> Organization Profile)

garrytrinder on 24 May 2018

👍4

All 8 comments

Seeing the same thing here :-(

alexc-MSFT on 23 May 2018

Same, also the same if I upload the sppkg file from the repo :(

garrytrinder on 24 May 2018

Same here, tried both bundling and packaging the source to a sppkg and the sppkg from the repo, both had this error.

tchagan on 24 May 2018

As talked about on the PnP SIG call this morning, it may be because API Management is missing from the admin center in your tenant. @garrytrinder Thanks for the info as well.

bcameron1231 on 24 May 2018

I've now got this working, it was a tenant issue for me.

garrytrinder on 24 May 2018

👍4

@bcameron1231 thanks for the help 👍

garrytrinder on 24 May 2018

@garrytrinder thanks for detailing that, we have wasted a few hours and we changed the release on our test tenancy and package upload worked!

asumner on 24 May 2018

👍1

I had the same issue after install/uninstall the application.
I managed to resolve it by deleting manually the entry for my application in a list which it's hidden at 'Lists/ComponentManifests', so you can access from 'site/yourappcatalogsite/Lists/ComponentManifests