I am getting this error when I try to create a project in console.developers.google.com. I have 8 more projects left in my quota. I have tried different names and different project IDs. When I hit the "retry" button it shows the error after some time again.
UPDATE [Oct 9, 2017]: It looks like Google fixed the issue, since I was able to create a new project today.
I went ahead and attempted to create a new project in the Google API, and received the same error. This has occurred before with the Google API and is considered a temporary issue, often being fixed the same day. But if I remember correctly they have had it down longer in the past.
So the good news is, it's not something that is on your end, the bad news is, it's on Google's end.
If your google account is a Google Apps account (Google Suite, Google Apps, Gsuite, or whatever the Marketing folks are calling it these days), then you need to enable "Google Developers Console".
Login as an admin to admin.google.com
Go to Apps > Additional Google services
Find the "Google Developers Console" line item and set to "ON for everyone" (or whatever).
That should do it.
Related
Summary: when other users find my Google Slides add-on in the Google Workspace Marketplace and try to install it, they hit a screen saying they need to request access. When they click the button to request access, it sends me (the script owner) a request to share the script file, which should not be necessary. How do I fix this?
I have a Google Slides add-on which has been publicly listed in the marketplace for years (predating the rebranding to Google Workspace). I last updated it in 2019, and recently I wanted to publish another update.
Since this is an old project, I had to go through migrating the add-on to its own standard GCP project and then getting OAuth verification for the (not very sensitive) scopes it needed. This is all done now. All throughout, the add-on has continued being listed in the Google Workspace Marketplace, even though no new users could use it.
All that is done, but other users are still unable to install the add-on from the Marketplace. Now, when they try to do so, they'll get a small new window pop up saying they need to request access - seemingly to the script file of the add-on. This shouldn't be necessary. Does anybody know why it's happening?
If you want to try yourself, the add-on is called Superuser Tools, and the Marketplace listing is here.
I can't for the life of me find the unpublish/publish switch on the new Google Play developer site. It used to be in pricing but I just cannot find it.
I currently have an app unpublished and need to change it back to published but can't find the option.
I cannot switch back to the classic version as I get a 403 error code.
You can just transfer it to another Google Play Developer account.
Follow this tutorial post to do that: Android Apps Transfer to Different Developer Account
Finally found it!
Click on the app in question, then choose 'Setup' then 'Advanced settings' and it is in there.
We have an application listed in the old google apps marketplace and when our customers try to go to our app using the 'More' menu in google (nine dots icon), then they now get a 400 Bad Request during the redirection process. This was working until recently and nothing has changed on our end.
I take it that going to an app from more menu is still suppose to work for apps on the old google apps marketplace. Can some google person take a look and see why it is not working any more?
When I click on our application in the more menu we are taken to an url like this (I've changes some of the actual values in the url below to post here for security reasons) and get 400 Bad Request:
https://apis.google.com/additnow/l?applicationid=xxx&__ls=ogb&__lu=https%3A%2F%2Fusqa.blah.us%2Fblah-usqa%2Fpages%2FgoogleAppsMarketplace%2FgoogleAppsNavLink.html%3Ffrom%3Dgoogle%26domain%3Dblahblah.com&token=yyy
Regards,
LT
This issue should be fixed now. Let us know on this forum if this is still an issue.
Apoorv - Product Manager Google Apps marketplace.
Ok, so without much notification given, adding market place listings to your vendor profile is no longer possible. The 'create new listing' button is greyed out.
I need to make changes to an existing marketplace listing but that gives errors. We are forced into the new SDK.
So I went ahead and enabled the apps market SDK, filled out all details including images of all sizes, add a COB extension for the contextual gadget and saved the whole thing.
A minute later I return to make a modification and dang... error: "We are looking into this.".
#Google: HELP !
UPDATE : I can reliably reproduce the error as explained here.
Enable Google Apps Marketplace SDK in your project
click on the gear icon, you will be directed to the old API Console
Fill out all details
Add a COB extension (Contextual gadget)
Save everything
Close the API console
Go back to your cloud console -> Google Apps Marketplace SDK
Click on the gear icon again
ERROR
Tested with several google accounts on different computeres and multiple projects on the cloud console.
#jonathanberi could we have a status on this issue, please? We are experiencing the exact same issue and we are unable to publish our app (which is ready) because of this bug. We have tried both creating a new Google Apps console project from scratch as well as modifying a draft of a yet to be published page with the same result. Is any information that we could provide to help?
You must fill out parameter name and a paramter value or your cloud console will return errors and you will not be able to recover from this.
Ouch, that were 3 useless weeks....
When installing a Google Marketplace App, the flow usually ends with the admin in the app's settings on Google with the option to sign in now. Is there a way to end with the user actually using the app (i.e. not having to click the link to sign in to start using the app)? Could the user just be sent to the app on the optional setup without returning to the app settings page on Google without that causing other problems?
Some of the documentation says:
We strongly recommend that the administrator be directed through a short, linear series of actions and returned to Google quickly so additional users can start using the application.
I tried testing this out, but it seems like there's some lag between installing and the app showing up in the "more" drop down for Google (I tried installing another app and did end up on the final page but the app still didn't show up in another account. It's been a few hours and it still isn't there) so it's hard to tell if it's just slow or not actually installed on other users' accounts.
Sorry the last section was misleading. This is not a question about the link not showing up immediately.
The new experience for Google Apps Marketplace lets you land the user in the app instead of the admin console. There's now a popup for the app to request permissions and to agree to terms and then the user ends up in the app. One-step installation. Good work Google.