New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Package Not Valid #6

bergersj opened this Issue May 23, 2018 · 7 comments


None yet
6 participants

bergersj commented May 23, 2018


  • Question
  • Bug
  • Enhancement

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.


This comment has been minimized.

sharepointalex commented May 23, 2018

Seeing the same thing here :-(


This comment has been minimized.

garrytrinder commented May 24, 2018

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


This comment has been minimized.

tchagan commented May 24, 2018

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


This comment has been minimized.


bcameron1231 commented May 24, 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.


This comment has been minimized.

garrytrinder commented May 24, 2018

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

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)



This comment has been minimized.

garrytrinder commented May 24, 2018

@bcameron1231 thanks for the help 👍


This comment has been minimized.

asumner commented May 24, 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment