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.
If you are planning to share a new feature request (enhancement / suggestion), please use SP Dev UserVoice at http://aka.ms/sp-dev-uservoice.
Upon installation of the app, it should create a list and i can add the webpart to the pages as well
The list is being created as i install the app, but when i try to add the app to my page, the app is not showing up in the list of the available apps.
1) Install the app
2) The list provisioned
3) add webpart to page
4) the app is not listed
This is my package-solution.json
{
"solution": {
"name": "our-applications-client-side-solution",
"id": "c23661a1-50a2-4b69-b8f2-9b7a7a5db2b1",
"version": "1.0.2.16",
"features": [
{
"id": "49280240-2932-4868-b668-19361475ac9b",
"title": "Our Applications Web part feature",
"description": "A feature which activates the Client-Side WebPart named Our",
"version": "1.0.2.15"
},
{
"title": "our-applications-client-side-solution",
"description": "our-applications-client-side-solution",
"id": "523fe887-ced5-4036-b564-8dad5c6c6e24",
"version": "1.0.2.15",
"assets": {
"elementManifests": [
"elements.xml"
],
"elementFiles":[
"schema.xml"
]
}
}]
},
"paths": {
"zippedPackage": "solution/our-applications.sppkg"
}
}
@paigeflourin - if you would like us to take a look at this we will need the entire package. Please upload it as an attachment.
Hi @mcmynn83 i have my application here: https://github.com/paigeflourin/our-applications
Hi @mcmynn83 have you looked into it? this is the project.
our-applications-master.zip
Thanks for sending that, we will take a look at this.
@paigeflourin - I built your package and installed it in a test tenant. Could you clarify what exactly you are seeing as the issue?
I did the following:
You'll have to be more specific as to what you are actually seeing wrong.
Also, one other thing, you have duplicated your component ID's between your 2 webparts.
Hi @mcmynn83 ,
in the package that i have upload i removed the provisioning of assets so when i put this:
{
"solution": {
"name": "our-applications-client-side-solution",
"id": "c23661a1-50a2-4b69-b8f2-9b7a7a5db2b1",
"version": "1.0.2.16",
"features": [
{
"id": "49280240-2932-4868-b668-19361475ac9b",
"title": "Our Applications Web part feature",
"description": "A feature which activates the Client-Side WebPart named Our",
"version": "1.0.2.15"
},
{
"title": "our-applications-client-side-solution",
"description": "our-applications-client-side-solution",
"id": "523fe887-ced5-4036-b564-8dad5c6c6e24",
"version": "1.0.2.15",
"assets": {
"elementManifests": [
"elements.xml"
],
"elementFiles":[
"schema.xml"
]
}
}]
},
"paths": {
"zippedPackage": "solution/our-applications.sppkg"
}
}
in my package-solution.json. the app would install properly and the list would be deployed. However, you wont be able to add a webpart because the "our-application" is nowhere to be seen.
Ok, so I do not see that. Please send the exact package you are using that is having the error as building the project you sent does not repro the issue.
hi @mcmynn83 apologies for that one, here is the package.
@paigeflourin - I'm sorry, but I still don't see the error you are suggesting. I went and added the package you sent (in the zip file under sharepoint\solution folder I added the sppkg file, added the app to the site, created a new page, and then saw Our-Application. It fails to load because it Failed to load URL 'https://campress.sharepoint.com/TeamApplications/our applications angular-ourapplicationsstrings_en-us_536e65149b0acf4d52c0043073b9fc59.js... But I don't see the webpart missing when trying to add it to a page.
@mcmynn83 was the list created upon adding the app? This is what happens to my app
I added the app, then the list gets created after:
then what i try to add it to my page, i do not see the application webpart:
i have attached the latest app that i have took the screenshot from
Our Applications Angular.zip
@mcmynn83 additionally, when i try to update the existing app on a site. i get the error "manifest not found"
@paigeflourin - that sounds like there was an issue at deploy time. There is currently a bug (which is being fixed and rolled out as we speak), which allows an app to say it is successfully deployed even when an error occurs. Could you go to your app catalog and try redeploying your app (either delete it and add it again, or undeploy and then deploy it).
hi @mcmynn83 ,
not sure what happened, but that completely resolved the issue. Apologies if it took much of your time. dont know why it wasnt showing initially.
Excellent glad to hear it is working!
Hello, I encountered a similar problem.
I deployed a first version of my SPFx projects with 1.0.0.0 version. I could see my web parts without any problems.
After that, I wanted to upgrade my version to 1.0.0.1. I'm upload my sppkg to catalog and I can see the update of its version on sharepoint. But, when I refresh my page I don't see my webparts !!!
After some tries, I founded a solution but it's not really very good ! I changed the solution ID when I increment my version (package-solution.json), I delete the old package and I upload the new solution with new ID and new version. With this way, I can see my webparts on the page.
Do you have any idea, why upgrading solution version doesn't work ?
Yes, this is a known issue. It should have been fixed with our rollout to 1.4.1. Please see issue https://github.com/SharePoint/sp-dev-docs/issues/775 for details.
How can I do when we I have to upgrade sppkg with app installed in many sub-sites ? I have to delete, re-install app manually ?
@mimosa803 - unfortunately that is true... you can also programatically do it using our ALM API... but it has to be done in each web that you are using the SPFX solution.
This bug happened again on latest spfx 1.9.1 .
Yes I am facing the same issue in spfx 1.9.1
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
Most helpful comment
Yes I am facing the same issue in spfx 1.9.1