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.

Sign up for GitHub

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

Jump to bottom

SpFx Helloworld webpart does not show up under modern Page toolbox #775

Closed
Moreshwar83 opened this issue Aug 9, 2017 · 80 comments
Closed

SpFx Helloworld webpart does not show up under modern Page toolbox #775

Moreshwar83 opened this issue Aug 9, 2017 · 80 comments
Labels
area:spfx Category: SharePoint Framework (not extensions related) status:fixed Issue was fixed in current or prior release. status:tracked Currently tracked with Microsoft’s internal issue tracking system. DO NOT ADD/REMOVE (MSFT managed) type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.

Comments

@Moreshwar83
Copy link

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.

Category

  • Bug

spfx issue

If you are planning to share a new feature request (enhancement / suggestion), please use SP Dev UserVoice at http://aka.ms/sp-dev-uservoice.

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
Copy link
Contributor

patmill commented Aug 9, 2017

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

@Moreshwar83
Copy link
Author

Moreshwar83 commented Aug 9, 2017 •
edited
Loading

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
spfx1

@patmill
Copy link
Contributor

patmill commented Aug 9, 2017

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
Copy link
Author

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
Copy link
Author

It started working now.
Resolution:

  1. Go to ~appcatalog/AppCatalog/Forms/AllItems.aspx
  2. Edit properties for the web part, I added short description & Description and saved.
    Webpart started appearing under ~appcatalog/Lists/ComponentManifests/AllItems.aspx
  3. 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
Copy link
Contributor

patmill commented Aug 10, 2017

Glad you got it sorted out.

@Dilli
Copy link
Contributor

Dilli commented Aug 23, 2017 •
edited
Loading

@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
Copy link
Collaborator

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
Copy link
Contributor

Dilli commented Aug 24, 2017 •
edited
Loading

@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
Copy link
Collaborator

@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
Copy link
Contributor

Dilli commented Aug 28, 2017

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

@paigeflourin
Copy link

paigeflourin commented Nov 23, 2017 •
edited
Loading

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
Copy link

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
Copy link

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
Copy link

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
Copy link

Denloof commented Dec 19, 2017 •
edited
Loading

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
Copy link

Denloof commented Dec 20, 2017

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
Copy link

@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
Copy link

Denloof commented Jan 25, 2018

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
Copy link
Contributor

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

Please advice!

@pasadyaguy
Copy link

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
Copy link
Contributor

patmill commented Jan 29, 2018 via email

@pasadyaguy
Copy link

@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
Copy link
Contributor

patmill commented Jan 29, 2018 via email

@pasadyaguy
Copy link

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

  • added a few properties for defaults
  • removed officeFabricFontIconName and added iconImageUrl

image

@Leif-Frederiksen
Copy link
Contributor

Leif-Frederiksen commented Jan 29, 2018 via email •
edited
Loading

@VesaJuvonen VesaJuvonen reopened this Jan 30, 2018
@VesaJuvonen
Copy link
Contributor

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

@Leif-Frederiksen
Copy link
Contributor

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"
      }
    }
  ]
}

@wobba
Copy link
Contributor

wobba commented Feb 15, 2018

@VesaJuvonen so this means you have been able to repro the issue and figured out the problem? Could you elaborate on the actual issue causing this?

@VesaJuvonen
Copy link
Contributor

This is now fixed. We have a solid repro and have fixed the underlying issue as part of the v1.4.1 release. This was related to false behavior in Yeoman template solution packaging, which caused feature ID to get updated on a newer version of the package. ´

Unfortunately fixing this from existing environments will require some extra work and you should be upgrading to v1.4.1 as soon as possible. Here's a direct quote from the 1.4.1 release notes.

Fixed issue in the generator that prevented activation of new versions of SPFx packages.

Symptoms - You deploy a new version of SharePoint Framework packages and you no longer see your web parts in web part picker.

Issue reported here: #775

Fix - To be able to fully successfully fix this issue, you will need to perform following steps in your SharePoint Online tenants.

  1. Remove all instances of existing SharePoint Framework solutions from site level
  2. Remove SharePoint Framework solution from app catalog
  3. Upload new SharePoint Framework solution built with 1.4.1 version to your app catalog
  4. Install SharePoint Framework solutions back to sites.

Notice that this issue is not happening for tenant-scoped SharePoint Framework solutions and it's not happening for SharePoint add-ins.

You might potentially take advantage of the SharePoint ALM APIs or SharePoint PnP PowerShell cmdlets for add-ins to automate this needed process.

