From the "Pre-installed Apps and Extensions" management in "Google Apps Admin console / Device management / Chrome / User settings / Apps and Extensions", the list of suggestions should only show Chrome extensions and Chrome applications.
Currently, it also shows "Google Drive Add-ons" and "Google Apps Marketplace applications", so, it's confusing for administrators because they don't know which one to select for automatic installation. Moreover, selecting a "Google Drive Add-on" or a "Google Apps Marketplace application" from "Pre-installed Apps and Extensions" has no effect.
For examples, you will find "Table of contents" (that is a Google Drive Add-on) and "LumDocs" (where you have a Chrome Application and a Google Apps Marketplace application).
I was able to reproduce it so it's either a bug or expected behavior now that end users can install Google Apps Marketplace apps themselves.
This type of report should be submitted to the Google for Work team via phone or support.google.com/a > Contact Us. They'll be able to confirm the behavior and provide more details.
Related
I received an email from Google saying that my webapp (www.Photopea.com) is unpublished from the Google Workspace Marketplace, because I did not provide a privacy policy URL.
According to their web, Photopea has been installed 1.352 million times and many people are complaining to me that they can not find it in the marketplace.
When I go to "Google Console" - "Photopea" - "APIs and services" - "Google Workspace Marketplace SDK" - "Store Listing", I see "Unpublished (Rejected)". The "PUBLISH" button is gray and says "Currently disabled.".
Is there a way to publish it again?
*** I don't know what "Google Workspace" is, I am not aware of ever using it. My only goal is to let people double-click PSD files in their Google Drive to edit them in Photopea. It worked perfectly since 2016 until now.
I followed all recommended steps for setting up a PWA which can be installed on the user device, following the guideline here: Installable PWAs (MDN):
To make the website installable, it needs the following things in place:
- A web manifest, with the correct fields filled in
- The web site to be served from a secure (HTTPS) domain
- An icon to represent the app on the device
- A service worker registered, to allow the app to work offline (this is required only by Chrome for Android currently)
Still, I don't see the browser-default installation prompt.
How do I find out, why my PWA cannot be installed?
I recommend using Lighthouse, which is an excellent tool for auditing your web app with respect to different categories, including PWA properties. It is also available in Google Chrome in the developer tools (Ctrl-Shift-I / Cmd-Opt-I and select tab Lighthouse).
How do I trigger a PWA audit in Lighthouse (in Google Chrome)?
Choose the category Progressive Web App and then click on Generate report.
Example report
In the example below, you can see that there are some issues present. But the reason, why you don't see the installation prompt is the service worker. Apparently, it isn't registered as expected.
Web app manifest or service worker do not meet the installability requirements
As a developer, 4 weeks back I have unpublished GSuite marketplace app(Spreadsheet addon) through Chrome web store developer dashboard. On Chrome web store dashboard status is updated. But it is still visibile in GSuite marketplace search listing (don't know why). Probably this is Google bug that even after marking unpublish it is visible in public marketplace.
Not getting much quick support for requests raised to Google to delete this app from marketplace.
Query: I want this app to be deleted from GSuite marketplace. My question is if I mark my app as "unlisted" through chrome web store developer dashboard, then will it remove GSuite marketplace listing? Can anyone please confirm.
From this page:
How can I manage and uninstall the applications I have installed from the Marketplace?
By clicking on "Manage Apps" on the top right of the Marketplace,
users can view the applications they have installed. From there they
can rate, review and uninstall applications (unless admin-installed).
There's also Delete an app in Gsuite Marketplace which states the same steps.
How can I see error messages when running a Chrome packaged app? I've been running the app in the browser and using DevTools but this technique has it's limitations.
If you need to inspect app windows, you can reach them at chrome://inspect/#apps
Or, as Daniel mentions, use the Developer Tool app.
General Chrome Debugging
By opening
chrome://inspect/#apps
you may debug all Apps and Extensions.
You may also like the official Google Chrome Apps & Extensions Developer Tool
Debugging Chrome Extensions
As described in the chrome developer Tutorial you can activate the developer mode within the settings. Afterwards an inspect popup option is avaialbe when you right-click an app-icon.
Couple days ago Google Chrome automatically updated from version 31.* to version 32.0.1700.76 m. After that happened it does not show in DevTools network traffic request/responses of "application/msbin1" type anymore. These requests are visible in all other browsers' dev tools (FireFox, IE) and in Fiddler, but not in Chrome. Also Chrome's popup menu in this version is very glitchy.
I don't see the way to downgrade Chrome to previous version. Please help I don't want to uninstall Chrome.
Network traffic does not even show resources (XAP file) a page loads.
Example:
http://www.microsoft.com/silverlight/pixel-shader/demo/
This page loads file SilverlightShaderApp.xap, however dev tools of new Chrome's version never shows it in network tab.
I posted the question here, because it's developers question, not just chrome users.
I reported this issue on google chrome forum as well: here.
Possibly related bugs:
Issue 173844: Developer tools (Network section) don't show response of requests from flash applications
Issue 335502: XMLHttpRequests from Silverlight is not visible in devtools network tab
To avoid the bug, you could downgrade to Chrome 31. A fully offline installer can be downloaded from http://download.oldapps.com/Chrome/31.0.1650.39_chrome_installer.exe.
If you downgrade Chrome, don't forget to disable auto-update. Also, "star" the relevant issues on Chromium's issue tracker so you'll receive email notifications for progress updates. When the issue is fixed, enable auto-update again.
Often, starting a new version of Chrome renders a profile unusable for older Chrome versions ("Your profile can not be used because it is from a newer version of Google Chrome."). When you see such message on start-up, either delete your old profile (don't forget to make a back-up!) (you can also try to delete some files, according to various users, deleting "Web Data" and "Web Data-journal" is sufficient), or launch Chrome with a new profile directory (--user-data-dir=path\to\profile-dir).
For more information on user profiles, see http://www.chromium.org/user-experience/user-data-directory.