Developer Tenant cannot use this package?,about pnp/sp-starter-kit

Comments (14)

VesaJuvonen commented on August 23, 2024 3

As noted in the pre-requirements, this does require that the whole tenant is in Targeted release setting due to dependency on preview capabilities around the Microsoft Graph.

Notice also that if you move your tenant to Targeted release mode, it can take up to 24 hours for the setting to fully taken into account. I just tested this with one clean new tenant and got exactly the same exception around "Error in package", but after 18 hours from changing the settings, all works fine. We do understand that the wait time is not optimal, but can't fix that right now.

So - please do wait a while and try to install the sppkg file again on the app catalog. You cannot use deploy.ps1 unless you can successfully deploy the package to the tenant level.

from sp-starter-kit.

VesaJuvonen commented on August 23, 2024 1

We do recommend using the spppkg file in the package folder, as noted in the readme file. You can install that to your app catalog in your tenant and that will then skip the npm install etc. commands in the flow, which would require development setup.

from sp-starter-kit.

jonasbjor commented on August 23, 2024

Same here! (mine is production)
Is it a must to have the tenant set to targeted release / first release for this sppkg to work?

from sp-starter-kit.

bcameron1231 commented on August 23, 2024

@cheynen Can you confirm that your tenant is "targeted release for everyone" and that API Management is available for you in the new SharePoint Admin Center?

@jonasbjor Yes your tenant must be set to targeted release for everyone.

from sp-starter-kit.

cheynen commented on August 23, 2024

Yes, my tenant is targeted release.
As it turns out, I deleted the app, waited an hour and uploaded it without error. Unfortunately not one single bit of the deploy.ps1 would work thereafter. This is discouraging.
I am getting a lot of NuGet package errors that I don't seem able to correct in Code.

from sp-starter-kit.

cheynen commented on August 23, 2024

Thank you so much. Waiting was the answer for the app package. No errors today. Now however I have npm errors – even though I ran npm update… What does this mean? Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: Vesa Juvonen <[email protected]> Sent: Thursday, June 14, 2018 11:16 PM To: SharePoint/sp-starter-kit <[email protected]> Cc: cheynen <[email protected]>; Mention <[email protected]> Subject: Re: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) As noted in the pre-requirements, this does require that the whole tenant is in Targeted release setting due to dependency on preview capabilities around the Microsoft Graph. Notice also that if you move your tenant to Targeted release mode, it can take up to 24 hours for the setting to fully taken into account. I just tested this with one clean new tenant and got exactly the same exception around "Error in package", but after 18 hours from changing the settings, all works fine. We do understand that the wait time is not optimal, but can't fix that right now. So - please do wait a while and try to install the sppkg file again on the app catalog. You cannot use deploy.ps1 unless you can successfully deploy the package to the tenant level. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AMZ7EnhKB5-Ec14v5YGKINOGOOvscRViks5t81EPgaJpZM4UoYKK> . <https://github.com/notifications/beacon/AMZ7EsAzx77-tND09vXcNVUvDPKl3E6mks5t81EPgaJpZM4UoYKK.gif>

from sp-starter-kit.

cheynen commented on August 23, 2024

And then, when I run it again, it has been sitting here for half an hour, just like this… Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: [email protected] <[email protected]> Sent: Friday, June 15, 2018 6:13 AM To: 'SharePoint/sp-starter-kit' <[email protected]> Subject: RE: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) Thank you so much. Waiting was the answer for the app package. No errors today. Now however I have npm errors – even though I ran npm update… What does this mean? Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: Vesa Juvonen <[email protected] <mailto:[email protected]> > Sent: Thursday, June 14, 2018 11:16 PM To: SharePoint/sp-starter-kit <[email protected] <mailto:[email protected]> > Cc: cheynen <[email protected] <mailto:[email protected]> >; Mention <[email protected] <mailto:[email protected]> > Subject: Re: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) As noted in the pre-requirements, this does require that the whole tenant is in Targeted release setting due to dependency on preview capabilities around the Microsoft Graph. Notice also that if you move your tenant to Targeted release mode, it can take up to 24 hours for the setting to fully taken into account. I just tested this with one clean new tenant and got exactly the same exception around "Error in package", but after 18 hours from changing the settings, all works fine. We do understand that the wait time is not optimal, but can't fix that right now. So - please do wait a while and try to install the sppkg file again on the app catalog. You cannot use deploy.ps1 unless you can successfully deploy the package to the tenant level. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AMZ7EnhKB5-Ec14v5YGKINOGOOvscRViks5t81EPgaJpZM4UoYKK> . <https://github.com/notifications/beacon/AMZ7EsAzx77-tND09vXcNVUvDPKl3E6mks5t81EPgaJpZM4UoYKK.gif>

