Skip to content

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

Closed

Description

@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

Activity

  1. gorhill commented on Sep 12, 2026

    @gorhill
    Member

    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.

  2. thinkpad4 commented on Sep 14, 2026

    @thinkpad4

    @gorhill I installed the re-generated CRX package and it still didn't autoupdate from dev build 1.74.1b6 to 1.74.1b7

  3. gorhill commented on Sep 15, 2026

    @gorhill
    Member

    Just wait at least 24h.

  4. thinkpad4 commented on Sep 15, 2026

    @thinkpad4

    Will do. Edit: side note, will this work on desktop browsers too?

  5. DarkHorse313 commented on Sep 16, 2026

    @DarkHorse313
    Author

    Thanks alot it’s work now

  6. added
    bugSomething isn't working
    fixedissue has been addressed
    on Sep 19, 2026
  7. Rikk commented on Oct 17, 2026

    @Rikk

    @gorhill I was waiting for my browsers to auto-update from 1.75.1b11 to 1.75.1b12 but nothing yet. It has been released 4 hours ago. Wouldn't it be better to use https://raw.githubusercontent.com/gorhill/uBlock/refs/heads/master/dist/chromium/update-dev.xml instead of https://cdn.jsdelivr.net/gh/gorhill/uBlock@master/dist/chromium/update-dev.xml for the update checker?

  8. gorhill commented on Oct 17, 2026

    @gorhill
    Member

    Browsers auto update extensions according to their own update schedule, just wait for it to auto update yours. There is no emergency fix in latest dev build, there is no need to be anxious about it.

  9. krystian3w commented on Oct 18, 2026

    @krystian3w
  10. Rikk commented on Oct 18, 2026

    @Rikk

    Hey @krystian3w nice tool! Thanks for the tip!

    It seems we can automate the purge with a direct url: https://purge.jsdelivr.net/gh/gorhill/uBlock@master/dist/chromium/update-dev.xml (from the original url just replace "cdn." with "purge.") [reference]

    Does it clear the cache only for me or for everyone?

  11. krystian3w commented on Oct 18, 2026

    @krystian3w

    I think this applies to everyone, so there’s no point in clearing it if the file hasn’t been updated on GitHub – which the CDN detects within 24 hours or up to 7 days.

    I think a free proxy from another country or continent will suffice for the test, as it seems no one has yet set up a private script to flush the CDN two minutes after a commit.

  12. locked as resolved and limited conversation to collaborators on Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingfixedissue has been addressed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions