David Fernández Aldana

Hello: I've investigated this issue, and the problem arises in this `finally` block https://github.com/mozilla/web-ext/blob/7a1eba57e742aeef50b7342d47dca2ba0ac1838a/src/extension-runners/firefox-android.js#L598 with the whole relevant section being: ```js try { // Got a debugger socket file to...

@rpl can you assign me to this? This would be my first contribution but I think it's a pretty easy fix

@willdurand thanks will do

Further investigating this happens in either of the following two conditions (in `run`): - Automatic reloading is disabled. - Waiting to launch the activity on Android. For example: this occurs...

@willdurand PR linked and ready ;)

> ### Is this a feature request or a bug? > Feature > > ### What is the current behavior? > [run](https://extensionworkshop.com/documentation/develop/web-ext-command-reference/#web-ext-run) only supports Chrome and Firefox > > ###...

It does by specifying the `--target` as `chromium` and specifying `--chromium-binary` to the path of your Edge binary. I guess you are saying the current Edge, the legacy Edge is...

Sure, especially since there are developers who might think `chromium` only relates to `chrome` although the `chromium-binary` doc already says so. But anyway, since this is a open-source repo suggest...

I'm pretty sure it does since the documentation does not mention any specific OS (but I cannot personally confirm)

If desired, this could be further simplified by using the suggested library at [https://github.com/PlasmoHQ/edge-addons-api](https://github.com/PlasmoHQ/edge-addons-api) instead of plain http requests: ```js import { EdgeAddonsAPI } from "@plasmohq/edge-addons-api" const client = new...