NoComponentId error when open a migrated page form classic to modern using PnP PowerShell

Reporting an Issue or Missing Feature

• Page Transformation: Page is not looking correct after transformation.

Overview

A sub site migrated to be a new Communication site and It has some Classic Pages (WebPart and Wiki Pages)

Expected or Desired Behavior

Excepted behavior is to have classic pages converted to modern pages. Excepted to see logs on SharePoint or file system by using the parameters (-LogType) (-LogFolder) but no reports generated

Observed Behavior

Observed that migrated pages created in only specific Page library regardless of where the source page is existing despite it should be created in the SitePages Libraries. All converted pages are giving error “NoComponentId” when trying to open any one.

Sorry, something went wrong NoComponentId TECHNICAL DETAILS Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: xxxxx-xxxx-xxxx-xxxx-xxxxxxxx

Observed Errors in power Shell for some pages

ConvertTo-PnPPage : Page is an basic aspx page…can’t currently transform that one, sorry! ConvertTo-PnPPage : Page ‘xxxxx.aspx’ does not exist

PnpPowerShell Script

link to the PowerShell

PnpPowerShell versions:

• PnP.PowerShell 1.3.0

Which operating system/environment are you running PnP PowerShell on?

• Windows

[jansenbe]

Please try tomorrow, the last fix was not yet in the current nightly

[mohammadamer]

Issue resolved with the latest nightly build Awesome! classic pages that are living in different libraries converted to modern in SitePages library. Great! Thanks @jansenbe