Sp-dev-docs: Debug error message appears on _layouts/15/viewlsts.aspx after debugging

[StfBauer]

Category

• [x] Bug

Describe the bug

The following error message appears all over SharePoint on Site Contents after debugging has started and already ended.

Steps to reproduce

1. Debug SharePoint Framework web part or application customizer with the query string '?loadSPFX=true&debugManifestsFile=https://localhost:4321/temp/manifests.js'
2. Stop debugging and navigate to any site collection using /_layouts/15/viewlsts.aspx?view=14 like the regular link on 'Site Contents'

Expected behavior

• Option 1: Once a debugging session has been finished it may ask only once if you really like to debug still
• Option 2: Don't try to load debugging for _layouts pages.

Intermediate solution

• Option 1: Closing the browser and open it again.
• Option 2: sessionStorage.clear() on the console of the browser

Environment details (development & target environment)

General issue related by passing in the query parameter.

Tested in this case in Firefox.

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[andrewconnell]

I think that's related to this: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/debug-modern-pages#disabling-debug-scripts

Once you start a debug session, it is persisted through the browser session unless you reset it.

[StfBauer]

Thank you @andrewconnell - Confirmed - documented but awkward implementation.

The only question left. Why pages only in the _layouts/15 show this error message but none of the others. Considering this I think it is a bug rather than a wanted behaviour.

Especially look at the "errorLoadingDebugManifestTitle" as well as "debugManifestErrorDebugDismissButtonText" this seems more like an incomplete malicious implementation.

[andrewconnell]

@johnguy0 ... can you address @StfBauer's follow up questions? This is related to the change that was made a while back that you were looking into...

[msft-github-bot]

Closing this issue as "answered". If you encounter a similar issue(s), please open up a new issue. See our wiki for more details: Issue-List: Our approach to closed issues