SpFx Helloworld webpart does not show up under modern Page toolbox

Moreshwar83 commented 7 years ago

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Expected or Desired Behavior

After adding SpFx webpart to site contents, the webpart should be available in toolbox for modern UI page in SharePoint online.

Observed Behavior

Cannot find Simple hello world webpart in modern UI page toolbox, although it is available under site contents.

Steps to Reproduce

Followed all steps as explained in article https://dev.office.com/sharepoint/docs/spfx/web-parts/get-started/serve-your-web-part-in-a-sharepoint-page However, stuck at last step, i.e. cannot add webpart to page.

patmill commented 7 years ago

Silly question, but can you scroll down in the modern page toolbox and see it lower?

Moreshwar83 commented 7 years ago

Offcourse I have tried it. The webpart cannot be seen at all. I was not able to put that together in screenshot. Below is full screen grab, if that helps

patmill commented 7 years ago

OK, just double checking. Did you get your part working on your local workbench and / or hosted workbench before uploading it to the app catalog?

If you type this into your browser (https://yourtenant.sharepoint.com/sites/yoursite/_api/web/GetClientSideWebParts) can you find your webpart listed?

If you go to your app catalog site, can you go to https://yourtenant.sharepoint.com/sites/yourappcatalog/Lists/ComponentManifests/AllItems.aspx and see your webpart in the list of available components?

Moreshwar83 commented 7 years ago

Hello Patmill, Please find my answers below:

Did you get your part working on your local workbench and / or hosted workbench before uploading it to the app catalog? Ans: Yes it is working on local workbench. If you type this into your browser (https://yourtenant.sharepoint.com/sites/yoursite/_api/web/GetClientSideWebParts) can you find your webpart listed? Ans: No, I cannot find it.

If you go to your app catalog site, can you go to https://yourtenant.sharepoint.com/sites/yourappcatalog/Lists/ComponentManifests/AllItems.aspx and see your webpart in the list of available components? Ans: No, I do not see it here as well

Moreshwar83 commented 7 years ago

It started working now. Resolution:

Go to ~appcatalog/AppCatalog/Forms/AllItems.aspx
Edit properties for the web part, I added short description & Description and saved. Webpart started appearing under ~appcatalog/Lists/ComponentManifests/AllItems.aspx
Removed and re-added webpart from dev site. It started showing up in page toolbox. I was able to add and see it on page as well.

Thank you for your guidance Patmill.

patmill commented 7 years ago

Glad you got it sorted out.

Dilli commented 7 years ago

@Moreshwar83 Thanks for pointing out to fill 'Description' and 'Short Description'. If there is no 'Description' and 'Short description' 'Client Side WebPart' don't show up in the modern page toolbox.

@patmill There seem to be bug in pulling 'Client Side WebPart' to show up in the modern page toolbox when 'Description' and 'Short Description' not filled in against the app in app catalog.

waldekmastykarz commented 7 years ago

If you check the schema of the web part manifest in ./node_modules/@microsoft/sp-module-interfaces/lib/manifestSchemas/IClientSideWebPartManifest.d.ts you can see that the description property is required. When you try to build the project without it, or with an empty value you will get a build error. Could you share your web part manifest so that we can see your configuration?

Dilli commented 7 years ago

@waldekmastykarz Firstly, the manifest path provided above does not seems correct in local. But managed to find the file in the following path '.\SPFx\helloworld-webpart\node_modules\@microsoft\sp-module-interfaces\lib\manifestSchemas'. Please comment otherwise.

IClientSideWebPartManifest.d.ts.txt

I do see, the 'description' is not optional in the file, but could be bug in mappings. There is no mention about 'short description' field though in the very same file.

P.S I have added '.txt' extension to the file as the file type is not supported by git hub comments.

waldekmastykarz commented 7 years ago

@Dilli sorry, I shortened the path too much in my comment, you got it right. Where did you get the reference to 'short description' from? It doesn't seem to be mentioned anywhere.

Dilli commented 7 years ago

@waldekmastykarz , Myself picked the 'short description' from app catalog. Please ignore 'short description'.

paigeflourin commented 6 years ago

Hi @patmill @Moreshwar83

what would i do if i cant see it in the /_api/web/GetClientSideWebParts but it is present in the sites/appcatalog/Lists/ComponentManifests/AllItems.aspx. i still cant see it when i try to add my webpart

P.S: my webpart has description as well

smithderekm commented 6 years ago

I'm experiencing the same behavior as @paigeflourin - worked last week (11/20), but now, the updated web part no longer appears in the web part gallery.

I did add a provisioning feature to my solution in addition to the web part - and I'm wondering if that is what is causing the web part to no longer appear. I tried a new build without the feature block in the package-solution.json file, but that does not seem to fix it.

My solution does not appear in the /_api/web/GetClientSideWebParts output, but it is shown in ~appcatalog/Lists/ComponentManifests/AllItems.aspx and has no error messages from deployment.

Any guidance is appreciated.

vickeybird commented 6 years ago

I'm facing the same issue as @paigeflourin . Moreover when I try to unsinstall the app containing the webpart, it goes to recycle bin and shows zero KBs as size. I'm unable to delete it from solution from recycle bin and consequently unable to try updating the web part as well. Anyone else facing this issue?

smithderekm commented 6 years ago

In my case, I found that when I added my own feature definition in the package-solutions file for provisioning, it was essentially overwriting the feature for the web part. The tooling generates the feature behind the scenes but never reveals it (annoying!) so my hand-entered feature caused the conflict.

The fix was to ensure that the package-solution file has 2 features with different IDs - one for the web part, and one for the provisioning. Once I did that, then the installation of the app put everything in the right place and the web part re-appeared in the gallery to place on a page.

Here's a sample package-solution.json to illustrate. You'll need to generate new guids for your solution/features.

{
  "$schema": "https://dev.office.com/json-schemas/spfx-build/package-solution.schema.json",
  "solution": {
    "name": "Hello World",
    "id": "300ecbc4-f139-459e-bb2d-bc3b1445a12c",
    "version": "1.0.0.0",
    "features": [
      {
        "id": "3be4d3fd-963b-4a1b-9607-cddb02c4cf16",
        "title": "Hello World Web part feature",
        "description": "A feature which activates the Client-Side WebPart named Hello World",
        "version": "1.0.0.0"
      },
      {
        "title": "Hello World Provisioning",
        "description": "Adds site columns, content types, lists for Hello World items.",
        "id": "f1c4625d-e32a-4960-8166-7610cdcb24d1",
        "version": "1.0.0.0",
        "assets": {
          "elementManifests": [
            "elements.xml"
          ]
          // ,
          // "elementFiles": [
          //   "schema.xml"
          // ]
        }
      }
    ]
  },
  "paths": {
    "zippedPackage": "solution/hello-world-webpart.sppkg"
  }
}

Denloof commented 6 years ago

Same problem as vickeybird here. Webpart not showing up and after removal there where several files in the recyclebin, one of those is 0kB. And that one can't be removed.

Edit: /_api/web/GetClientSideWebParts doesn't show the desired webpart appcatalog/Lists/ComponentManifests/AllItems.aspx shows the correct manifest

Denloof commented 6 years ago

Ok, after an update in sharepoint (??, recyclebin look/behaves differently) things seem to be working again. Was now able to remove the item and reinstall, now webpart shows up.

paigeflourin commented 6 years ago

@smithderekm

I did exactly what you did but it's still not showing up :( This is my package-solution.json

{
  "solution": {
    "name": "our-applications-client-side-solution",
    "id": "c23661a1-50a2-4b69-b8f2-9b7a7a5db2b1",
    "version": "1.0.2.9",
    "features": [
      {
        "id": "3be4d3fd-963b-4a1b-9607-cddb02c4cf16",
        "title": "Our Applications Web part feature",
        "description": "A feature which activates the Client-Side WebPart named Our Applications",
        "version": "1.0.2.9"
      },
      {
      "title": "our-applications-client-side-solution",
      "description": "our-applications-client-side-solution",
      "id": "523fe887-ced5-4036-b564-8dad5c6c6e24",
      "version": "1.0.2.9",
      "assets": {
        "elementManifests": [
          "elements.xml"
        ],
        "elementFiles":[
          "schema.xml"
        ]
      }
    }]
  },
  "paths": {
    "zippedPackage": "solution/our-applications.sppkg"
  }
}

Denloof commented 6 years ago

I have the same problem again... Update an existing webaprt (updated the version in package-solution.json) Update sppkg file in appcatalog (overwrite), shows new version number. Go to sitecolletion where the existing webapart was working, update to new version and nothing works... The webaprt isn't showing up anymore.

/_api/web/GetClientSideWebParts doesn't show the desired webpart appcatalog/Lists/ComponentManifests/AllItems.aspx shows the correct manifest

Removig reinstalling doesn't work, same result.

Am I missing something or is this just buggy?

Leif-Frederiksen commented 6 years ago

I also have this problem again now - but only on some sites. This seems to be really buggy and fragile.

Please advice!

pasadyaguy commented 6 years ago

I am also experiencing this issue. Any update would be great. When I first created the solution, I was able to add the new webpart to a modern page. I made some changes, updated the package in the AppCatalog and tried adding to a new site I was working on and now it won't show up at all.

It does NOT appear when I go to "_api/web/GetClientSideWebParts" on the site I am working on. It does appear when I go to "/Lists/ComponentManifests/Allitems.aspx".

patmill commented 6 years ago

Did you approve / activate the updated package?

From: Brian Smith notifications@github.com Sent: Monday, January 29, 2018 11:36:06 AM To: SharePoint/sp-dev-docs Cc: Pat Miller (SHAREPOINT); Mention Subject: Re: [SharePoint/sp-dev-docs] SpFx Helloworld webpart does not show up under modern Page toolbox (#775)

I am also experiencing this issue. Any update would be great. When I first created the solution, I was able to add the new webpart to a modern page. I made some changes, updated the package in the AppCatalog and tried adding to a new site I was working on and now it won't show up at all.

It does NOT appear when I go to "_api/web/GetClientSideWebParts" on the site I am working on. It does appear when I go to "/Lists/ComponentManifests/Allitems.aspx".

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fissues%2F775%23issuecomment-361360663&data=02%7C01%7CPat.Miller%40microsoft.com%7C1c347abf444d44d3d67008d5674f8b1c%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636528513684536533&sdata=FYYZHkNmdqSS3BW4rReHcJL6UmNKzIkv%2FEPDCxbKmsA%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADl-SYKi_JvSD2JdGgQ0xWooGHjdJLnuks5tPh2mgaJpZM4OyQo6&data=02%7C01%7CPat.Miller%40microsoft.com%7C1c347abf444d44d3d67008d5674f8b1c%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636528513684536533&sdata=agP%2F0LU2UIXx%2Bwls4VQc6qBFZYYBGjE07MaXQXxUFZI%3D&reserved=0.

pasadyaguy commented 6 years ago

@patmill To be honest, I am not sure what you mean by approve / activate. When I drag and drop the solution into the app catalog. I am given a prompt to deploy the solution. Which may be what you are meaning by approve, right? Any site I go to, when I click on add an app, my web parts appear and I can add them. I just don't see them in the web part section when editing a page. I do see the web part app in site contents.

patmill commented 6 years ago

Sorry – yes, “Deploy”. Do you happen to know what your preconfigured entries section looks like in your manifest?

There have been some updates to the toolbox that are rolling out. I’ll follow up with that team as well.

Thanks.

From: Brian Smith [mailto:notifications@github.com] Sent: Monday, January 29, 2018 11:54 AM To: SharePoint/sp-dev-docs sp-dev-docs@noreply.github.com Cc: Pat Miller (SHAREPOINT) Pat.Miller@microsoft.com; Mention mention@noreply.github.com Subject: Re: [SharePoint/sp-dev-docs] SpFx Helloworld webpart does not show up under modern Page toolbox (#775)

@patmillhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpatmill&data=02%7C01%7CPat.Miller%40microsoft.com%7Cb74f454780414e79bcf508d5675216b4%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636528524696864754&sdata=QJ4F2fc3RMqVoUgvC86606XFbNUemgkWn1Rg8EXzPDc%3D&reserved=0 To be honest, I am not sure what you mean by approve / activate. When I drag and drop the solution into the app catalog. I am given a prompt to deploy the solution. Which may be what you are meaning by approve, right? Any site I go to, when I click on add an app, my web parts appear and I can add them. I just don't see them in the web part section when editing a page. I do see the web part app in site contents.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fissues%2F775%23issuecomment-361366075&data=02%7C01%7CPat.Miller%40microsoft.com%7Cb74f454780414e79bcf508d5675216b4%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636528524696864754&sdata=h1jqLoJbm4rCV9ck89AgUTMcFMilWA0FSNeMlFAGpQM%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADl-SZyTMxZGv4W1i6tOFxP5UzkW6sWlks5tPiHrgaJpZM4OyQo6&data=02%7C01%7CPat.Miller%40microsoft.com%7Cb74f454780414e79bcf508d5675216b4%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636528524696864754&sdata=9OLcQTmHb75cDf0PsPDqzdujS6mT4xFbTtu7NX2UVZw%3D&reserved=0.

pasadyaguy commented 6 years ago

@patmill Here is my preconfiguredEntries. The change I made are

added a few properties for defaults
removed officeFabricFontIconName and added iconImageUrl

Leif-Frederiksen commented 6 years ago

My observation of the problem is that the webpart shows up on some sites and on other sites it does not. Sites within the same tenant! Really strange and something I need to get sorted out real soon. Can we get some insight into what the REST call that shows the available webparts actually do?

Regards Leif

VesaJuvonen commented 6 years ago

Reopening for ensuring that would not get hidden as closed issue.

Leif-Frederiksen commented 6 years ago

I'll just post my WebPart manifest file here, if it's any help in debugging this issue:

{
  "$schema": "../../../node_modules/@microsoft/sp-module-interfaces/lib/manifestSchemas/jsonSchemas/client-side-component-manifest.schema.json",

  "id": "2fd7e645-afd2-44f9-b243-87d461e2cbd1",
  "alias": "LedelsessystemWebPart",
  "componentType": "WebPart",

  // The "*" signifies that the version should be taken from the package.json
  "version": "*",
  "manifestVersion": 2,

  // If true, the component can only be installed on sites where Custom Script is allowed.
  // Components that allow authors to embed arbitrary script code should set this to true.
  // https://support.office.com/en-us/article/Turn-scripting-capabilities-on-or-off-1f2c515f-5d7e-448a-9fd7-835da935584f
  "requiresCustomScript": false,

  "preconfiguredEntries": [
    {
      "groupId": "6737645a-4443-4210-a70e-e5e2a219133a",
      "group": { "default": "MTH" },
      "title": { "default": "MT Højgaard: Ledelsessystem" },
      "description": { "default": "Navigation til Ledelsessystemet." },
      "iconImageUrl": "https://sometenant.sharepoint.com/sites/SPFx/Bundles/SPFxMTHicon.png",
      "properties": {
        "description": "Ledelsessystem",
        "processLibraryName": "Pages",
        "toolsLibraryName": "Documents",
        "termSetName": "QMS Navigation",
        "resultSource": "578b90fb-655b-4b93-897c-f67a00c3029b"
      }
    },
    {
      "groupId": "6737645a-4443-4210-a70e-e5e2a219133a",
      "group": { "default": "MTH" },
      "title": { "default": "Ajos: Ledelsessystem" },
      "description": { "default": "Navigation til Ledelsessystemet." },
      "iconImageUrl": "https://sometenant.sharepoint.com/sites/SPFx/Bundles/SPFxMTHicon.png",
      "properties": {
        "description": "Ledelsessystem",
        "processLibraryName": "Sider",
        "toolsLibraryName": "Dokumenter",
        "termSetName": "QMS Navigation Ajos",
        "resultSource": "8eeb918e-c59d-4209-b7ed-e055a2821e38",
        "groupProcessLibraryName": "Pages",
        "groupToolsLibraryName": "Documents"
      }
    }
  ]
}

pasadyaguy commented 6 years ago

I was able to get it working again. But as @Leif-Frederiksen mentioned earlier, its fragile and buggy.. Steps I took to get it to work again without making any changes to the actual webpart.

Delete app from app catalog.
Go to recycle bin and delete the app package again there.
Go to second stage recycle bin and delete the app package again there.
Upload the solution package to the app catalog.
Go to the site and FULLY delete the app if it is still there. (First Stage and Second Stage).
Install app again.

This got it working for me. But I would hate to have to follow that process every time for each update as I have to fix the webpart on all sites/pages that it is being used...

patmill commented 6 years ago

Thanks Brian. We will continue to look into what's going on here.

Get Outlook for iOShttps://aka.ms/o0ukef

From: Brian Smith notifications@github.com Sent: Tuesday, January 30, 2018 12:30:29 PM To: SharePoint/sp-dev-docs Cc: Pat Miller (SHAREPOINT); Mention Subject: Re: [SharePoint/sp-dev-docs] SpFx Helloworld webpart does not show up under modern Page toolbox (#775)

I was able to get it working again. But as @Leif-Frederiksenhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fleif-frederiksen&data=02%7C01%7CPat.Miller%40microsoft.com%7Cf294e00cf86a4cf4c82a08d568204dd8%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636529410406628263&sdata=z1cKSuhaFUw8bKpRCvBIOge%2FzPLMiURkNv2b1UB074I%3D&reserved=0 mentioned earlier, its fragile and buggy.. Steps I took to get it to work again without making any changes to the actual webpart.

Delete app from app catalog.
Go to recycle bin and delete the app package again there.
Go to second stage recycle bin and delete the app package again there.
Upload the solution package to the app catalog.
Go to the site and FULLY delete the app if it is still there. (First Stage and Second Stage).
Install app again.

This got it working for me. But I would hate to have to follow that process every time for each update as I have to fix the webpart on all sites/pages that it is being used...

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fissues%2F775%23issuecomment-361724436&data=02%7C01%7CPat.Miller%40microsoft.com%7Cf294e00cf86a4cf4c82a08d568204dd8%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636529410406628263&sdata=u75mWigabPZaXBKQkpSdjTEGrU4tpbQJM%2FyYpVlNmXw%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADl-Salt8qmoqLuMHbC8cZXSVBTuvOieks5tP3vlgaJpZM4OyQo6&data=02%7C01%7CPat.Miller%40microsoft.com%7Cf294e00cf86a4cf4c82a08d568204dd8%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636529410406628263&sdata=6NVaeUeROpuACZqvFI9QJ9iz5GX41%2FvljoppDP55KJc%3D&reserved=0.

paigeflourin commented 6 years ago

Mine also worked when i fully removed the package from the appcatalog and redeployed it again.

patmill commented 6 years ago

If it happens again, and you know how to get the information, could you find the correlation ID for the network request that populates the toolbox? We can pull logs and see if anything shows up (or at least add additional logging to help track it down).

From: Page Flourin Tangalin notifications@github.com Sent: Tuesday, January 30, 2018 4:05:54 PM To: SharePoint/sp-dev-docs Cc: Pat Miller (SHAREPOINT); Mention Subject: Re: [SharePoint/sp-dev-docs] SpFx Helloworld webpart does not show up under modern Page toolbox (#775)

Mine also worked when i fully removed the package from the appcatalog and redeployed it again.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSharePoint%2Fsp-dev-docs%2Fissues%2F775%23issuecomment-361777748&data=02%7C01%7CPat.Miller%40microsoft.com%7Cb8ebdb175ef44e44166b08d5683e6675%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636529539575394547&sdata=zM3fu9hdXQqki7vpWbsXMXPkS%2BPNFXbasUsaabANWI8%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADl-SfEySMRdAt4ZS7joYsDO1JhSW5f6ks5tP65igaJpZM4OyQo6&data=02%7C01%7CPat.Miller%40microsoft.com%7Cb8ebdb175ef44e44166b08d5683e6675%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636529539575404556&sdata=QDbIwMpI36RYD4BaH567IvdRrL4sTfItEl2A19nMQS0%3D&reserved=0.

Leif-Frederiksen commented 6 years ago

I have a pretty consistent scenario where the webpart appears in the toolbox on one site, but is missing on other sites in the same tenant.

Can we use this to gather something for debugging this issue? Please instruct on how I can deliver something useful.

NB: The site where it is actually working is a production site, so I'm not really up for the "remove from app catalog and add again" approach, since I will lose the config of the webpart on all pages where it is used.

Regards Leif

bubbleswap commented 6 years ago

Same issue here as Leif, the remove/re-deploy worked for some but not others, these subsites are all under the same collection.

Also am unable to delete the app from recycle bin of a site, I get the error message: Correlation ID: 2809469e-a0ad-5000-1cdd-8f9373bdf938

For the sites that worked, it worked after I repackaged the web part and updated the version number. I'm not certain the version number is what made a difference.

Also thought the "Site Features" might be an indicator, then that isn't true when a site with the app as "Active" in Site Feature still can't see the app in web parts gallery.

If there's anything else I can try, please do share, thanks in advance!

GrahamMcMynn commented 6 years ago

@bubbleswap - for the error of not being able to delete from the recycle bin please open a new issue @Leif-Frederiksen - please see below, for instructions on gathering a correlation ID.

Thanks for all the feedback. It actually looks like there are 2 classes of issues here:

The webpart never shows up being available anywhere.
The webpart is available on some sites but not others.

For case 1, the problem has a temporary fix. Basically anytime an exception was thrown during deployment we would mark the package as deployed and eat the exception. This is obviously bad and has been fixed by no longer eating the exception and marking the package as not deployed. Also, we update error field to include the correlation ID of the deployment. Our logging will help us determine what the root cause is, and we should be able to create a fix once we see this happen again (it has only rolled out to 75% of production, and just started on Sunday, but I don't see any instances of this yet).

For case 2, I am more interested as this is a new problem I have not seen before and am unsure of what is wrong. We would like more information on this in order to help us diagnose what the issue is. @Leif-Frederiksen - please follow these steps to capture a correlation ID:

Load developer tools and start a network trace (F12)
Load a modern page
Put it in edit mode.
Click the "+" to add a webpart
View your network trace in the developer tools, you will see a request to GetClientSideWebParts
Look at the response header sprequestguid and respond here with that, as well as your tenant domain
If you know what webpart is missing, please include the details of it such as name/component id.

Thank you for helping us track down this issue, Graham

Leif-Frederiksen commented 6 years ago

Hi Graham,

Here is the info:

sprequestguid: b426469e-5065-5000-a684-b9581c831c38 Tenant domain: mthportal.sharepoint.com

I am uncertain about the component id. I have the following Id's Solution: 7858eb79-bf7e-4481-8b3c-ceb6ad854d82 Webpart: 2fd7e645-afd2-44f9-b243-87d461e2cbd1 Group id of preconfigured entries: 6737645a-4443-4210-a70e-e5e2a219133a

To give you the full picture I post the content of the configuration files below - please let me know if I can provide more info.

package-solution.json:

{
    "solution": {
        "name": "MTH Ledelsessystem",
        "id": "7858eb79-bf7e-4481-8b3c-ceb6ad854d82",
        "version": "1.16.21.0",
        "iconPath": "Images/AppMTHicon.png",
        "skipFeatureDeployment": false
    },
    "paths": {
        "zippedPackage": "solution/MTH.Ledelsessystem.sppkg"
    }
}

webpartmanifest.json:

{
  "$schema": "../../../node_modules/@microsoft/sp-module-interfaces/lib/manifestSchemas/jsonSchemas/client-side-component-manifest.schema.json",

  "id": "2fd7e645-afd2-44f9-b243-87d461e2cbd1",
  "alias": "LedelsessystemWebPart",
  "componentType": "WebPart",

  // The "*" signifies that the version should be taken from the package.json
  "version": "*",
  "manifestVersion": 2,

  // If true, the component can only be installed on sites where Custom Script is allowed.
  // Components that allow authors to embed arbitrary script code should set this to true.
  // https://support.office.com/en-us/article/Turn-scripting-capabilities-on-or-off-1f2c515f-5d7e-448a-9fd7-835da935584f
  "requiresCustomScript": false,

  "preconfiguredEntries": [
    {
      "groupId": "6737645a-4443-4210-a70e-e5e2a219133a",
      "group": { "default": "MTH" },
      "title": { "default": "MT Højgaard: Ledelsessystem" },
      "description": { "default": "Navigation til Ledelsessystemet." },
      "iconImageUrl": "https://mthportal.sharepoint.com/sites/SPFx/Bundles/SPFxMTHicon.png",
      "properties": {
        "description": "Ledelsessystem",
        "processLibraryName": "Pages",
        "toolsLibraryName": "Documents",
        "termSetName": "QMS Navigation",
        "resultSource": "578b90fb-655b-4b93-897c-f67a00c3029b"
      }
    },
    {
      "groupId": "6737645a-4443-4210-a70e-e5e2a219133a",
      "group": { "default": "MTH" },
      "title": { "default": "Ajos: Ledelsessystem" },
      "description": { "default": "Navigation til Ledelsessystemet." },
      "iconImageUrl": "https://mthportal.sharepoint.com/sites/SPFx/Bundles/SPFxMTHicon.png",
      "properties": {
        "description": "Ledelsessystem",
        "processLibraryName": "Sider",
        "toolsLibraryName": "Dokumenter",
        "termSetName": "QMS Navigation Ajos",
        "resultSource": "8eeb918e-c59d-4209-b7ed-e055a2821e38",
        "groupProcessLibraryName": "Pages",
        "groupToolsLibraryName": "Documents"
      }
    }
  ]
}

will101 commented 6 years ago

Also having this issue alot: @smithbrianscott 's suggestions worked though!

GrahamMcMynn commented 6 years ago

@Leif-Frederiksen - thank you for sending that, I can't fetch the logs until Monday, but I will take a look then.

Leif-Frederiksen commented 6 years ago

That sounds good @mcmynn83. I'm curious as to what you can see from the logs on Monday. Have a nice weekend until then :-)

Regards Leif

paoIpao commented 6 years ago

Same problem. I try sample "react-script-editor" on site with specific site collection app catalog. NO show on modern page (also already remove all and reinstall but nothing happen). It's show in "features" list and also in "/Lists/ComponentManifests/AllItems.aspx" . If try in workbench it's works all fine.

tsekityam commented 6 years ago

There is an advisory SP128660 in Office Admin Center, which titled "Can't install or activate add-ins or modern SharePoint packages". Is this issue related to that advisory??

OverkillTV commented 6 years ago

Hmmm I think I met this issue last week when the webpart show up on first time deployment but after that every app upgrading will cause it to disappear from the Web Parts toolbox. Later then I found out that there is an issue with the "includeClientSideAssets" in the package-solution.json

I CREATED ANOTHER PROJECT with that "includeClientSideAssets" set to false and using the CDN URL instead and things are working now even after upgrading the app.

But I do recall that once it has disappeared then even set the "includeClientSideAssets" to false and re-deploy won't make it show up again.

Now I'm facing the issue with the app keep saying " The App is installing..." and just hang there forever without any errors.

telmocruz commented 6 years ago

I was also facing this issue , the only workaround i found was to delete the app packages from the site collections and from the app catalog and then redeploy everything. Is is working now as expected in all sites except one

Leif-Frederiksen commented 6 years ago

Hi @mcmynn83 - did you get a look at the logs?

pedro-pedrosa commented 6 years ago

I had the same issue. Increasing the version number in package-solution.json and deploying again to the app catalog then upgrading and/or re-installing multiple times would never work. Removing from the app catalog and recycle bin 2nd stage did the trick.

I did notice something else, if I added another web part using the yeoman generator, only the new web part would show up if I upgraded the solution without removing from the app catalog. However, as soon as I increased the version number and upgraded again, my recently added web part would also disappear.

Hope this helps.

poikjo commented 6 years ago

I noticed on my tenant that */CLIENTSIDEASSETS was not added to to public CDN origins event thou CDN was enabled. Added that manually, removed app from AppCatalog and from sites and the webpart showed up. (this happened on Classic SP)

Leif-Frederiksen commented 6 years ago

Hi @mcmynn83 - any success with looking into the logs?

Regards Leif

tsekityam commented 6 years ago

I logged this case as a Severity B premier support ticket. MS CS team told me that their engineer will contact me tomorrow at 9am (HKT)

BTW, I am using Azure CDN, but I still experience the issue. I don't think that it is a SharePoint CDN config issue.

Leif-Frederiksen commented 6 years ago

That sounds great @tsekityam - looking forward to hearing what they find :-)

pdemro commented 6 years ago

I am experiencing this today on multiple tenants. Thanks for the research on this all. I will try the suggested workaround of completely reinstalling from app catalog.

edit: reinstalling app package to tenant and then reinstalling to site collections resolved the issue.

SharePoint / sp-dev-docs