Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add-on Google Chrome / Edge disabled by Google #42

Open
supertanuki opened this issue Jan 3, 2022 · 6 comments
Open

Add-on Google Chrome / Edge disabled by Google #42

supertanuki opened this issue Jan 3, 2022 · 6 comments

Comments

@supertanuki
Copy link
Collaborator

supertanuki commented Jan 3, 2022

In french : l'extension a été désactivée par Google pour la raison suivante :

Règles non respectées :
Utilisation des autorisations :
Référence du cas de non-respect du règlement : Purple Potassium
Description du cas de non-respect du règlement : les autorisations suivantes sont demandées, mais pas utilisées :
storage
Solution : supprimez les autorisations ci-dessus
Extrait du règlement du programme :
Demandez les autorisations nécessaires les plus limitées pour exécuter les fonctionnalités ou les services de votre produit. Ne demandez pas d'autorisations pour des fonctionnalités ou services que vous n'avez pas encore implémentés dans l'intention de préparer votre Produit pour l'avenir.

Or, le storage est utilisé pour stocker les données.

@supertanuki supertanuki changed the title Désactivation Extension Google Chrome Addon Google Chrome disabled by Google Jan 3, 2022
@carbonalyser carbonalyser changed the title Addon Google Chrome disabled by Google Add-on Google Chrome disabled by Google Jan 3, 2022
@carbonalyser carbonalyser changed the title Add-on Google Chrome disabled by Google Add-on Google Chrome / Edge disabled by Google Jan 3, 2022
@bpresles
Copy link

Is it possible to still build the extension for Chrome and offer builds for side loading on GitHub ?

@AAABBBCCCAAAA
Copy link

Yes it is possible to offer some build from github but it requires users to disable addons verification. So it is for developpers/testers not for end users.

@bpresles
Copy link

bpresles commented Feb 9, 2022

@AAABBBCCCAAAA Indeed, and that's what I meant. I'd like to sideload the extension on Brave Browser as a developer.

@AAABBBCCCAAAA
Copy link

AAABBBCCCAAAA commented Mar 1, 2022

An example of autobuild with github actions (based on git tags eg tag '1.2.1') is avaliable here. Then the release is avaliable in "release" section.

For chrome you can still get carbonalyser with this method.

@bpresles since brave is chrome derivated you should success a similar way as chrome tutorial please let me know if it works for you.

@AAABBBCCCAAAA
Copy link

AAABBBCCCAAAA commented Mar 11, 2022

It is not an issue from Google but from your extension.
The issue comes from the fact that yes you use the storage https://developer.mozilla.org/fr/docs/Web/API/Web_Storage_API. But the classical one (eg cookie) so the permission storage is not needed. The storage permission is needed for webextension storage.

solution: remove the requested permission. or use webxt storage API

@hugolpz
Copy link

hugolpz commented Oct 6, 2022

Was this handled ? Desactivating the permission request is super easy for someone knowing the code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants