I've created a project in Google Developer Console to access Google Fit API but when I wanted to add scope in the OAuth consent screen, no scopes from the Fitness API are available even though the API has been enabled.
Fitness API overview
OAuth consent screen
Could anyone let me know what might go wrong here? Is the API still available?
Thanks in advance,
Kemal
Related
I have received a Google Map API Key and it seems to work just fine. Looking on the credential page of the GCP I see there are some alternate methods that I don't see documented anywhere. I have attached a screen shot of the specific page I am referring to, but I was wondering if anyone could give me insight on how to use these methods (OAuth and Service Accounts) or where I might find more documentation.
Thank you.
OAuth 2.0 Client IDs and Service Accounts may not be needed for Google Maps APIs. You will only need API keys to authenticate Google Maps APIs requests as explained here, so I think you can ignore the others.
But to give you an insights, as per the documentation here:
OAuths 2.0 Client IDs are used to allow your apps to access other Google Cloud products on behalf of the user.
Service Accounts are accounts that used by an app to make authorized API calls for other Google Cloud products. You can learn more here: https://cloud.google.com/iam/docs/service-accounts
I am regular user of Mindmup on google drive , a top rated mind mapping tool on Google drive marketplace.
I have an 2016 Mindmup which I am not able to open. Mindmup said they can help if google can provide “Drive Realtime API data” associated with the old file.
Google has a note that claims that read only access should continue, which is not true. And the link to how to "export realtime API data" is broken.
Answer:
Unfortunately, as the Google Realtime API has been deprecated, this isn't something the Stack Overflow community can help with.
What You Can Do:
From here, your best bet is to contact Google directly and see if they can provide you with the respective API data that you need. There is still a cached version of the API reference on Google Search which you can access, which may have links to the correct pages you are looking for.
Google Support can be contacted here, though I feel for this it may be more helpful for you to contact G Suite Support directly. You'll need to follow the corresponding link to you account on this page and contact them this way.
References:
Cache of Google Realtime API Reference
Google Help
Contact G Suite Support
I have a web app and have successfully configured it to access google maps from this URL outside the JavaScript API using this URL:
http://mt0.google.com/vt/lyrs=y&hl=en&x={x}&y={y}&z={z}&s=Ga
The app uses the imagery as background in a PDF report that members of the public can download - this is going to be a free service.
I contacted Google Maps support to ask them if this was allowed under their Terms of Services Agreement but they have referred me to here.
Could I please get an answer as to whether this is allowed or whether I need to enter into a licensing agreement or subscription - and if so what kind? Or alternatively refer me to where I am best to direct this inquiry.
There must be a miscommunication with regards to your concern when you reached out to the support team of the Google Maps Platform API, I would highly recommend that you file another support case via https://console.cloud.google.com/google/maps-apis/support as only the support team of the Google Maps Platform can share more knowledge about your concern as this will require internal investigation as well.
Doing some stress / load testing I got this message and figured out that I'm using the free version of the API and not the one available to us in our Google Premium Plan. We do have a clientId and a crypto key, but we are not sure on how to use them in the URL for proper authentication.
Could anyone please provide hints on such?
If you need to apply a client ID and digital signature in web service requests you should follow this documentation:
https://developers.google.com/maps/premium/previous-licenses/webservices/auth
If you need to authenticate Maps JavaScript API the documentations is here:
https://developers.google.com/maps/premium/previous-licenses/clientside/auth
For load testing you can use a mock API instead of the real one. This way you won't consume your map credits.
Please read about load testing of Google Maps APIs here:
https://developers.google.com/maps/premium/prelaunch-checklist#load_testing
Hope it helps!
I have gone through Quickstart with Google Drive and I have also used Google Play Services. The docs for Google Drive outline the process of how the authorization flow works. The docs also indicate that developers should not use Drive initiated authorization although it appears that the Quickstart sample app does exactly that. I am left with the impression that Google prefers that the developer handle all the details of authorization.
Yet after trying out sample code that uses Google Play Services (but not for Google Drive), I am left with the impression that Google wants developers to use Google Play Services to handle all the authorization. It seems that Google Play Services simplify the authorization process significantly. Although the docs don't say this, I found elsewhere online that GoogleAuthUtil.getToken manages how access and refresh tokens are retrieved, especially after they expire.
Basically, the issue I am struggling with to understand is whether the Google Drive docs for the API are out of date and Google wants us to rely upon Google Play Services. There seems to be a lot of complexity in the Google Drive authorization process that Google Play Services has eliminated. At the same time, the docs for Google Drive API has been available for over half a year, so it makes me question why Google hasn't updated these docs to show any reflection on how Google Play Services are used with it.
Any insight into this would be appreciated.
The recommended approach for authorization on Android is using Google Play Services. The Android quickstart guide on the Google Drive SDK documentation covers exactly that:
https://developers.google.com/drive/quickstart-android
The Google Drive docs are out of date and Google should really update them. Retrieving tokens and authenticating users should be done using Google Play Services. The only thing you should be using the Google Drive API for is accessing the Google Drive service. Google Play Services handles all the details of authenticating users, retrieving access and refresh tokens and handling all the errors that can arise.