from sp-starter-kit.

cheynen commented on August 23, 2024

End result – incomplete installation… Help? From: [email protected] <[email protected]> Sent: Friday, June 15, 2018 7:05 AM To: 'SharePoint/sp-starter-kit' <[email protected]> Subject: RE: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) And then, when I run it again, it has been sitting here for half an hour, just like this… Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]> > Sent: Friday, June 15, 2018 6:13 AM To: 'SharePoint/sp-starter-kit' <[email protected]> Subject: RE: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) Thank you so much. Waiting was the answer for the app package. No errors today. Now however I have npm errors – even though I ran npm update… What does this mean? Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: Vesa Juvonen <[email protected] <mailto:[email protected]> > Sent: Thursday, June 14, 2018 11:16 PM To: SharePoint/sp-starter-kit <[email protected] <mailto:[email protected]> > Cc: cheynen <[email protected] <mailto:[email protected]> >; Mention <[email protected] <mailto:[email protected]> > Subject: Re: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) As noted in the pre-requirements, this does require that the whole tenant is in Targeted release setting due to dependency on preview capabilities around the Microsoft Graph. Notice also that if you move your tenant to Targeted release mode, it can take up to 24 hours for the setting to fully taken into account. I just tested this with one clean new tenant and got exactly the same exception around "Error in package", but after 18 hours from changing the settings, all works fine. We do understand that the wait time is not optimal, but can't fix that right now. So - please do wait a while and try to install the sppkg file again on the app catalog. You cannot use deploy.ps1 unless you can successfully deploy the package to the tenant level. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AMZ7EnhKB5-Ec14v5YGKINOGOOvscRViks5t81EPgaJpZM4UoYKK> . <https://github.com/notifications/beacon/AMZ7EsAzx77-tND09vXcNVUvDPKl3E6mks5t81EPgaJpZM4UoYKK.gif>

from sp-starter-kit.

cheynen commented on August 23, 2024

PS D:\git\sp-starter-kit\provisioning> .\deploy.ps1 -TenantUrl https://scleraca.sharepoint.com -SitePrefix MyDemo Reading Site Hierarchy from ./hierarchy.json Creating https://scleraca.sharepoint.com/sites/MyDemoportal Creating MyDemohr Creating MyDemomarketing

***@***.*** install D:\git\sp-starter-kit\solution\node_modules\deasync node ./build.js

`win32-x64-node-8` exists; testing Binary is fine; exiting

***@***.*** install D:\git\sp-starter-kit\solution\node_modules\node-sass node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.7.2/win32-x64-57_binding.node Download complete Binary saved to D:\git\sp-starter-kit\solution\node_modules\node-sass\vendor\win32-x64-57\binding.node Caching binary to C:\Users\CaroleeHeynen\AppData\Roaming\npm-cache\node-sass\4.7.2\win32-x64-57_binding.node

***@***.*** install D:\git\sp-starter-kit\solution\node_modules\phantomjs-prebuilt node install.js

PhantomJS not found on PATH Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-windows.zip Saving to C:\Temp\phantomjs\phantomjs-2.1.1-windows.zip Receiving... Received 17767K total. Extracting zip contents Removing D:\git\sp-starter-kit\solution\node_modules\phantomjs-prebuilt\lib\phantom Copying extracted folder C:\Temp\phantomjs\phantomjs-2.1.1-windows.zip-extract-1529076395212\phantomjs-2.1.1-windows -> D:\git\sp-starter-kit\solution\node_modules\phanto mjs-prebuilt\lib\phantom Writing location.js file Done. Phantomjs binary available at D:\git\sp-starter-kit\solution\node_modules\phantomjs-prebuilt\lib\phantom\bin\phantomjs.exe

@***@***.*** install ***@***.***\sp-loader node npm-postinstall.js ***@***.*** postinstall D:\git\sp-starter-kit\solution\node_modules\spawn-sync node postinstall ***@***.*** postinstall D:\git\sp-starter-kit\solution\node_modules\uglifyjs-webpack-plugin node lib/post_install.js ***@***.*** postinstall D:\git\sp-starter-kit\solution\node_modules\node-sass node scripts/build.js

Binary found at D:\GIT\sp-starter-kit\solution\node_modules\node-sass\vendor\win32-x64-57\binding.node Testing binary Binary is fine

@***@***.*** postinstall ***@***.***\spfx-controls-react node postinstall/install.js

INFO: Adding the required localized resource configuration to the config.json file. npm : WARNING: it seems something is wrong with the config.json file or the "ControlStrings" reference was already set. At D:\git\sp-starter-kit\provisioning\deploy.ps1:76 char:5 + npm install + ~~~~~~~~~~~ + CategoryInfo : NotSpecified: (WARNING: it see...as already set.:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}) added 1817 packages from 1672 contributors and audited 264619 packages in 4416.716s found 10 vulnerabilities (1 low, 5 moderate, 4 high) run `npm audit fix` to fix them, or `npm audit` for details Building solution Bundling solution Packaging solution Provisioning solution WARNING: An OAuth permission with the resource Microsoft Graph and scope Sites.Read.All already exists. Parameter name: permissionRequest WARNING: An OAuth permission with the resource Microsoft Graph and scope Contacts.Read already exists. Parameter name: permissionRequest WARNING: An OAuth permission with the resource Microsoft Graph and scope User.Read.All already exists. Parameter name: permissionRequest WARNING: An OAuth permission with the resource Microsoft Graph and scope Mail.Read already exists. Parameter name: permissionRequest WARNING: An OAuth permission with the resource Microsoft Graph and scope Calendars.Read already exists. Parameter name: permissionRequest Applying template to portal WARNING: You specified to remove existing content types for the list with url '/sites/MyDemoportal/Lists/Alerts'. We found a list with the same url in the site. In case o f a list update we cannot remove existing content types as they can be in use by existing list items and/or documents. Id Title Site Scripts

…

-- ----- ------------ aae18efc-49e1-434c-9566-db7cad53438d Contoso Team Site {cb3f84ac-8a5c-436f-b4ba-bfc9c839e128} 751e0fe8-5000-4466-a852-7a89e9543dc0 Contoso Communication Site {481c053a-0e5f-4de5-b763-8e2737128a28} Updating navigation and applying collab templates Connect-PnPOnline : The remote server returned an error: (404) Not Found. At D:\git\sp-starter-kit\provisioning\deploy.ps1:139 char:28 + ... onnection = Connect-PnPOnline -Url "$TenantUrl/sites/$SitePrefix$($ch ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Connect-PnPOnline], WebException + FullyQualifiedErrorId : System.Net.WebException,SharePointPnP.PowerShell.Commands.Base.ConnectOnline WARNING: The source site from which the template was generated had a base template ID value of GROUP#0, while the current target site has a base template ID value of SITE PAGEPUBLISHING#0. This could cause potential issues while applying the template. Connect-PnPOnline : The sign-in name or password does not match one in the Microsoft account system. At D:\git\sp-starter-kit\provisioning\deploy.ps1:139 char:28 + ... onnection = Connect-PnPOnline -Url "$TenantUrl/sites/$SitePrefix$($ch ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Connect-PnPOnline], IdcrlException + FullyQualifiedErrorId : Microsoft.SharePoint.Client.IdcrlException,SharePointPnP.PowerShell.Commands.Base.ConnectOnline WARNING: The source site from which the template was generated had a base template ID value of GROUP#0, while the current target site has a base template ID value of SITE PAGEPUBLISHING#0. This could cause potential issues while applying the template. Done. Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: [email protected] <[email protected]> Sent: Friday, June 15, 2018 7:42 AM To: 'SharePoint/sp-starter-kit' <[email protected]> Subject: RE: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) End result – incomplete installation… Help? From: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]> > Sent: Friday, June 15, 2018 7:05 AM To: 'SharePoint/sp-starter-kit' <[email protected]> Subject: RE: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) And then, when I run it again, it has been sitting here for half an hour, just like this… Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: [email protected] <mailto:[email protected]> <[email protected] <mailto:[email protected]> > Sent: Friday, June 15, 2018 6:13 AM To: 'SharePoint/sp-starter-kit' <[email protected]> Subject: RE: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) Thank you so much. Waiting was the answer for the app package. No errors today. Now however I have npm errors – even though I ran npm update… What does this mean? Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: Vesa Juvonen <[email protected] <mailto:[email protected]> > Sent: Thursday, June 14, 2018 11:16 PM To: SharePoint/sp-starter-kit <[email protected] <mailto:[email protected]> > Cc: cheynen <[email protected] <mailto:[email protected]> >; Mention <[email protected] <mailto:[email protected]> > Subject: Re: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) As noted in the pre-requirements, this does require that the whole tenant is in Targeted release setting due to dependency on preview capabilities around the Microsoft Graph. Notice also that if you move your tenant to Targeted release mode, it can take up to 24 hours for the setting to fully taken into account. I just tested this with one clean new tenant and got exactly the same exception around "Error in package", but after 18 hours from changing the settings, all works fine. We do understand that the wait time is not optimal, but can't fix that right now. So - please do wait a while and try to install the sppkg file again on the app catalog. You cannot use deploy.ps1 unless you can successfully deploy the package to the tenant level. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AMZ7EnhKB5-Ec14v5YGKINOGOOvscRViks5t81EPgaJpZM4UoYKK> . <https://github.com/notifications/beacon/AMZ7EsAzx77-tND09vXcNVUvDPKl3E6mks5t81EPgaJpZM4UoYKK.gif>

