I created a Chrome Packaged App and already published it. The status is already published, but when I go to the Chrome Webstore and search for my app, I can't see it. What am I missing?
Some points to check on your published App:
Your app or extension will take few minutes to several hours appear in search result.
Republish your app
App indexing to web store takes time/ couple of days
if all else fails, file a report to Chromium Support
Here is the Google Group regarding Chromium for additional information and you can post the error that you experience there.
Related
I have currently a simple Hello World Google App Script following Google Documentation
I published it, giving access to anyone on the internet (including anonymous users) and then get both a xxx/dev and xxx/exec urls (latter for "published versions" usage, latter for work in progress usage).
None of those URL are currently working when I call it in my Browser (or through a cURL command) :
Any idea on what could go wrong ?
Note : I already published some Google App Scripts in the past and they are still working today. It is as if my "new" google app scripts was not getting published.
This could be because you are logged into multiple Google accounts. Try:
deleting the "u/0" from the URL
signing out of all of your Google accounts, and back into just one
trying the /exec in an "incognito" window
I am making a chrome extension, and for the purposes of my Chrome Extension, I am wanting users to be able to sign in to their Google account so they can send information to a server. I have been reading about user authentication and whatnot from the Google documents, but this is for apps that are being published into the store, and mine is in development. This is brand new territory for me, and I am lost. I feel like there's something that I must be missing, but I don't know how to get started.
Thanks.
Check this documentation about the quick way of loading up your working directory for testing. Extensions that you download from the Chrome Web Store are packaged up as .crx files, which is great for distribution, but not so great for development.
I searched all over and couldn't find my specific issue here so please excuse me if my search-fu has failed me.
My issue:
I am currently trying to create a kiosk app for my company's chromeboxes. I have the application packaged and published privately on the chrome web store. I get the app to load but once I launch the kiosk app and enter in my company's url I am presented with, "Unsupported Chrome App Origin Detected". The only thing I can find so far about this is to run the flag --disable-web-security. I can only find examples for Windows/Mac/Linux plus that isn't secure. Am I missing something in my Default.cr or manifest.json files? Is this even possible? This is on a vanilla chromebox that isn't part of a Google Apps domain. Do I need to have it added to a Google Apps for Work domain to get this to work? Any help would be appreciated.
Please add your generated chrome extension app id to storefront web.config file. Please have a look at http://docs.citrix.com/en-us/receiver/chrome/1-7/receiver-chrome-deploy.html point 8 at the end on how to do it.
Also please use 1.7 as it supports better Kiosk mode integration.
Google chrome extension:
I created a Google chrome extension and published it on Google Chrome Store,
but I can't find it while searching on it.
There are a couple steps you can try to diagnose the issue
Try to refine search by extensions.
Try searching your google username.
If neither of these work your extension may not be public and published to everyone (not just testers). Please refer to this guide on how to publish your extension to the world.
https://developer.chrome.com/webstore/publish#world
An issue I had was that I had uploaded the .zip but never hit publish. Make sure in your developer dashboard it doesn't say draft version where it should say published version.
In the newly published version of my app that is using Google Maps Android API V2, I've implemented all the things suggested by the developer guides to ensure the user has GooglePlayServices installed, and it has been working well on all the devices I own and the several hundred people that have updated to the new version of the app so far.
Today I received a bug report via acra with a strange error. This is happening on the following line of code, after setupMapIfNeeded() has completed:
mMap.setMyLocationEnabled(true);
Logcat reports:
W/GooglePlayServicesUtil(10401): Google Play Store is missing.
Shouldn't the call to GooglePlayServicesUtil.isGooglePlayServicesAvailable() also ensure that the Play Store is installed? That seems like a huge oversight on Google's part if it doesn't.
Any help is appreciated.
In case someone came here by accident or was just wondering why it was not working...
This could happen when user had old Android Market installed, which was replaced by Google Play Store.
Here is relevant issue: http://code.google.com/p/gmaps-api-issues/issues/detail?id=4862 (fixed in february update).