Databases
StackOverflow2013
Postsdbo
POGoogle Docs/Drive API does not permit a new document to be inserted into a new Google account
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGoogle Docs/Drive API does not permit a new document to be inserted into a new Google account
    text
    copied!<p>We have identified an issue with the Google Docs/Drive APIs that is consistently reproducible, and appears to be a new bug introduced a few weeks ago. To see the issue, follow these steps:</p> <ol> <li>Create a brand new Google account, but do NOT do anything in that account (do not click on Drive to view Google Drive) -- just create it and close that window.</li> <li>Attempt to insert a new (empty) document via the Google Docs API (we use Zend GData for that) or the new Google Drive API.</li> </ol> <p>Result: With old Google Docs API, the error "<strong>Expected response code 200, got 400. Unable to convert document</strong>" is thrown (which is meaningless when we are just creating a new document, not uploading something). With the new Google Drive API, the same thing produces the error "<strong>An error occurred: Error calling POST googleapis.com/drive/v2/files: (500) Internal Error</strong>"</p> <p>This continues to happen until I go into that new Google account and click "Drive" to enter Google Drive. Something about doing that "initializes" Google Drive for that user, at which point the code to insert the new document works without any issue.</p> <p>This only started happening recently (within the last few weeks). The same code has been in place for years without any problem in this scenario. In a school setting, where an administrator is creating new student accounts (as Google Apps for Education accounts), this issue shows up very frequently as they use our service. Is this going to be fixed? Is there a work-around? Help, Google API folks!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload