Migrate from the Google Drive Android API

The Drive Android API is deprecated as of December 6, 2018 and will be fully turned down on February 1, 2023.


Date Drive Android API status
December 6, 2018 Deprecation is publicly announced. Existing clients will be able to access the API normally, but should immediately commence with migration efforts. New clients must not use the API.
October 21, 2019 The Drive Android API is removed from the Google Play Services SDK distribution. Apps will be unable to build until removing the Drive Android API dependency, but existing builds will be unaffected. The Drive Android API public documentation will no longer be available.
March 3, 2022 The Drive Android API is deprecated and all API calls are non-operational. Clients must migrate by this date.
February 1, 2023 The Drive Android API will be fully turned down and all connection attempts will be unsuccessful.

Use the Drive REST API

The Drive REST API offers the same functionality as the Drive Android API, including ways to:

To ease client migration efforts, a sample app is provided which demonstrates each of the proposed replacements above. It also shows how to create, modify, and query for a user's Drive files using the REST API. If you have any issues, check out the google-drive-api tag on StackOverflow.


Since the Drive Android API is deprecated, and all API calls are non-operational, make sure your app is no longer calling the API. To do this, remove the code that initializes the API: addApi(Drive.API).

If you don't migrate from the Drive Android API, and your app attempts to call the API, the following error message is returned:

com.google.android.gms.common.api.ApiException: 17: API: Drive.API is not available on this device. Connection failed with: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}