We're having problems with Google Plus API. Since yesterday it sends timeouts for some of our requests (most of them). Does anyone that uses the API has experienced this problem? I have problem contacting someone from Goggle plus to explain the behaviour
This might have something to do with the announcement:
The photos space will sunset in early January 2018. Your users can
continue to access Google Photos via the drive space by enabling the
Google Photos folder in My Drive in the Drive client settings
This is currently posted in Drive API docs.
Check the How Google Photos works with Google Drive for more info.
Related
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
This might be a very silly question, but I'm just trying to make sure I'm going about things for my senior project right. Does the Google Drive API connect to the user's personal Drive space?
Actually it's a very good question because it confuses a lot of first time Drive users.
The answer is, It depends.
There are two distinct Google Drive APIs, with different characteristics and capabilities. These are the Google Drive REST API and the Google Drive Android API (GDAA). You have tagged your question with both.
The Google Drive REST API can connect to any Drive account, e.g. your own, one of your users, or a Service Account. Which account it connects to is determined by how the Access Token was generated.
The GDAA only connects to the Google account associated with the Android device it's running on.
The 22nd of January, I received an email with the subject 'Important: Steps to migrate from discontinued Documents List API' from Google Apps .
Important: Steps to migrate from discontinued Documents List API
Hello administrators,
We recently communicated that Documents List API will be discontinued on April 20, 2015. This change means that service calls for this API will no longer be supported, and any Google Apps features that are implemented using this API will no longer function.
Our records indicate that you may have an application that uses Documents List API, and we recommend that you migrate to Drive API, which has comparable
functionality, as soon as possible.
Here's what you need to do:
Determine if you have an application that makes requests to these
types of URLs:
https://docs.google.com/feeds/
https://docs.googleusercontent.com/
https://spreadsheets.google.com/feeds/
Migrate the applications to Drive
API. If you have questions
about migration, please contact Google Apps for Work Support.
Sincerely, The Google Apps for Work Team
I think it says that applications using https://spreadsheets.google.com/feeds/ should migrate to the new Drive API. But in the new Drive API, this URL is used too:
https://developers.google.com/google-apps/spreadsheets/#sheets_api_urls_visibilities_and_projections
Is there a typo somewhere in the URL either in the email or Drive API documentation?
Or is this email saying that when you determined you used any of these URL's you're OK?
PS: I opened a case at Google but I fear a late response, so I asked here.
Short answer is no.
The Docslist API is being discontinued because it has been replaced by the Drive API. In the case of the Spreadsheet API, there is no replacement API (yet - maybe one day), so it remains supported.
The only gotcha is that at some point, only OAuth 2 will be supported for authentication/authorisation so if you're using OAuth 1 or u/p, you have some work to do.
The official Google response is that the Spreadsheets API will continue to function after the 20 April shutdown:
"Apologies for the confusing email. The sheets API is not yet deprecated and will continue to operate beyond the April shutdowns."
https://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3709
I am facing a bug with Realtime API of Google Drive SDK and I like to know if there is an issue tracker where I can check if that issue is registered and eventually fill a new one.
There are no official bug trackers for the Google Drive service.
There is this page, which lists the known issues encountered using Google Drive :
http://support.google.com/drive/bin/static.py?hl=en&page=known_issues.cs
And this other one that links to Google Drive service's forum, where yo can actually report an issue (look at the proposed categories):
https://productforums.google.com/forum/m/#!forum/drive
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.