I'm getting a serious issue with uploading an app to Chrome Store. Keeps saying:
"An error occurred: Failed to process your item.
The 128x128 icon file is missing.".
I do have the 128x128 .png file in there. This is my .json file:
{
"name": "Radio Player UK",
"version": "1.0",
"manifest_version": 2,
"description": "Radio, but without the rubbish. The best radio stations are here. Choose from lots of great radio stations.",
"app":{
"urls": ["http://www.radioplayeruk.com"],
"launch":{
"web_url": "http://www.radioplayeruk.com/index.php"
}
},
"icons":{
"icons": {
"16": "logo16.png",
"128": "logo.png"
}
}
}
I know the file extensions are case sensitive and have adjusted this accordingly.
Can anybody shed some light on why I keep getting this message?
You have set the icons twice. According to the Google docs it should be just one icons key.
So, your manifest should be:
{
"name": "Radio Player UK",
"version": "1.0",
"manifest_version": 2,
"description": "Radio, but without the rubbish. The best radio stations are here. Choose from lots of great radio stations.",
"app":{
"urls": ["http://www.radioplayeruk.com"],
"launch":{
"web_url": "http://www.radioplayeruk.com/index.php"
}
},
"icons": {
"16": "logo16.png",
"128": "logo.png"
}
}
Related
First of all, I'm trying to use the new manifest 3, but there are no samples out there so it's difficult to understand how develop a chrome extension.
I'm trying to build a basic Hello world app, and i want to have an icon on the toolbar so when the user clicks it, a message "hello" shows up on the page.
This second part is easy as I already know how to inject the code, but the problem is that I cannot seem to see the app icon in my tool bar...
{
"manifest_version": 2,
"name": "My App Name",
"version": "1.0.0",
"description": "do something",
"short_name": "My App Name",
"permissions": ["activeTab", "declarativeContent", "storage", "<all_urls>"],
"content_scripts": [
{
"matches": ["<all_urls>"],
"css": ["src/bg/background.css"],
"js": ["src/bg/background.js", "js/jquery/jquery.min.js"]
}],
"browser_action":
{
"default_title": "My App Name",
"default_icon":
{
"16": "icons/icon16.png",
"32": "icons/icon32.png",
"48": "icons/icon48.png"
}
}
}
not sure what I need to add to see the icon
FYI I'm testing it locally ...i'm not sure if the local version acts differently from a packeged final version...
There has been a continuous extension rejection, even with icons, screenshots, descriptions all uploaded. Anybody has encountered the same recently?
Item has a blank description field, or missing icons or screenshots, and appears to be suspicious.
The manifest is like
{
"short_name": "My Tabs",
"name": "My Tabs",
"description": "This extension will help uses to quickly open often visited pages.",
"icons": {
"16": "tabs.png",
"48": "tabs.png",
"128": "tabs.png"
},
...
}
I'm trying to make a google chrome extension, but I'm having a problem. Please answer as basic as possible as I'm really bad at code. Whenever I upload something as a zip file, it says
"An error occurred: Failed to process your item. manifest.json:5:26:
unexpected char."
This is my code :
{
"name": "ROBLOX Character Asset ID",
"version": "1.9.0", // version
"manifest_version": 2,
"description": "This extension is for GFX artists who need their customer's character asset ID",
"browser_action": {
"default_icon": "icon.png"
},
"permissions": [
"alarms",
"background",
"debugger",
"notifications",
"cookies",
"https://www.roblox.com/"
],
"background": {
"scripts": ["bgWork.js", "jQuery-ver3.js"]
},
"icons": { "16": "icon.png",
"48": "icon.png",
"128": "icon.png" }
}
This has to do with the content in your scripts and when you load the extension it not being able to be processed as I loaded your manifest.json just fine (though with blank js files). So don't look towards your manifest.json, you must have an illegal character in your js file.
Here is my manifest.json file
{
"name":"Name",
"version": "1.0",
"description":"This is the description",
"manifest-version": 2
}
Chrome says
manifest file is missing or unreadable
The file is indeed a .json file, rather than a .txt file. What is wrong with my manifest.json file?
manifest file is missing or unreadable
You have manifest-json instead of manifest_json in the code snippet.
If you follow this tutorial then it lists the simple manifest.json for chrome extension. In below snippet replace name, description, icon, url with your own and give it a try.
{
"name": "Great App Name",
"description": "Pithy description (132 characters or less, no HTML)",
"version": "0.0.0.1",
"manifest_version": 2,
"icons": {
"128": "icon_128.png"
},
"app": {
"urls": [
"http://mysubdomain.example.com/"
],
"launch": {
"web_url": "http://mysubdomain.example.com/"
}
}
}
Let us know, if you have any difficulty in following the tutorial.
My CRX had the proper html page options.html in it, the manifest declares it properly (it shows up as a link on the chrome://extensions page) but when I click that link, Chrome gives the error:
This webpage is not available
The webpage at chrome-extension://invalid/ might be temporarily down or it may have moved permanently to a new web address.
It says "invalid" but the app runs perfectly well (all the content scripts run, the background created a database and saved to it). Why would it show as invalid? Why doesn't it have the extensions' id?
Here's the manifest:
{
"manifest_version": 2,
"name": "MyAPP",
"description": "My App",
"version": "0.0.0.32",
"minimum_chrome_version": "27",
"offline_enabled": true,
"options_page": "options.html",
"icons":
{
"16": "images/icon16.png",
"48": "images/icon48.png",
"128": "images/icon128.png"
},
"app":
{
"background":
{
"scripts":
[
"scripts/background.js"
]
}
},
"permissions":
[
"unlimitedStorage",
"fullscreen",
{
"fileSystem":
[
"write"
]
},
"background",
"<all_urls>",
"tabs"
]
}
Does it need to be declared in "web_accessible_resources"? Any idea what's wrong?
Update
Adding to "web_accessible_resources" does not fix the issue. I added everything on that page too.
update 2
It looks like it might be a Chrome bug for packaged apps. When I remove the "app" section in the manifest, it works! This is a bug since the Chrome app documentation states that apps can have options pages: https://developer.chrome.com/apps/options.html
Options pages are only supported for extensions, you have indeed discovered a documentation bug (I've filed issue 255079).