[SPFx 1.22.1] Allow debug scripts pop up appears every time the page refreshes after making a change.

[kbeverforden]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

Describe the bug / error

If you create a brand new 1.22.1 project (possibly 1.22.0, as well) and edit the default web part and click save it will automatically refresh the page but show this pop up again. If you click "Load debug scripts" it will refresh the page with your changes applied. I can also replicate this on an existing project that I upgraded to 1.22.1.

Steps to reproduce

See message above

Expected behavior

This pop up used to only appear once but now it's appearing on every save.

[Ashlesha-MSFT]

Hello @kbeverforden,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
If you don’t receive a reply within two working days, please use this escalation form to escalate.

[Tanddant]

@kbeverforden - Could you share some more info about your configuration? - I'm not seeing this 🤔 AFAIK it's not directly related to SPFx, it's just on the SharePoint side of things, so would be interesting if this is a browser issue, are you blocking cookies, or something? - different browser, inPrivate, ect. is this something you're seeing everywhere?

[Ashlesha-MSFT]

@kbeverforden,
We were able to reproduce this issue in our tenant using SPFx 1.22.1. The “Allow debug scripts” prompt now appears on every page refresh after saving changes (Even if you won't update the files just refresh "Load debug scripts" appears), whereas previously it only appeared once per session.

We have logged this behavior as a bug, and our engineering team is actively investigating the root cause.
Thanks for reporting this and for your patience.