Please migrate off JSON-RPC and Global HTTP Batch Endpoints - Google Drive API

user_1477347 0
Viewed 731

Similar to other developers, I got an email from Google regarding my Android app, saying "Please migrate off JSON-RPC and Global HTTP Batch Endpoints", and it lists the offending API as:

Google Drive API version drive@2 and "Global HTTP Batch Endpoint"

It says that I should somehow "migrate off" it, but is not clear how. I updated the dependency from:

google-api-services-drive:v2-rev305-1.23.0

to

google-api-services-drive:v2-rev332-1.25.0

But is this enough? Or must I upgrade to drive:v3, which is lacking some functionality from v2 and would be very difficult to use in my case? Or perform some other magic???

google-drive-android-api google-cloud-endpoints google-drive-api android
1 Answers

There's a blog for Google Developers about discontinuing support for JSON-RPC and Global HTTP Batch Endpoints.

The JSON-RPC protocol and Global HTTP Batch (Javascript example) features was based on an architecture using a single shared proxy to receive requests for all APIs. To improve performance and security, these features are no longer compatible with the latest architecture and business requirements.

As a result, next year, on March 25, 2019 we will discontinue support for both these features.

You can check the guidance from the blog which will help you ease the transition and also consult the API documentation.

user_101053210
Related