Home/ Questions/Q 7876137
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T03:07:19+00:00

I’m trying to get familiar with the Google Drive API using the official Java

  • 0

I’m trying to get familiar with the Google Drive API using the official Java sample. However, after wasting a few hours and attempting to set the sample up two times, I’m still not able to use it as expected.

Instead of displaying a file’s content it throws a 404 error in the FileServlet (/svc path). More specifically, service.files().get(fileId).execute(); seems to return null. I’ve tried it with different files, different MIME types, directly from Google Drive as well as using the Google File Picker.

I’ve followed the steps described over at https://developers.google.com/drive/examples/java as closely as possible.

Has anyone been able to get the sample running?

edit:
Here’s the log output of the FileServlet when requesting the URL /svc?file_id=0B08R9MrOE-ejZTY2M2I5MjAtYmVjZS00OTkyLWI4ZTEtOTg4OGM3YTIxMWEw (the 404 error is thrown at line 78):

2012-04-26 08:21:36.077
com.google.api.client.http.HttpRequest execute: -------------- REQUEST  --------------
GET https://www.googleapis.com/drive/v1/files/0B08R9MrOE-ejZTY2M2I5MjAtYmVjZS00OTkyLWI4ZTEtOTg4OGM3YTIxMWEw
Accept-Encoding: gzip
User-Agent: Google-HTTP-Java-Client/1.8.3-beta (gzip)

D 2012-04-26 08:21:36.263
com.google.api.client.http.HttpResponse <init>: -------------- RESPONSE --------------
403 OK
content-type: application/json; charset=UTF-8
content-encoding: gzip
date: Thu
date: 26 Apr 2012 06:21:36 GMT
expires: Thu
expires: 26 Apr 2012 06:21:36 GMT
cache-control: private
cache-control: max-age=0
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
content-length: 188
server: GSE
x-google-cache-control: remote-fetch
via: HTTP/1.1 GWA

D 2012-04-26 08:21:36.265
com.google.api.client.http.HttpResponse getContent: Response size: 188 bytes
D 2012-04-26 08:21:36.271
com.google.api.client.http.HttpResponse getContent: {
 "error": {
  "errors": [
   {
    "domain": "usageLimits",
    "reason": "dailyLimitExceededUnreg",
    "message": "Daily Limit Exceeded. Please sign up",
    "extendedHelp": "https://code.google.com/apis/console"
   }
  ],
  "code": 403,
  "message": "Daily Limit Exceeded. Please sign up"
 }
}

This sounds a lot like “I don’t know you” to me, so I have taken another look at my Client ID and Client Secret: I’ve noticed that there are two Client IDs and Client Secrets being displayed in the API Console, one “Client ID for web applications” and another “Client ID for Drive SDK”. I’ve used the one for web applications previously, so I tried to switch to the one for the Drive SDK. Unfortunately, this doesn’t change anything. Same error… :/

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I eventually managed to get it working. I’m not sure what was the problem before, but here are some tips for those who are facing similar problems:

    • The “Client ID for web applications” and the “Client ID for Drive SDK” confused me. Unfortunately the documentation doesn’t tell you which one to use at which place, but it seems like you only need the “Client ID for web applications”.

    • If you update your Chrome extension or the API console it could take some time until Drive recognizes those changes. For example, changing the OAuth Client ID in the API console could take some time until it takes effect, since everybody’s caching. If you are testing your application, deleting cache and cookies helps speed up the process.

    Good luck with your applications, and thanks to everybody who helped me!

    • 0