prayagverma / gdata-python-client

Automatically exported from code.google.com/p/gdata-python-client
1 stars 0 forks source link

Unable to access some of the spreadsheets shared with user through API #624

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi!

I am having some issues with accessing some spreadsheets through the gdata API. 
The scenario is that we have a bunch of spreadsheets organized in a folder 
hierarchy owned by user A. A folder in the hierarchy has been shared (with edit 
permissions) to user B and the idea is that user B will use the gdata python 
API to programatically fetch information from spreadsheets located beneath that 
folder. This works fine for most spreadsheets but some of them fail to be found 
when using the API. If I log in to gmail as user B and access the documents 
through the web interface, I am able to see the spreadsheets, so this seems to 
be related to the API itself. If I access the spreadsheet through the web 
interface as user A and click "Share", user B is listed as having access with 
edit permissions. Finally, explicitly adding user B once again through the 
share dialog resolves the issue and user B is able to access the spreadsheet 
through the API (this is however unfeasible due to the amount of documents).

The situation is quite hard to reproduce as I can see no logic between whether 
the spreadsheets are accessible or not. I've attached a code snippet containing 
the API code I use for accessing the spreadsheets feed, it should be fairly 
self-explanatory. 

Any suggestions are welcome.

What steps will reproduce the problem?
1. Share a folder structure with spreadsheets with another user
2. Try to locate the spreadsheet in the spreadsheets feed as that user (see 
enclosed code snippet)

What is the expected output? What do you see instead?
"Found 1 spreadsheets matching ..." when being able to access document but 
"Found 0 spreadsheets matching ..." if not.

What version of the product are you using?
2.0.17

Please provide any additional information below.

Original issue reported on code.google.com by b97...@gmail.com on 28 Jun 2012 at 12:25

Attachments: