[BUG] apply provisonning template error header layout compact

[moudhafersalhi]

If you have a question and are not reporting a bug, please go to:

https://github.com/pnp/pnp-powershell/discussions

Notice

Many bugs reported are actually related to the PnP Core Library which is used behind the scenes. Consider carefully where to report an issue:

1. Are you using Apply-PnPProvisioningTemplate or Get-PnPProvisioningTemplate? The issue is most likely related to the Provisioning Engine. The Provisioning engine is not located in the PowerShell repo. Please report the issue here: https://github.com/pnp/PnP-Sites-Core/issues.
2. Is the issue related to the cmdlet itself, its parameters, the syntax, or do you suspect it is the code of the cmdlet that is causing the issue? Then please continue reporting the issue in this repo.
3. If you think that the functionality might be related to the underlying libraries that the cmdlet is calling (We realize that might be difficult to determine), please first double check the code of the cmdlet, which can be found here: https://github.com/pnp/PnP-PowerShell/tree/master/Commands. If related to the cmdlet, continue reporting the issue here, otherwise report the issue at https://github.com/pnp/PnP-Sites-Core/issues

Reporting an Issue or Missing Feature

Issue

Expected behavior

Apply-PnpProvisionning -Path $mypathXML -ClearNavigation I expect that the site would be provisionned with 3 Lists, 5 Navigation nodes, Compact layout for the header

Actual behavior

Error before treating the navigation nodes :

Steps to reproduce behavior

Please include complete code samples in-line or linked from gists Apply-PnPProvisioningTemplate : {"error_description":"Invalid issuer or signature."} ServerErrorTraceCorrelationId: b0058d9f-60ac-2000-9071-bc0a4aa43a2b In Zeile:1 Zeichen:1

• Apply-PnPProvisioningTemplate -Path $config.ProjectTemplateFile -Clea ...

• 
  + CategoryInfo          : WriteError: (:) [Apply-PnPProvisioningTemplate], Exception
  + FullyQualifiedErrorId : EXCEPTION,PnP.PowerShell.Commands.Provisioning.Site.ApplyProvisioningTemplate 

BUT if i delete the line everything works fine.

Which version of the PnP-PowerShell Cmdlets are you using?

• [ ] PnP PowerShell for SharePoint 2013
• [ ] PnP PowerShell for SharePoint 2016
• [ ] PnP PowerShell for SharePoint 2019
• [X ] PnP PowerShell for SharePoint Online

What is the version of the Cmdlet module you are running?

(you can retrieve this by executing Get-Module -Name sharepointpnppowershell* -ListAvailable)

How did you install the PnP-PowerShell Cmdlets?

• [ ] MSI Installed downloaded from GitHub
• [X ] Installed through the PowerShell Gallery with Install-Module
• [ ] Other means

[phillipharding]

I also noticed this behaviour today when trying to apply a <pnp:Header /> or <pnp:Footer />

[moudhafersalhi]

I also noticed this behaviour today when trying to apply a <pnp:Header /> or <pnp:Footer />

are you also using the certificate authentification? there are some strange patterns while using the thumbprint authentification

[phillipharding]

No I was using an SP Addin credentials, also have the same problem with <pnp:ApplicationLifecycleManagement />

Reverted back to v3.23.2007.0 for now

[kadu-jr]

This happened to me too. Eventually, I figured the

and

tags mess with something tenant-related, and I believe they try to use the PnP PowerShell App registration to get tenant permissions. All I did was include the -UseWebLogin(or the LaunchBrowser, I'm not sure) parameter and login trhough their popup screen, which prompted me to give the PnP-PowerShell app the permissions they request. After that, my XML worked fine.