My extension is getting disabled when I do an update

[Mujtaba Idrees]

Hi, 

We have updated our extension to a new version for the first time and noticed that soon after the update went live, the extension was automatically disabled for all users until they manually enabled it again. 

In this extension, we have host permission enabled because we want to help users improve their AI prompts at various chat agents. I understand that it requires more permissions, but if the user has already granted the permissions, then why do we need to disable it at every update? In this update, we did not ask for any new permissions on any new site. So what the user accepted before was still valid for this version. 

This is an alarming long-term problem for us because if 1000s of users use this extension in the future, one small bugfix will disable this extension on their machines, destroying all our efforts and distribution. 

I request you to please fix it as a priority. 

Here is the extension link: https://chromewebstore.google.com/detail/ai-context-flow-use-your/cfegfckldnmbdnimjgfamhjnmjpcmgnf?authuser=0&hl=en-GB

Best regards,

Mujtaba

[Oliver Dunk]

Hi,

In your last release, you added host permissions for `http://localhost:3000/*`. Since this is a new host which the user has not previously given the extension permission to run on, it is expected that the extension will be disabled.

You can learn how to see the warnings that you might encounter ahead of time here: https://developer.chrome.com/docs/extensions/develop/concepts/permission-warnings#view_warnings

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/d6866230-12cc-4efd-97c8-00608e04f431n%40chromium.org.

[Mujtaba Idrees]

Hi Oliver, 

Thanks for the quick response, much appreciated. 

Maybe we added localhost and missed it. Just to confirm the policy, it will only be disabled if we change the host permissions?

Best, 

Mujtaba

[Oliver Dunk]

Not quite. Generally disabling an extension is linked to the level of access increasing - this can be, for example, adding a new content script that injects on a new host. It can also be adding a new API permission.

This is determined automatically but the logic is complicated. I'd encourage you to use the documentation I linked to check any updates you are concerned about.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB