[Bug] [Android] New addons are not being enabled in Tor browser

When installing new addons it shows that it is being installed but when browsing the internet on the hamburger with the subsection of Add-ons, only HTTPS Everywhere and NoScript is shown to be active and being used.

Installed version 10.5.5. (91.2.0)

added Android Bug labels

added Backlog label

changed milestone to %Tor Browser: 11.0 Issues with previous release

It's a feature.

@gaba

I think the tor browser in Android is set to run on "private browsing" mode by default. The newly installed add-ons doesn't seem to be enabled to run in private browsing mode by default.

If you install a new add-on, the private mask symbol in the add-on manager is not there unlike the default installed add-ons.

Recently reinstalled from f-droid and encountered the same issue. Note that the icons for the remaining add-ons don't always remain in place? Sometimes they both have the same icons. Not sure if relevant but felt like I should add.

mentioned in issue tpo/team#47 (closed)

@aguestuser

Could you please look at this as its quiet a problematic bug! It has been lingering for almost 6 months now without anyone looking at it.

Look at my comments here as I figured out what's happening:

#40606 (comment 2751353)

assigned to @aguestuser

added Roadmap::Future label and removed Backlog label

unassigned @aguestuser

Note:

On two old phones that I had in 2020 and 2021, I could utilize addons like uBlock Origin only if I selected the option to allow in private mode during the installation process of uBlock Origin. If I failed to select the "allow in private mode" option, the option would not appear in the addon menu for uBlock Origin.

In the current build (11.0.14, 96.3.0-release) on my current phone, I do not get the option to select "allow in private mode" during the installation process for any of the addons available for the Android Tor Browser at all.

This applies for the versions in Google Play and F-Droid.

removed milestone %Tor Browser: 11.0 Issues with previous release

This bug is a close second to fenix#40216 (moved) in terms of the number of support requests it's generating.

Well it's a pretty obvious bug that a lot of people encounter (probably trying to install and use uBlock Origin) and it shouldn't be that hard to fix it, probably something trivial considering it used to work some versions back

Please feel free to take a look and create a merge request if you wish! I'm sure someone will be able to review it.

Unfortunately I don't have the knowledge to make a fix myself, I was just assuming because as @Mystic said maybe it's just a flag that needs to be changed or similar

removed Roadmap::Future label

added Next label

removed Next label

added Roadmap::Future label

mentioned in issue #41156 (closed)

Fixed in #41156 (closed)

closed