We have a private extension in WebStore which only available to “trustedTesters”
Brave never updates such extensions in private list.
Even “update” button on extensions page doesn’t work.
Is there any way to let Brave update private extensions?
I personally love to use and encourage people to use Brave but it seems we need to switch back to Chrome since our extension updates can not be delivered to our users.
Description of the issue: How can this issue be reproduced?
Publish a private extension to Chrome webstore (trustedTesters)
Install extension to Brave
Send a new update to extension
Brave never updates extension. It always on installed version.
Expected result:
Brave should update private extensions.
We have the same issue at my company. We have an extension published on the Chrome WebStore that you can only view while being logged in with Google SSO, once installed it never updates even when clicking “Update” in developer mode.
It looks like the private nature of the extension is the problem here. I guess Chrome can do it if you’re logged in the browser, but here Brave doesn’t manage our Google account so maybe it can’t fetch the updates?
I suspect you’re right; this is probably due to Brave not using the Google Account of the user. Unlisted extensions work without issue, but anything that requires authentication would likely run into obstacles.
I’d love to hear more about this scenario. When somebody is added to the list of Trusted Testers, do they receive an email? And does that email ask them to navigate to the Chrome Web Store, and install the extension? If so, what does the user see when they visit that same extension page at a later point, when an update is available?
So with domain restriction people don’t receive any email, we give them the link of the extension on the Chrome Web Store, which they can acces only if they’re logged in with their Google account. The page always looks the same, except the published version number which of course increases for each update.
