After following the directions at https://developers.google.com/gmail/api/quickstart/nodejs I have found that I get an error in my console that looks as follows
This tells me that I need to be including some redirect_uri to the console, but the tutorial appears to give no counsel on what I should be doing to get there so that information makes it into the json file downloaded?
The first download for some reason didn't include the redirect_uris. I redownloaded the file and now it works
Related
I bought an app template to mess around with, and when I'm trying to login in this case via Facebook it's calling the API I set up according to the guide.
It's calling
http://IP/mobileapp_api/api/registerUser
Now it's giving me the 404 error because the API folder does not exist, but when looking through the documentation and double-checking everything I also notice that he also doesn't have an API folder, but he's able to get a response just fine.
How is this possible?
Link for the video documentation https://www.youtube.com/watch?v=G1OTEbnD6CM&t=324s
I've tried to reach out to the developer, but with the current covid situation in his home country, I doubt I'll get a reply anytime soon, hence why I've come here.
Not sure why, but uploading the files via CPanel and not Filezilla somehow made it all work.
We are getting error "Invalid credentials for xxxxxxxxxxxx" when I try reverse geocode on Here Maps API.
Even with demo app_id & app_code gives error.
Anyone known a support contact from Here Maps to check out what's going on?
[Edited]
The example request to produce error is:
https://reverse.geocoder.cit.api.here.com/6.2/reversegeocode.json?app_id=DemoAppId01082013GAL&app_code=AJKnXv84fjrb0KIHawS0Tg&mode=retrieveAddresses&prox=41.8842,-87.6388,250
Working examples using the demo credentials can be found on developer.here.com
I guess the issue here is that you are attempting to use the Demo Credentials outside of the examples instead of your own user credentials, and text of the error message is probably deliberately misleading. Try using your own app_id and app_code instead.
You could also download the Geocoder Postman Collection to generate proper REST requests rather than relying on a browser.
You could check if the following link works for you.
https://reverse.geocoder.cit.api.here.com/6.2/reversegeocode.json?prox=41.8839%2C-87.6389%2C250&mode=retrieveAddresses&maxresults=1&gen=8&app_id=XXXXXXXXX&app_code=XXXXXXXXX - it works for me.
I am in the process of switching my site analytics from GA to Piwik and would like to incorporate all the historic data that I can. I have already concatenated the full trail of apache log files I have in my possession. However, what I do next is not at all clear to me and the Piwik documentation does not help. It says something along the lines of
python /path/to/piwik/misc/log-analytics/import_logs.py --url=http://analytics.example.com access.log
I have my concatenated log file, all.logs, in the log-analytics folder. I would have thought that I just need to issue
python /path/to/piwik/misc/log-analytics/import_logs.py all.logs
but that throws up an error message. When I provide the URL to the site in question too I get an error saying that it gets back an HTML document (naturally) which it does not like.
I'd be most grateful to anyone who might be able to put me on the right track here.
I think --url=http://analytics.example.com let's you set the URL of Piwik, not your website.
I have been facing the same problem from Google Cloud API Console for over a day now.
I tried to add a new redirect_uri for an old project to use it in my webapp but it gives me "redirect_uri mismatch" error. Old redirect uri still work as they used to.
I even tried creating a fresh project from the start and then registered a new application. This now gives me "invalid_client" error via google oauth.
If the old redirect_uri redirect as they should, then why doesn't the new one? Does something else need to be done when addding a new redirect uri?
Your errors are all self explanatory, so you simply need to carefully retrace your steps and check typing, that you are using the correct client id with the appropriate urls.
it gives me "redirect_uri mismatch" error.
The uri must match character for character. eg. watch for http(s) and trailing slash
This now gives me "invalid_client" error via google oauth.
Either you forgot to enable the API or you haven't correctly installed the new client ID in your app.
Does something else need to be done when adding a new redirect uri?
NO. Just make sure it exactly matches the URL you are passing.
It's sometimes easier to switch back to the old API Console. There is a faint grey link at the bottom of the screen in the new cloud console.
This looks like a bug.
See Newly created Oauth Client IDs don't work for what seems like a successful workaround.
I'm trying to setup the config.php with my values but I get this fatal error:
Fatal error: Uncaught exception 'Google_AuthException' with message 'Error fetching OAuth2 access token, message: 'invalid_grant'.
I entered the client ID, secret, simple API key, location and sqlite database as the documentation says here:
https://developers.google.com/glass/quickstart/php
Any idea of what I'm doing wrong?
Thanks in advance!
This happens when the URL where you're hosting your Glassware is not listed as a valid OAuth 2.0 redirect URI on the API console. Follow these steps to resolve it.
First, determine your OAuth 2.0 redirect URI. This is where traffic goes at the end of the OAuth dance. The correct value depends on where you're running the php quick start. If you're running it on a local web server, it's likely to be http://localhost/mirror-quickstart-php/oauth2callback.php. If you're running it on example.com, it might be https://example.com/oauth2callback.php.
Go to the API console. This link will lead you to the right panel (services), but double check that you're on the correct project.
Scrolling down you should see a section of the page that looks like this: . Click on 'Edit Settings...'.
This triggers a pop-up where you can enter your OAuth redirect URIs. Add your redirect URI to the top text area. Make sure to put each URI on its own line.
Reload the page for the PHP Quick Start and everything should work.
If you're still having an issue, please share the full error message on the page and the value you have for the base url in config.php.
If you're getting the invalid_grant error from Google : Instead of using the client ID from google developer console as your value for client ID in the code, try using the email address value from developer console. This is actually what they expect. So, to confirm - the value for Client ID should be the value from developer console ending #developer.gserviceaccount.com
Had similar problem in Windows PS dotnet environment when trying to connect to DialogFlow Google Cloud Project recently and it appeared to be intermittent fault but it turned out to be global $env:GOOGLE_APPLICATION_CREDENTIALS in windows PowerShell was pointing to a key file set when first setup access to GCloud days before and since regenereated keys in GCP Console
After generating new key file and setting it with new generated key file using $env:GOOGLE_APPLICATION_CREDENTIALS="[Path_To_JSON_Key_File]" the problem went away but fix only lasted as long as the window was open, then after a while ran $env:GOOGLE_APPLICATION_CREDENTIALS on a newly opened PS window and noticed it was still pointing to the old key file!
setting the system environment variable GOOGLE_APPLICATION_CREDENTIALS to the value of [Path_To_JSON_New_Key_File] fixed it, all newly opened PS windows had the correct key file and authenticated correctly using Service Account and .Net Google Cloud API calls worked after that