Command Line Argument --load-extension not working

Hello, I developed a small chrome extension that lets webpages to call chrome extension APIs in the background (thus enabling me to run CDP commands), but am not able to load it with the EXE app created by ExeOutput.

I am trying to load the unpacked extension from its folder, NOT the packed CRX file.

I tried adding --load-extension=myextfolder in AdditionalChromiumArgs but looks like this argument does not have any effect at all. The extension is not loaded and tehre are no error messages.

[1]
Suppose the EXE file name is "App.exe" and I have placed myextfolder in the same folder as App.exe.

when I run the app from Command Prompt with App.exe --load-extension=myextfolder it loads the extension as expected.

[2]
When I run the command App.exe --load-extension=wrongfoldername in Command Prompt, the app starts but shows an error popup "Failed to load extension from ...\wrongfoldername. Manifest file is missing or unreadable." which is obvious because we entered the folder name that does not even exist.

[3]
When I add the --load-extension=wrongfoldername argument in AdditionalChromiumArgs Rendering Engine settings, the app loads normally and does not show any error message at all.

This means the --load-extension argument does not have any effect at all, and so I cannot load my extension.

Kindly look into this and help me load my own extension at app startup, thanks!

Unfortunately, CEF in ExeOutput has a very limited extension support, but with the recent CEF releases, we'll check whether this has been improved. Note that we are focused on WebView2 now, and probably we'll depreciate CEF as WebView2 offers the opportunity to get smaller EXE files.

gdgsupport said:

CEF in ExeOutput has a very limited extension support

Click to expand...

As mentioned in the main post, running App.exe --load-extension=myextfolder from windows command prompt works well and the extension is loaded as expected.

That would mean CEF does support loading unpacked extensions from commandline - it is just that the same parameter does not work when added to the AdditionalChromuimArgs.

jaydadhania08 said:

As mentioned in the main post, running App.exe --load-extension=myextfolder from windows command prompt works well and the extension is loaded as expected.

That would mean CEF does support loading unpacked extensions from commandline - it is just that the same parameter does not work when added to the AdditionalChromuimArgs.

Click to expand...

please let me know if any update, have the exact problem