Verse Extension Installation Fails

Development Programming & Scripting
,
1

The Verse extension started to become buggy. It wouldn’t detect errors and it said the connection crashed multiple times.

So I uninstalled the Verse extension and tried to download it again but I keep getting
installation failed and the error message says:
“package is invalid because it does not contain the file extension.vsixmanifest at the root. The VSIX file may be corrupted.”

Here is the vsix file:

image
image740×399 16.3 KB

image

I use VSCode version: 64x 1.78.1
OS Name: Microsoft Windows 10 Home
OS Version: 10.0.19045 N/A Build 19045

Full Error Message:
27/02/2024 15.36.04 - Microsoft VSIX Installer
27/02/2024 15.36.04 - -------------------------------------------
27/02/2024 15.36.04 - vsixinstaller.exe version:
27/02/2024 15.36.04 - 17.8.2368+6fbeaa1954
27/02/2024 15.36.04 - -------------------------------------------
27/02/2024 15.36.04 - Command line parameters:
27/02/2024 15.36.04 - C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service\VSIXInstaller.exe,E:\test\Verse.vsix
27/02/2024 15.36.04 - -------------------------------------------
27/02/2024 15.36.04 - Microsoft VSIX Installer
27/02/2024 15.36.04 - -------------------------------------------
27/02/2024 15.36.04 - Initializing Install…
27/02/2024 15.36.04 - Searching for applicable products…
27/02/2024 15.36.04 - System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> Microsoft.VisualStudio.ExtensionManager.MissingPackagePartException: This VSIX package is invalid because it does not contain the file extension.vsixmanifest at the root. The VSIX file may be corrupted.
at Microsoft.VisualStudio.ExtensionManager.InstallableExtensionImpl.ReadVSIXManifestFromPackage(Stream stream, CultureInfo preferredCulture)
at Microsoft.VisualStudio.ExtensionManager.InstallableExtensionImpl…ctor(String path, CultureInfo preferredCulture)
— End of inner exception stack trace —
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object args, CultureInfo culture, Object activationAttributes, StackCrawlMark& stackMark)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object args, CultureInfo culture, Object activationAttributes)
at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object args, CultureInfo culture, Object activationAttributes)
at VSIXInstaller.ExtensionEngineFactoryForSku.GetTypeFromEngine[TInterface](SupportedVSSKU sku, String typeName, Object constructorArguments)
at VSIXInstaller.ExtensionService.GetInstallableDataImpl(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable1& skuData) at VSIXInstaller.ExtensionService.GetInstallableData(String vsixPath, String extensionPackParentName, Boolean isRepairSupported, IStateData stateData, IEnumerable1& skuData)
at VSIXInstaller.ExtensionPackService.IsExtensionPack(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.ExtensionPackService.ExpandExtensionPackToInstall(IStateData stateData, Boolean isRepairSupported)
at VSIXInstaller.App.Initialize(Boolean isRepairSupported)
at VSIXInstaller.App.Initialize()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute(

2

Hi, have you already tried verifying your FN/UEFN files through EGS?

In EGS:

  • Click the 3 dots on the FN tile
  • Click “Manage”
  • Click “Verify Files”
3

Actually, I did what you did and uninstalled the Verse Extension in VSCode. To re-install it I just dragged the Verse.vsix file from
“C:\Program Files\Epic Games\Fortnite\VSCode\Verse.vsix” into the extensions sidebar in VSCode and it reinstalled fine.

4

Yeah, I got it working late last night with the same solution. However, the extension was hidden when I added it back to vscode. So, I ran some troubleshooting commands, which made it appear visible in my extensions, allowing me to enable it. Thanks for the help anyway! :slight_smile: