Google Drive SDK

Drive Platform Release Notes

This page contains release notes for the Drive platform, beginning with the release of version 2. Latest notes are first.

Updates to the Drive Android API with Google Play Services 4.3

March 24, 2014

Several new features and metadata fields have been added to the API. The new features include:

Ending support for Internet Explorer 9 in the Realtime API on April 15, 2014

March 6, 2014

After April 15, 2014 the Realtime API will no longer support Internet Explorer 9.

Updates to the Drive Android API with Google Play Services 4.2

February 13, 2014

Updates to the Google API client removed the need for many of the Drive interfaces. Many function callbacks have been removed from the API and are replaced with the generic ResultCallback interface.

Google Drive Android API released

January 16, 2014

Initial release of the Google Drive Android API, letting developers more quickly and easily integrate Google Drive into their Android apps. The API simplifies common Drive tasks, handling offline access and file syncing so you can read and write files as if Drive were a local file system.

The Drive Android API also reduces the size of Drive-enabled apps. And since it's now part of the Google Play services client library, it no longer requires compliation with the Google APIs Client Library for Java.

Push notifications released and other changes

July 12, 2013

The Drive API now supports Push Notifications for individual files and folders as well as all changes to a user's Drive. Developers no longer need to poll resources to detect changes. You can create a notification channel using the files.watch and changes.watch methods. You can stop receiving notifications with the channels.stop method.

The openUrlTemplate property has been added to the apps resource. This feature allows developers to retrieve a template version of an application's open-with URL.

The headRevisionId property has been added to the files resource. This property provides a way to retrieve the ID of the head revision for a file with content stored in Drive.

The visibility parameter has been added to the files.copy and files.insert methods. This parameter allows the file visibility to be set to private or the user's default sharing policies. This only applies for files that are not native Google Docs or converted files.

The realtime.get method has been added to allow developers using the Realtime API to export Realtime data models as JSON through the Drive API.

Save to Drive button released

May 8, 2013

The Save to Drive button is now available. This feature provides a customizable button that can easily be added to any webpage to let users save files directly to their Drive accounts.

Undo and redo added to realtime API

April 10, 2013

The Realtime API now provides undo() and redo() methods for undoing and redoing changes.

Custom file properties and application data added

April 4, 2013

The API now supports adding custom file properties to create searchable fields that are private to your app or shared across apps. Additionally, an Application Data folder is now available for applications to store files that should not be modified by users, such as configuration files.

Announcing the new realtime API

March 19, 2013

We have released the collaboration technology that powers Google Docs, Slides, and Sheets as the new Realtime API. See our official announcement for more about this exciting new API!

Deprecated translation query parameters

February 6, 2013

The sourceLanguage and targetLanguage translation query parameters have been deprecated and removed from the files.list, files.update, and files.copy methods.

Empty file updates and revision ordering fixed

December 5, 2012

The head alias for the revisions.get now properly returns the latest revision. This fixes a previously reported issue.

File updates can now contain content with zero length to update a file to an empty state. This fixes a previously reported issue.

Google Drive site publishing and new image metadata added

November 28, 2012

Google Drive users can now serve static web pages from their Drive, and apps can programmatically manipulate webViewLinks (a new property in the files resource) for Drive-based web assets. See Publish Website Content for more information.

The files resource now contains additional image metadata fields for metering mode, sensor, exposure mode, color space, white balance, exposure bias, max aperture value, subject distance, and lens.

Android quickstart example added

November 26, 2012

Google Drive quickstart examples now include a guide for running a sample Android app. See Quickstart: Run a Drive App on Android.

Comments and discussions added

November 15, 2012

The API now includes comments and replies resources together with a simple anchoring scheme to facilitate Drive apps in building collaborative commenting and discussion threads in documents. For more information, see Manage Comments and Discussions.

SharedWithMe search field added

October 29, 2012

The search field sharedWithMe is now available to list files that have been shared with the authorized user. See Search for Files for more information.

Release notes format flattened

October 18, 2012

Previously, these release notes that you are reading contained three separate headings for changes to the Drive API, the Drive UI, and miscellaneous features. We have removed those headings so that you'll always see the latest changes at the beginning of this page.

Custom thumbnails and new image metadata added to files resource

October 18, 2012

The files resource now includes the thumbnail property, to enable the addition of custom thumbnails. For more information, see Uploading thumbnails.

Also, new image metadata fields have been added, including camera make and model, exposure time, aperture, and focal length.

New command-line app "quickstart" sample

August 30, 2012

In addition to the complete examples demonstrating integration with the Google Drive web UI, the documentation now provides an example of a simple command-line app in Java, Python, PHP, .NET and Ruby. See quickstart for information and instructions on how to set up and run the examples.

PHP client library refactored

August 22, 2012

The Google client library for PHP has undergone a major refactoring, and the related PHP code in our reference samples and example app has been updated.

APIs explorer added to reference

August 22, 2012

The Drive API reference documentation now includes the APIs Explorer, a tool to let you quickly try API calls from a graphic interface. See the bottom of the details page for any method, for instance files.list.

Support for drive.apps scope removed

August 3, 2012

Support for the OAuth scope https://www.googleapis.com/auth/drive.apps has been removed. Read-only access to get app information and list a user's installed apps is still available with https://www.googleapis.com/auth/drive.apps.readonly.

July 26, 2012

The webContentLink field was added to the File resource. It contains a URL that is a link for downloading the content of the file in a browser using cookie based authentication. In cases where the content is shared publicly, the content can be downloaded without any credentials.

July 26, 2012

The operators not and != have been added for methods that accept the search parameter q. For more information and examples, see Searching for files.

Image metadata added to file resource

July 26, 2012

The files resource now includes several metadata fields pertaining to image files, including size, dimensions, and geographic location information. For more information, see the reference for the files resource.

isExplicitlyTrashed property added to file resource

July 26, 2012

The files resource now includes a boolean property to indicate whether a trashed file was explicitly trashed by a user, or recursively trashed. For more information, see the reference for the files resource.

Aliases added for head revision and current user

July 26, 2012

When working with revisions, you can use the head alias to refer to the head revision. Similarly, you can use the me alias to refer to the currently authorized user. For more information, see the reference for the revisions and permissions resources.

July 17, 2012

Previously, the files resource included a permissionsLink property containing a link to the file's permissions collection. This link has been removed. Now, the preferred way to discover a file's permissions is to use permisssions.list.

Searching for child folders by parent ID

July 10, 2012

You can now perform queries on parents collections to find child folders using the in operator. For more information and an example, see Searching for files.

Resolution for issues with changes.get

July 10, 2012

Some clients may have experienced internal server errors when making calls to changes.get. The issue causing these problems has been resolved.

Set MIME type when creating shortcuts

June 28, 2012

As of version 2, you must specify the MIME type application/vnd.google-apps.drive-sdk when creating shortcuts to Drive files. This is a change from version 1, in which no MIME type was set for shortcuts. For more information, see Create a shortcut to a file.

Version 2 API resources

June 27, 2012

Version 2 of the Drive API introduces the following API resources:

These resources were not available in version 1 of the Drive API, nor the documents list API. For more information, see Migrate to v2.

Search capability with files.list and children.list

June 27, 2012

You can search or filter files with the files.list or children.list methods of the version 2 Drive API. For more information, see Searching for files.

Touch command to update last-modified time

June 27, 2012

As of version 2, you can use files.touch to make sure the last-modified time displays properly in the Drive UI. This command takes the file ID of a file or shortcut, and sets the file's last-modified time to the current server time.

Parameter id changed to fileId

June 27, 2012

As of version 2 of the Drive API, the parameter id from files.update and files.get is renamed to fileId.

Command to list installed apps

June 27, 2012

The apps.list method introduced in Drive platform v2 allows you to list a user's installed Drive apps. Requires the scope, https://www.googleapis.com/auth/drive.apps.

New setOAuthToken function available when opening files with Google Picker

July 17, 2012

The Google Picker API, used to open files from the Drive UI, now supports the setOAuthToken function. This method allows a file picker to determine the user via the OAuth 2.0 token for the current Drive API session, allowing easier handling of multiple login scenarios. We recommend using this method over setAuthUser except for cases where no token is available. For more information, see the Google Picker API Reference.

Android Drive UI integration

June 27, 2012

Using the Drive API and the Android Development Kit, you can integrate a mobile app with Google Drive on Android. For more information, see Integrate with Android.

Field parentsCollection renamed to parents

June 27, 2012

As of version 2 of the Drive API, the parentsCollection field in files listing parent folders has been renamed to parents. For more information, see Work with Files and Folders.

Alias for root folder

June 27, 2012

When working with files and folders, you can use the root alias to refer to the root folder anywhere a file ID is provided. This is new in Drive platform v2.

Open and convert Google Docs from the Drive UI

June 27, 2012

An app registered with the Import option enabled in the APIs Console can import supported Google Doc formats. This means that if a user selects Open with for a Google doc, the app can convert it to a format that the app can handle. For more information, see Open and convert Google Docs in your app.

Sharing dialog available to embed in apps

June 27, 2012

As of Drive platform v2, apps can display a standard Google Drive sharing dialog to let users share files. To implement this, you'll need to add some simple JavaScript to your application code as described in Launching the Google Drive sharing dialog in your app.

New Drive scopes

June 27, 2012

Drive platform version 2 introduces new authorization scopes, including a fine-grained scope for read-only access to file metadata (https://www.googleapis.com/auth/drive.readonly) and a utility scope for listing installed Drive apps with apps.list. (https://www.googleapis.com/auth/drive.apps). For more information, see Choosing Auth Scopes

Chrome Web Store installation requirement removed for Drive API access

June 27, 2012

Version 1 of the Drive platform did not allow API access unless third-party apps had created a listing to install the app from the Chrome Web Store. While there are still advantages to listing in the Chrome Web Store (see Integrating your app with the Drive UI and Chrome Web Store, the requirement has been removed. As of version 2, the Manage Apps dialog lists all apps that have been granted Drive access.

Enhanced discoverability for installed apps

June 27, 2012

In cases where the user has not installed a valid viewer for a file, and the Google Drive viewer can’t render the file either, Drive displays a link to a Chrome Web Store list of apps that can open that file type (if any). For information about adding your app to such lists, see Help Users Find your App.

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.