uBO Dev release doesn't auto update on Android Chromium Forks

[DarkHorse313]

Prerequisites

• I verified that this is not a filter list issue. Report any issues with filter lists or broken website functionality in the uAssets issue tracker.
• This is NOT a YouTube, Facebook or Twitch report. These sites MUST be reported by clicking their respective links.
• I performed a cursory search of the issue tracker to avoid opening a duplicate issue.
• The issue is not present after disabling uBO in the browser.
• I checked the documentation to understand that the issue I am reporting is not normal behavior.

I tried to reproduce the issue when...

• uBO is the only extension.
• using a new, unmodified browser profile.

Description

uBO dev release on github says that that will automatically updating but that didn’t happened on Chromium Forks on Android such as Aerium Browser, Bare Browser, Vivaldi Browser...

A specific URL where the issue occurs.

the extension itself https://github.com/gorhill/uBlock/commit/d0b84d75f9c5a61304e4987b284baee3bd689d2b

Steps to Reproduce

Please look into the inside extension problem

Expected behavior

uBO dev .crx release should auto updating itself.

Actual behavior

After I know it's been removed from the web store, but I've installed the .crx version from the Github repository but I have to download the file and drag it to the extensions menu on Chromium fork such as Aerium Browser, Bare Browser, Vivaldi Browser for each of my Chromium fork browsers everytime the dev build updates. Is there a way or is there a way in the works to let it auto update like it used to do from the web store? I think it should be possible because gorhill/uBlock@d0b84d7

Configuration

gorhill/uBlock@d0b84d7

[gorhill]

Looks like I made a mistake of using updateURL instead of update_url in the manifest. I will fix this for next dev build but this also mean a manual update will be needed before the fix works.

---

Actually I don't need to wait for a new release, I just re-generated all the crx packages, so hopefully the extension will properly auto-update from now on, it just requires to install one of the updated crx packages from the release section.