SPFx: Can't view Install Errors

[AJIXuMuK]

Category

• Question
• Typo
• Bug
• Additional article idea

Expected or Desired Behavior

If there are any Install errors for SPFx App package they should be visible after clicking on errors count on App Details page:

Observed Behavior

After clicking the link the whole content of the page disappears:

Steps to Reproduce

Create some .sppkg that will throw error while installing.
I got that situation trying to deploy Command Set Extension using Feature Framework with RegistrationId="0x01" and RegistrationType="ContentType" (#871)

[GrahamMcMynn]

@AJIXuMuK - Does this still repro? It looks like chrome, can you confirm what browser you are using? Could you please send a fiddler trace of your request clicking on the "1" to grahamc at Microsoft.com?

[AJIXuMuK]

@mcmynn83 all is good now. and yup - it was Chrome.

[samir-farid]

I'm experiencing the same issue. I tried this in FireFox and Edge, but I get an empty page. Could we reopen this issue?

[GrahamMcMynn]

@samir-farid - could you send a fiddler trace of your call when you click on the 1? That will help us determine why the page isn't loading, we have not been able to investigate it because we haven't been able to repro it.

[tnubel]

I'm hitting this same issue... would be great to know what solved it for @AJIXuMuK .

@mcmynn83 - I traced the request in Chrome developer tools and what's happening is it's throwing an Access Denied error behind the scenes - the error comes from 'https://tnubel.sharepoint.com/_layouts/15/AccessDenied.aspx?Source=https://tnubel.sharepoint.com/_layouts/15/appmonitoringerrordetails.ashx?appInstanceId=d236417e-87cd-4a73-923e-9ac12fb20d2e&entryCode=3&lcid=1033&correlation=61b27b9e-00f6-6000-edc2-51d2602b2f52'

Not sure why I'm getting access denied as I'm the site collection administrator and an admin user.

[AJIXuMuK]

@tnubel I believe it was some portion of luck for me :)

[GrahamMcMynn]

@tnubel - Thanks for the access denied URL. I can actually investigate that!!! The reason why you are receiving this error message is that we do a permissions check for the following permissions:
SPBasePermissions.Open |
SPBasePermissions.ViewPages |
SPBasePermissions.AddAndCustomizePages |
SPBasePermissions.ManageSubwebs |
SPBasePermissions.ManagePermissions |
SPBasePermissions.BrowseDirectories |
SPBasePermissions.ManageWeb

The reason you don't have all of those permissions is that AddAndCustomizePages is removed due to noscript being enabled on that site collection. Internally we will discuss if that permission check is really necessary or not.

Thanks,
Graham

[zolem]

I am having this same problem. Is there a workaround here? I am trying to develop an SPFX webpart that provisions and it is erroring out on the install. I can't see what the errors are because of this bug. Is there a log file somewhere else I can look at?

I have an app catalog on my test site collection so I can't seem to monitor the app either.

[AJIXuMuK]

Same issue again, but this time for Add in, not SPFx solution.

[gpeipman]

Same problem here. There is one install error but no way to see it. When I click on link after install error I see popup for a moment and then page goes blank.

[gpeipman]

There is request made to somewhere and it gets redirected to AccessDenied.aspx.

[good-gravy]

You can avoid the error if you enable custom site scripts. Using the powershell script below you can toggle the setting on/off.

To avoid the error:

Connect-SPOService -Url $tenantUrl
Set-SPOSite -Identity $siteUrl -DenyAddAndCustomizePages $false
Disconnect-SPOService 

To return to default setting:

Connect-SPOService -Url $tenantUrl
Set-SPOSite -Identity $siteUrl -DenyAddAndCustomizePages $true
Disconnect-SPOService 

[andrewconnell]

This still an issue? I'm going back through old issues and making sure they are appropriately closed/labeled/visibility raised if necessary

[gpeipman]

It is still issue. It seems to come down to users who can add apps but who are not tenants admins.

