Configuration file is not read apikey etc

[Ahnafudin]

I configured the config.js file on the latest version of CapSolver.Browser.Extension-chrome-v1.11.0 and it doesn't read the apikey on the chrome extension

However, I tried using the CapSolver.Browser.Extension-v.1.7.1 version in the config.json file and it read the apikey on the chrome extension

Maybe the file that connects config.js to the latest file has an error?

[sergio-itru]

solution is to add newline ='\n' when write to a file. like this with open(path, 'w', encoding='utf-8',newline='\n') as f:

[ducklin404]

For anyone coming here later, there is already an issue opened here.
Here is my workaround: #5 (comment).
It won't show the API key in the extension, but it will still solve the issue.
Also, the API key to add in my-content-script.js can be find by this:
manualSolving:!1,apiKey:"",appId:""

[Ahnafudin]

For anyone coming here later, there is already an issue opened here. Here is my workaround: #5 (comment). It won't show the API key in the extension, but it will still solve the issue. Also, the API key to add in my-content-script.js can be find by this: manualSolving:!1,apiKey:"",appId:""

nice, so have to add the API key in both files: my-content-script.js and assets/config.js