@VesaJuvonen VesaJuvonen added status:fixed Issue was fixed in current or prior release. and removed status:fixed-next-drop Issue planned to be fixed in an upcoming release. labels Feb 15, 2018
@wobba
Copy link
Contributor

wobba commented Feb 15, 2018 via email

@VesaJuvonen
Copy link
Contributor

@wobba - Please submit a new issue if needed, so that we can track that with repro steps and web part configuration setup. Thx. Otherwise, it's impossible for us to track the tasks in VSO - as all of these issues are automatically synced for internal processing for our team.

@andrewconnell andrewconnell mentioned this issue Feb 18, 2018
Closed
4 tasks
@Laskewitz
Copy link
Contributor

Laskewitz commented Feb 21, 2018 •
edited
Loading

I'm still having issues although I ran these steps:

To be able to fully successfully fix this issue, you will need to perform following steps in your SharePoint Online tenants.

Remove all instances of existing SharePoint Framework solutions from site level
Remove SharePoint Framework solution from app catalog
Upload new SharePoint Framework solution built with 1.4.1 version to your app catalog
Install SharePoint Framework solutions back to sites.

The webpart still isn't selectable in the toolbox...

EDIT: Nevermind. It looks like an administrator disabled the O365 CDN... and that results in the same issue. Either way, a transition to the Azure CDN seemed the solution for me.

This was referenced Feb 22, 2018
Closed
Closed
@vman
Copy link
Contributor

vman commented Mar 3, 2018

This one got me now as well. My SPFx 1.4.1 tenant scoped webpart had includeClientSideAssets set to true and same as @poikjo, I had the Office 365 CDN enabled on the tenant but did not have the */CLIENTSIDEASSETS origin added.

So the solution was to add the origin and the webpart started to appear in the "add new webpart" dialog.

(You can also turn off the Office 365 CDN in which case the web part should appear as well. The JS files will then be served from the app catalog)

@VesaJuvonen
Copy link
Contributor

Yep - few things to notice here.

  • @Laskewitz - If you are using the standard URL in the write-manifests.json as "cdnBasePath": "<!-- PATH TO CDN -->"- and you use asset packaging - then it does not matter if the CDN is enabled or not... If CDN is enabled, we'll load the web part from CDN, if not, we load it directly from app catalog... without any changes needed by the developers.
  • @vman - This is indeed something to notice. If you used CDN before CLIENTASSETS origin being there, you'll need to add that origin there manually or reactivate CDN

Not seeing any actual new issues here, so not reopening... if there are similar issues, please do open a new issue with sufficient details.

@tarjeieo tarjeieo mentioned this issue Mar 4, 2018
Closed
4 tasks
@agamadrid
Copy link

Hi,

I'm experiencing similar issue here.
I have a site collection with about 20-25 subsites.
I've installed the app at site collection catalog.
I'm using the 1.4.1 version.
For most of the subsites the webparts are available, but for some of them I can't see them.
Same app & same site collection.

Any idea or suggestion?
Thanks!

@Cyan005
Copy link

Cyan005 commented Mar 28, 2018 •
edited
Loading

I can confirm this issue is still lingering. To resolve the issue prior, I updated my solution to use 1.4.1. Then upon deployment seemed to be fine. Now performing some changes and redeployed the web part is no longer visible to add to the page onto the page.

EDIT I can confirm that the old version of the app was still installed in the app catalog. My newest 1.4.1 solution was installed over top of it (different tenant). Completely removing the app from the catalog and the site collections and installing again made it visible again.

@wobba
Copy link
Contributor

wobba commented Mar 28, 2018

@Cyan005 Check my post http://www.techmikael.com/2018/02/alternative-way-to-solve-issue-where.html or the release notes at https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-for-SPFx-Package-Version-1.4.1#other-relevant-fixes on how to resolve this.

@RoyKimYYZ
Copy link

I have been struggling with this issue where deploying the react-script-editor (https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor) and it is not showing in the toolbox of Site Pages in modern team site and communication site. I cloned the repo 2 weeks ago which means I have the newest 1.4.1 spfx as I see it referenced in package.json.

I followed the many suggestions in this thread I can say I removed from Site Collection and Tenant App Catalog countless times and redeployed manually and via PnP Powershell.

I have tested even across 2 different tenants which are more cleaner than my primary dev tenant.

My general approach is

  1. Create private CDN such as \sites\CDN\siteassets\ and PnP PowerShell to set the CDN origin
  2. Deploy to tenant App Catalog. SkipFeatureDeployment is TRUE so that it is deployed to all sites
  3. Go to either a modern team site, communication site, or classic site to attempt to find and add the Modern Script Editor web part.
  4. Issue: I only can see this web part in toolbox for 3-5 classic sites among 3 different tenants.
    I am able to to see add/publish 1 other SPFX sample web parts from this repo.

I am particularly interested in using the react-script-editor webpart. And I only changed the cdnbasePath and skipfeaturedeployment settings in the .json. No other code changes. gulp --ship and gulp package-solution -ship

Appreciate any advice.

@patmill
Copy link
Contributor

patmill commented Apr 15, 2018 via email

@RoyKimYYZ
Copy link

Thanks @patmill . I just used some powershell to disable powershell. Thought it be something simple that I missed. Much appreciated for the guidance!!

@wobba
Copy link
Contributor

wobba commented Apr 15, 2018

@RoyKimYYZ as @patmill said, default settings are to require a script enabled site. At the bottom of https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor the readme has notes how to deploy to noscript sites or tenant wide.

@RoyKimYYZ
Copy link

@wobba Thanks for pointing that out. I guess I didn't read it more carefully and should have played around the requiresCustomScript setting. By this web part "not being allowed", I just thought it would error out in App Catalog or when Adding App to the site. Nevertheless, I'm still learning the nitty gritty details of the multi-step process of install,deploy,activate multiplied by various config setting options. Appreciate your hard work and guidance!

@frevds
Copy link

frevds commented Apr 17, 2018

Anybody having issues emptying the recycle bin to remove the app do this:
After removing the app in the classic mode (which is the only mode you can remove an app in), change back to modern mode (there should be a link below the side navigation) and open the recycle bin in the modern mode. this mode allows to delete the package from the recycle bin.

@pyranha-ch pyranha-ch mentioned this issue Jul 6, 2018
Closed
4 tasks
@TylerLu
Copy link

TylerLu commented Jan 25, 2019

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"
  }
}

Thanks! This works for me. One thing to be noticed is that the id of web part feature must be the same as the id used in your XXXXWebPart.manifest.json

@anthonynhn
Copy link

in my case, I have several webparts in the same project (e.g. 4 webparts in total):

  • In the workbench, all webparts are displayed properly in the toolbox to be added into the page.
  • In the modern page, only the first 2 created webparts are displayed in the toolbox, and the latest 2 webparts were NOT displayed in the toolbox.

Troubleshooting: I ensured that Description and Short Description have values in the App Properties, but the latest 2 webparts were not found anywhere (also checked in https://yourtenant.sharepoint.com/sites/yoursite/_api/web/GetClientSideWebParts and https://yourtenant.sharepoint.com/sites/yourappcatalog/Lists/ComponentManifests/AllItems.aspx )

Solution:
I need to delete the app in the Site Contents and re-added the app back. My highlight is that we have a retention policy enabled in the tenant, and we must change the version of the app at Visual Studio Code (config\package-solution.json) so that we can re-add the same app (with a newer version) back to the Site Contents of the site.

@PieterHeemeryck
Copy link

PieterHeemeryck commented May 24, 2019 •
edited
Loading

I've also encountered this problem + found a solution that worked for me:

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".

My solution (for an SPFx solution NOT deployed to the entire tenant in one go):
Step 1: (preferrably) remove the apps on the site collections where you installed them. Do it like this: from site contents, remove. As a site collection admin (or global admin), go to the recycle bin. There is an error indeed when attempting to remove it there. However, change the url: _layouts/15/RecycleBin.aspx to _layouts/15/AdminRecycleBin.aspx. There, remove the app. Also, go to the second stage recycle bin (_layouts/15/AdminRecycleBin.aspx?View=2) and remove it there. Now the app is completely removed from your site collection.

Step 2: remove the spfx app from the app catalog. Repeat the steps with the admin recycle bin to make sure this item is completely gone from the app catalog site collection.

Step 3: re-add your spfx package to the app catalog. I did not have to alter any ids to get it to work.

Step 4: re-add your app to the site collection where you want to add your web part.

Step 5: find your web part in the toolbox ! You can now also check the following endpoints to see your web part listed:
_api/web/GetClientSideWebParts
/Lists/ComponentManifests/Allitems.aspx

@PieterHeemeryck
Copy link

#1253 Related issue

@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.
Assignees
No one assigned
Labels
area:spfx Category: SharePoint Framework (not extensions related) status:fixed Issue was fixed in current or prior release. status:tracked Currently tracked with Microsoft’s internal issue tracking system. DO NOT ADD/REMOVE (MSFT managed) type:bug-suspected Suspected bug (not working as designed/expected). See “type:bug-confirmed” for confirmed bugs.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests