I am attempting an Exchange to Gmail conversion. First steps are to open developer and then create a service project. I get a Google Cloud Platform service has been disabled error right away. The Cloud Platform is enabled on my system, and Google support has verified. Does anyone have any thoughts?
I got the same error in Firefox and tried it on Chrome. It got me to the sign up and give payment info page, which is farther than I got on Firefox.
Related
I am currently trying to verify my Google OAuth App, and for the demo video I need to show the App Name and Client ID on the OAuth Client. However, I am only able to get the domain.com to show up. I have configured my App Name in Google Cloud Console. Does anyone know how to fix this?
I have resolved this issue and verified my app! Turns out, you only need to show your App name and client id in some way in the Demo video and configure it in Google Cloud Console.
Anyone else having trouble adding the DoubleClick Bid Manager API to his/her Google Developer Console?
It's always showing "Failed to load" to me.
All other APIs can be added normally (especially the other Advertising APIs). So I am wondering what's wrong with the DoubleClick Bid Manager API.
Am seeing the same issue when trying to enable the DBM API for a cloud console project.
I have previously enabled the DBM API for a different cloud console project registered under an email address which is also authorised to access DBM.
I've just disabled and then successfully enabled the DBM API for this project and it worked fine. No 'failed to load' error. phew.
My suspicion based on this is that you can only enable the DBM API for projects registered under an email address which is authorised to access DBM.
I've sent feedback to Google on this and based on previous experience I don't expect to hear back anytime soon...
Good luck!
Ok, it just has come down to missing permissions for DBM. It took a long while for the DBM-"owner/admin" (here: agency) to figure out what permissions are missing.
I've created a Google Hangout extension app, tested it works privately etc and now I'm trying to publish it. I have followed the instructions here:
https://developers.google.com/+/hangouts/publishing
I've filled in the forms correctly, created the O-Auth client ID, filled out the consent form etc. When I tick the Make this application public tickbox and try to save, a server error message pops up along the lines of:
Server Error
Whoops! Our bad.
Please try again. If the problem persists, please let us know using the "Send feedback" link below. Thanks!
Tracking Number: XXXXXXXXXXXXXXXXXXXXXXXXX
[Send feedback]
I've checked the Chrome console - the request gets a 500 error and in the JSON response I can see:
{"message":"Developer not registered with CWS."}
I have paid the $5 one-off developer fee on the Chrome Web Store and I am the Hangout project owner. I'm not sure what I'm missing here. I need to get this published in the next 24 hours...
Any useful insights? Is there any official support forum for Google+ platform developers?
UPDATE
I was using a Google Apps account before so I've paid the developer fee on a personal account to verify me on CWS, made this account owner of the Hangout project and I still get the same message response.
I believe then that it's basically just broken. Thanks Google.
I am currently getting "You do not have access to the following domain:" error in Google developer console when attempting to use the "Configure webhook notifications" button for Google API push notifications despite the fact that the very same site / domain is listed as mine in Webmaster Tools and I have access to all of the services there. Any ideas?
I guess you also registered "https://yourdomain.com" in google webmaster tools, because the webhooks require https.
The very same thing is happening to me since about one week. I can add all kinds of domains to the push notification list, even "www.chatgrape.com" but not "chatgrape.com".
I described the problem in the Google Product Forums in detail but nobody was able to help me yet: https://productforums.google.com/forum/#!category-topic/apps/general-discussion/Numad1TlCJ8
Yes I actually found that it would only work if I had the https version of the URL registered in Webmaster tools. However, the reason that I can use an https version is that there are some SSL services included with a free CloudFlare account. This does not include using a signed certificate installed on your server. To use Google push, you need to have a certificate installed and it cannot be self signed.
We are in the process of creating our new app for v2 of the apps marketplace. Recently we have run into quite a major issue and we are having a lot of trouble resolving it.
We are testing the workflow where a domain admin installs via the chrome webstore listing. The actual installation of the app works, insofar as the app is installed on the domain and the scopes appear to be granted when looking at the "Manage API client access" section in the domain admin panel (http://i.stack.imgur.com/a63nv.png).
However, when we attempt to use the service account to get calendar or contacts info, we are getting "Requested client not authorized" errors.
{
"error" : "access_denied",
"error_description" : "Requested client not authorized."
}
However, if we manually add our service account + scopes to the domain in question, then accessing the data programmatically works fine (http://i.stack.imgur.com/g6pRg.png).
So, clearly we are missing something here, with how installing a marketplace app via the chrome web store is supposed to work.
Other things to note:
Chrome webstore listing is marked as unlisted.
New marketplace app is not approved (obviously) as the tester received this specific error when attempting to install the marketplace app.
We got it figured out. The issue was in how we declared our contacts API scope in the marketplace sdk setup screen.
In the marketplace setup screen, we declared using the contacts scope without a trailing slash ("https://www.google.com/m8/feeds").
However in our app, we were sending oauth requests for the calendar feed with the slash at the end. ("https://www.google.com/m8/feeds/"). This mismatch caused the whole request to fail with the error message above.
If anyone runs into this and is baffled at why their service account requests are failing, make sure you are consistent with your slashes at the end!
I would suggest to Google that you should update the marketplace sdk screen to also be consistent and reject scopes that do not have a slash at the end. That would have saved us days of frustration.