from sp-starter-kit.

cheynen commented on August 23, 2024

Thank you, Installing the sppkg is simple enough, and in fact, I do that before ruining the .ps1. Is there a link to how to make the example sites from that though? Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: Vesa Juvonen <[email protected]> Sent: Sunday, June 17, 2018 11:51 PM To: SharePoint/sp-starter-kit <[email protected]> Cc: cheynen <[email protected]>; Mention <[email protected]> Subject: Re: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) We do recommend using the spppkg file in the package folder, as noted in the readme file. You can install that to your app catalog in your tenant and that will then skip the npm install etc. commands in the flow, which would require development setup. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AMZ7EtYtW8wQB-Qwln-lNqoOj04gM-M5ks5t903YgaJpZM4UoYKK> . <https://github.com/notifications/beacon/AMZ7Env8teCsBFcwTgptZqYKPOpuMH7Xks5t903YgaJpZM4UoYKK.gif>

from sp-starter-kit.

cheynen commented on August 23, 2024

Thanks Beau, I was able to install the starter kit after coming back to the project a couple days later. Evidently, because my dev tenant was new, I needed to wait a while? In any case the script worked. EXCEPT FOR the departmental sites. They did not get provisioned with any of the custom content and do not inherit branding from the hub. Have you heard of this issue? Kind Regards, Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: Beau Cameron <[email protected]> Sent: Thursday, June 14, 2018 2:05 PM To: SharePoint/sp-starter-kit <[email protected]> Cc: cheynen <[email protected]>; Mention <[email protected]> Subject: Re: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) @cheynen <https://github.com/cheynen> Can you confirm that your tenant is "targeted release for everyone" and that API Management is available for you in the new SharePoint Admin Center? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AMZ7EuwvYxRL9uyfrhrfcf87HXRY40vPks5t8s_ugaJpZM4UoYKK> . <https://github.com/notifications/beacon/AMZ7Ei0UToA0EWAXk2Xgg_r966kPrif5ks5t8s_ugaJpZM4UoYKK.gif>

from sp-starter-kit.

eoverfield commented on August 23, 2024

@cheynen Expected behavior for a new dev tenant. With a new dev tenant, you will need to enable targeted release, which will take about 24 hours to fully propagate.

Regarding the issue with the department sites, I suggest you start a new issue and provide more details if possible.

from sp-starter-kit.

cheynen commented on August 23, 2024

Thank you, will do. Carolee A. Heynen Cell: +1 616.516.6739 <mailto:[email protected]> [email protected] <http://www.facebook.com/caroleeheynen> . <http://www.linkedin.com/in/caroleeheynen> . From: Eric Overfield <[email protected]> Sent: Monday, June 25, 2018 9:05 AM To: SharePoint/sp-starter-kit <[email protected]> Cc: cheynen <[email protected]>; Mention <[email protected]> Subject: Re: [SharePoint/sp-starter-kit] Developer Tenant cannot use this package? (#27) @cheynen <https://github.com/cheynen> Expected behavior for a new dev tenant. With a new dev tenant, you will need to enable targeted release, which will take about 24 hours to fully propagate. Regarding the issue with the department sites, I suggest you start a new issue and provide more details if possible. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AMZ7Em5_PqPjeGMrmOSwEKlFTQxcAbXLks5uAQovgaJpZM4UoYKK> . <https://github.com/notifications/beacon/AMZ7EuBHQeXbM2t-GhYUqozhXU8SbWBiks5uAQovgaJpZM4UoYKK.gif>

from sp-starter-kit.

eoverfield commented on August 23, 2024

Closing issue, solved via described expected behavior with a developer tenant that has been configured to requirements and the recommended time as transpired before installation of starter kit.

from sp-starter-kit.

Developer Tenant cannot use this package? about sp-starter-kit HOT 14 CLOSED

Comments (14)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent