Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Continually prompted to Allow Debug Manifests even after app removed #636

Closed
3 tasks
thechriskent opened this issue Jun 9, 2017 · 4 comments
Closed
3 tasks
Assignees

Comments

@thechriskent
Copy link
Collaborator

Category

  • Question
  • Typo
  • [X ] Bug
  • Additional article idea

Expected or Desired Behavior

After removing an app containing an application customizer and removing the custom action using Remove-PnPCustomAction users should no longer be prompted to Allow Debug Manifests on every modern page.

Observed Behavior

Despite removing the app (and ensuring it is removed from the recycle bins) and removing the Custom Action for the ApplicationCustomizer, users are still being prompted to Allow Debug Manifests.

When choosing to Load debug scripts and checking the console, there are no file not found errors (as would be expected when debugging and gulp serve is not running or when the CDN location doesn't contain any assets).

Steps to Reproduce

Follow the Deploy your extension to SharePoint tutorial and then remove the app and the custom action.

@patmill
Copy link
Contributor

patmill commented Jun 9, 2017

Can you hit the page with ?reset=true and see if it clears things up?

@thechriskent
Copy link
Collaborator Author

@patmill that worked perfectly! Thanks! I only needed to do this on a single page and all other modern pages were corrected as well. What is this magic?

@patmill
Copy link
Contributor

patmill commented Jun 10, 2017 via email

@msft-github-bot
Copy link
Collaborator

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues

@SharePoint SharePoint locked as resolved and limited conversation to collaborators Jan 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants