sahilg1410 / google-api-php-client

Automatically exported from code.google.com/p/google-api-php-client
Apache License 2.0
0 stars 0 forks source link

Drive API - Error 400 when setting base64encoded thumbnail #216

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Do what your instructions say on this page:  
https://developers.google.com/drive/file?hl=en
2. Get a Error 400
3. Smack head on desk.

What is the expected output? What do you see instead?

I'm expecting to get a custom thumbnail on the file we are inserting.

What version of the product are you using? On what operating system?

0.6.0 revision: 508

Please provide any additional information below.

If i just put garbage (123) in for the image data it passes but does not work 
(obviously).  It only gives an error 400 when I pass a valid image base64 
encoded.

Original issue reported on code.google.com by j...@lucidchart.com on 7 Nov 2012 at 6:26

GoogleCodeExporter commented 9 years ago
Hi Jeff, would you be able to provide a minimal sample that demonstrates the 
problem so we can verify & investigate it?

Original comment by ianbar...@google.com on 22 Mar 2013 at 4:10

GoogleCodeExporter commented 9 years ago
This issue tracker is now closing. Development on the Google PHP client library 
moved to GitHub with the release of the 1.0.0-alpha, and now the 1.0 branch has 
reached beta status there will be no further releases of the 0.6 branch of the 
library. 

Please take a look at the latest version on 
https://github.com/google/google-api-php-client

For information on migrating, please take a look at this guide: 
https://developers.google.com/api-client-library/php/guide/migration

For general library support please ask a question on StackOverflow: 
http://stackoverflow.com/questions/tagged/google-api-php-client

If you are looking for support with a specific API, please contact the team 
working with that API via StackOverflow or their preferred support mechanism. 

If your issue still exists with the new version of the library, please raise a 
bug in the GitHub issue tracker with a minimal code sample. 

Thanks!

Original comment by ianbar...@google.com on 22 Jan 2014 at 4:53