google-chromegoogle-chrome-extensionchrome-web-store

Unable to publish the chrome extension to public

I am trying to publish an chrome extension with following manifest file.

Every time I publish my app it is getting rejected.

Updated

{
  "manifest_version": 2,
  "name": "Aiwozo",
  "description": "AI Work Zone Web Automation Extension is an component developed for browser interaction to implement automation on web applications.",
  "version": "1.1",
  "icons": {
    "16":"static/activate_icons/Aiwozo16.png",
    "32":"static/activate_icons/Aiwozo32.png",
    "64": "static/activate_icons/Aiwozo64.png",
    "128":"static/activate_icons/Aiwozo128.png"
  },
  "background":{
    "scripts":["background.js"]
  },
  "browser_action": {
    "default_icon": {
      "16":"static/activate_icons/Aiwozo16.png",
      "32":"static/activate_icons/Aiwozo32.png",
      "64": "static/activate_icons/Aiwozo64.png",
      "128":"static/activate_icons/Aiwozo128.png"
    },
    "default_title": "Artificial Intelligence Work Zone"
  },
  "permissions": ["nativeMessaging", "<all_urls>"],
  "web_accessible_resources": [ "css/general.css", "static/activate_icons/AIwozo16.png", "static/activate_icons/AIwozo32.png", "static/activate_icons/AIwozo64.png", "static/activate_icons/AIwozo128.png", "static/deactivate_icons/AIwozo16.png", "static/deactivate_icons/AIwozo32.png", "static/deactivate_icons/AIwozo64.png", "static/deactivate_icons/AIwozo128.png"]
}
Solution

  • It seems that Google now requires you, the developer, to provide an explanation of what your extension does (according to Single Purpose Policy) and an explanation of why specific permissions are needed.

    This is on the Privacy tab of the "new" Developer Dashboard's listing: Privacy UI

    Until those fields are filled out, Web Store blocks publishing of new extensions and updated versions of existing extensions.

    On the plus side: it doesn't mean you have failed a review yet. So with good explanations you may be able to get this published. In your particualr case though, those are broad permissions + arbitrary code execution. It will be tough.