Forum Discussion
Invalid Package - Sharepoint Framework Extensions
- Jun 07, 2017
Issue was in the elements.xml file, but not in encoding. More obvious than that, but still hard to catch. App catalow actually has actually "unavailable apps" link, which provides details on the possible errors and it's typically really accurate.
If you open up the elements.xml file from the sharepoint/assets folder, you can see that the last Elements element is missing closing tag, like defined in above exception. Below is the original Elements.xml file content and you can see that we are missing final > closing. After adding that missing character there, it was all good for deployment.
<?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <CustomAction Title="SPFxApplicationCustomizer" Location="ClientSideExtension.ApplicationCustomizer" ClientSideComponentId="43833b44-df29-40bf-aec2-294dd435ee05"> </CustomAction> </Elements
So - completely logical reason, was just hard to spot.
Hi Pat, thanks for the quick reply, yes its a developer tenant, I created this one when the first public preview of SPFx came out last year, so I dont think that should be the issue, but if there is a way to verify via powershell or something in the admin center, let me know and I can double check.
In the meantime, I also uploaded a .RAR file with all the code, in case anyone on the PG can take a quick look.
Thanks again
Hi Luis,
apparently issue was visible only when you reference elements.xml file in the package. If you remove the reference from package-solution.json, everything was working fine. There was no visible reason for why it failed, so suspecting some sort of an encoding issue.
I deleted existing elements.xml file and recreated that with needed elements and all works fine. I can't really explain this in 100% level, but that should fix the issue with you as well. If you still though have the original package (sppkg, which failed), can you zip that and also share it, so that we can truly do a repro for this, since want to understand what actually in detailed went wrong, so looping right engineers for this to avoid future issue.
- DeletedJun 07, 2017
Thanks Vesa for your reply, I will try your suggestion when I get home at night, in the meantime, please see the app package attached.