How to change offeredby/developer information in chrome extension? [duplicate] - google-chrome-extension

This question already has an answer here:
Change "from [name]"/"offered by [name]" in a Chrome extension's Webstore listing
(1 answer)
Closed 6 years ago.
I just created a chrome extension, I wanted to know how to change the "offered by" and "developer" information. Check the screenshot below I have underlined the information I am referring to.
I found this one old SO thread - How to specify author of Extension in Manifest file.
And I have tried something like this
{
"browser_action": {
"default_icon": "icons/logo.png",
"default_popup": "popup.html",
"default_title": "Timezone Convertor"
},
"description": "The all in one, timezone plugin you had been waiting for!",
"manifest_version": 2,
"name": "Timezone Convertor",
"permissions": [ "storage", "tabs", "http://*/*", "https://*/*" ],
"update_url": "https://clients2.google.com/service/update2/crx",
"version": "1.5",
"authors": [{"name": "Ali Rizvi", "email": "example#gmail.com"}, {"name": "Yasser R Shaikh", "email": "example#gmail.com"}]
}
But it doesnt work. Google's manifest documentation also doesnt have much information about it.

Those were in manifests v1 (Also explained here). For v2 and v3 extensions they are changed in the Chrome Web Store Developer Dashboard.
Instructions updated 2023:
Visit https://chrome.google.com/webstore/devconsole and login
Your account settings can be accessed by clicking the "Account" button in the upper left corner

Related

Is my manifest.json fully compliant to Manifest v3?

Recently, I have been working on a Chrome plug-in with co-workers and I must admit that I do not have much experience with Chrome extensions. We already published one version. Now, I just submitted a second release.
I am aware that following the Manifest v3 rules helps to speed up the review process. Also, I believe we are following the rules and we really need to have a fast review process.
However, I keep seeing this message:
It points to the official documentation on the topic: Migrating to Manifest v3 which includes a check-list.
This message makes me suspicious that I might have made some mistakes.
Hence, I would like to show my manifest.json:
{
"name": "My plug-in name",
"description": "Auto-fill some specific forms",
"version": "0.0.22",
"manifest_version": 3,
"action": {
"default_popup": "src/importer/popup.html",
"default_icon": "src/importer/img/company-logo.png"
},
"icons": {
"128": "src/importer/img/company-icon.png"
},
"permissions": ["activeTab", "scripting"],
"background": {
"service_worker": "src/importer/background.js"
},
"content_scripts": [
{ "js": ["src/importer/content-script.js"],
"matches": ["https://*.onewebsite.com/*"] }
]
}
It seems to be correct.
Am I missing something? Is the extension Manifest V3 compliant?
Should I ignore Chrome Web Store alert?

My extension shows up in Chrome, how can I stop this?

So I am learning how to make chrome extensions. What I am trying to do is only useful at one specific website, so I hoped that I can somehow "hide" the extension when I am not at this website. It seems like Chrome Remote Desktop or Google docs extensions also don't show up next to the adress bar. How can I achieve the same with my extension? Here is my manifest:
{
"name": "Test",
"description" : "I am learning",
"version": "1",
"manifest_version": 2,
"content_scripts": [
{
"matches": ["*://www.google.com/*"],
"js": ["myscript.js"]
}
]
}

Avoid creation of browser action in Chrome extension [duplicate]

This question already has answers here:
Can I hide my extension's icon by default?
(4 answers)
Closed 5 years ago.
I am creating a chrome extension. When the extension is added to chrome, then icon next to address bar is added also (browser action). My extension does not need any browser action. So, how can I avoid creation of this icon?
Edit: My manifest file:
{
"background": {
"persistent": true,
"scripts": [ "background.js" ]
},
"description": "This extension ...",
"manifest_version": 2,
"name": "Something",
"permissions": [ "webRequest", "webRequestBlocking", "http://*/*",
"https://*/*" ],
"version": "1",
"icons": {
"128": "msdos.png"
}
If your browser extension does not need browser_action, you can simply remove it from your manifest.json see: from https://developer.chrome.com/extensions/browserAction.
It will remove the icon next to the bar address.
More details about manifest.json: https://developer.chrome.com/extensions/manifest
If it does not work, do you mind to post your manifest.json
EDIT: As wOxxOm mentionned, since January 2016, Chrome shows all the icons of the web extension. So there is no way to hide it (except on the older version of Chrome).

Why does my chrome extension ask for history permissions?

In my manifest.json file, I have nothing explicitly listed for reading a user's history, however, this warning comes up when you try to install the extension.
Here is my manifest file:
{
"manifest_version": 2,
"name": "QueueTube for YouTube!",
"short_name": "QueueTube",
"description": "Search YouTube without stopping the video, and make your own playlists!",
"version": "1.5",
"author": "Dara Javaherian",
"permissions": ["tabs", "*://*.youtube.com/*"],
"background": {
"persistent":true,
"scripts": [
"bg/socket.io.js",
"bg/background.js"
]
},
"icons": {
"128": "icons/youtube-128.png"
},
"browser_action": {
"default_icon": "icons/icon.png",
"default_popup": "popup/popup.html"
},
"web_accessible_resources": [
"spinner.gif"
],
"content_scripts" : [{
"matches" :
["https://www.youtube.com/*",
"http://www.youtube.com/*"],
"js" : [
"js/jquery.js",
"js/inject.js"],
"css" : ["styles/styles.css"]
}]
}
Does anyone know why this permission is showing up?
This is the standard warning for the "tabs" permission.
It allows you to query, and be notified of changes, to URLs of all tabs. This allows you to spy on the user's history in real time - even if you don't have access to the browser's own history log.
Note that "tabs" permission is not required in most cases. Providing access to URLs is basically the only reason to include it. You can use most of the tabs API without it, and can get access to current tab without warning using the "activeTab" permission.
Warnings and their triggers
It can be surprising when adding a permission such as "tabs" results
in the seemingly unrelated warning that the extension can access your
browsing activity. The reason for the warning is that although the
chrome.tabs API might be used only to open new tabs, it can also be
used to see the URL that's associated with every newly opened tab
(using their tabs.Tab objects)
Source: https://developer.chrome.com/extensions/permission_warnings

Chrome extension to add event in google calendar('background_page' requires manifest version of 1 or lower.)

I am a beginner for the chrome extension. I have found a demo to add event to google calendar, I have solved some problems for this demo, but it doesn't word yet... Now I have a problem and I don't know how to fix it
L'installation de cette extension a généré des avertissements :
'background_page' requires manifest version of 1 or lower.
manifest.json :
{
"name": "Add Event to Google Calendar",
"version": "1.4.1",
"manifest_version": 2,
"description": "A user can add events to Google Calendar by simply highlighting dates that appear on a webpage.",
"icons": { "48": "calendar48.png", "128": "calendar128.png" },
"background_page": "background.html",
"permissions": [
"tabs", "http://*/*", "https://*/*", "http://www.google.com/"
],
"content_scripts": [
{
"matches": ["<all_urls>"],
"js": ["jquery.js", "date.js", "content_script.js"]
}
]
}
background.html
I can not post background.html here, because it is too long...please download this here Add-to-Calendar-Chrome-Extension
Thank you very much!
Google are changing the manifest version requirements for Chrome as detailed in this link.
The warning is only visible with "Developer mode" active. They don't affect end-user. You can also consider using minimum_chrome_version to block users with older browsers from downloading your latest update. Downgrade to manifest_version: 1, wait for everyone to download downgraded version and, yet again, push update with manifest_version: 2 this time adding minimum_chrome_version: 18.
The background_page property has been replaced with a background. That property contains scripts, either a page or property. Details are available in the Event Pages documentation.
You may check this forum.

Resources