[patmill]

Alternately, can you go to the app / solution list, customize the view, and add the error column?

[msft-github-bot]

This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within next 7 days of this comment. Thank you for your contributions to SharePoint Developer activities.

[AJIXuMuK]

Why do you need author feedback if there is an ongoing conversation happening?
Yes, I experience that issue as well. It's not a priority for now but I'm sure that issues shouldn't be automatically closed.

[andrewconnell]

@AJIXuMuK it's just an automated bot doing that... Needs:AuthorFeedback is waiting for the OP to comment since they are the one who opened the issue. If they don't chime in, the automated closing process kicks in after 7d marking it stale, then closing if no more action happens in 14d... but if the OP does chime in (as you did here), you can see the bot jumped back in and removed that label.

Looking back, it seems I might have labeled it incorrectly/prematurely... my bad...

[AJIXuMuK]

Yup, I saw that it is done by bot. I just think that automation flow might be changed a bit to take into consideration ongoing conversation. But it's off-topic )

[andrewconnell]

Any idea @VesaJuvonen @patmill ? Seems to be incorrect behavior...

[JackWaayerSysdoc]

If you inspect the DOM, you can see that the opacity of the body element has been set to 0. Set that to 1 and you should hopefully see the error window. Don't ask me why it sets the body tag to 0 opacity haha. Hope this helps someone.

[chntn]

I set body element opacity to 1 and it's showing a Request Access form. When we click on the
Request Access button it's shows "Sorry, something went wrong This page has been modified since you opened it. You must open the page again" error.

[Ashish1662]

Hi All,

Is there any update on this issue. Facing exactly the same when trying to add an app that uses 'ContentType' as RegistrationType and RegistrationId as CT id.

[webdevelperify]

Hi All,
I also faced this issue and tried to disable the "no-script" flag at the site collection level (In Office365). After that it started showing me the error page properly.

[sohailrazarizvi]

I am also facing the same issue with one the messages
GET https://waconatm.officeapps.live.com/apc/trans.gif?73269134b9db1478abb08a5f576031e2 net::ERR_FAILED

[san-goyal]

This issue still persist.

Following pnp ps can be used as workaround -

Connect-PnPOnline -Url "https://tenant-admin.sharepoint.com"
$site = Get-PnPTenantSite -Detailed -Url "https://tenant.sharepoint.com/sites/name"
$site.DenyAddAndCustomizePages = 'Disabled'
$site.Update()
$site.Context.ExecuteQuery()
Disconnect-PnPOnline

Go back to App Details -> click on link next to "Install Errors" -> errors appear in a popup

[brianpmccullough]

Can confirm I experience this on 2020-01-26 on a Modern site collection when trying to install an app that is failing. Can also confirm that the DenyAddAndCustomizePages fix mentioned in the thread here does resolve this issue for me (I happen to also be Site Collection Admin in this particular site collection if that matters). I believe you should be able to view app installation errors in Modern site collections, without the need for this "workaround". I suspect much of the behavior is a related to the fact that many of the APP system pages still using the legacy UIs (classic UIs).

[giovanibm]

The issue on the view errors link is still happening. I have a sharepoint dev environment to work and do the permission work around, but i can't do tha same in the client's production tenant.

This need to be fixed.

[Dangerous-Mind]

This is surreal.

Four years later this is still happening...
I've found at least four reports like this one. All closed.

@good-gravy suggestion solved the problem.

[Chris-dot-net]

I am experiencing this issue only on cdn-tenants, but then the issue with blank page instead of showing error is guaranteed to happen.

[mhomol]

Issue still happening today. I am using PowerShell and PnP Core, so here is the proper command for folks who cannot get access to the Install Error

Set-PnPTenantSite -Url "https://tenant.sharepoint.com" -DenyAddAndCustomizePages:$false

[patmill]

Fixing this.

[patmill]

This should be rolled out WW by now, closing.

[ghost]

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