Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Files not Shown #5570

Closed
cyberduck opened this issue Dec 15, 2010 · 12 comments
Closed

Files not Shown #5570

cyberduck opened this issue Dec 15, 2010 · 12 comments
Assignees
Labels
bug googledrive Google Drive Protocol Implementation worksforme
Milestone

Comments

@cyberduck
Copy link
Collaborator

83c9d09 created the issue

Hi,

I am using 4.0b8(8071) same as the pre-Versions, i can log in - but i can not see any files or folders. If I am creating a new folder it ist there directely in GoogleDocs.

Do you have any soloutions for this problem`?

Thanks

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please check that your login credentials username match the email address that is the owner of the documents.

@cyberduck
Copy link
Collaborator Author

58c135a commented

I am having mostly the same issue. Using CyderDuck Version 3.8.1 (7954), I can login to GoogleDocs (connection is made) but see no files and no directories (yes, I have some). I can; however, create a directory with CyberDuck that DOES APPEAR in GoogleDocs, but does NOT APPEAR in CyberDuck. This suggests that CyberDuck is indeed connected to the correct Google Docs account, but that it does not display files or folders.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you make sure that you login in with the email address that is equal to the owner of the documents.

@cyberduck
Copy link
Collaborator Author

58c135a commented

Yes, I am logging in with my primary gmail address and I also tried with my secondary email address. No difference in behaviour.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you post the file cyberduck.log in the Cyberduck AppData directory.

@cyberduck
Copy link
Collaborator Author

58c135a commented

Replying to [comment:5 dkocher]:

Can you post the file cyberduck.log in the Cyberduck AppData directory.

I cannot find a "cyberduck.log" file. I am on Mac OS X, not Windows. Perhaps this should move to a new ticket number?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:7 lyne.eaker]:

Replying to [comment:5 dkocher]:

Can you post the file cyberduck.log in the Cyberduck AppData directory.

I cannot find a "cyberduck.log" file. I am on Mac OS X, not Windows. Perhaps this should move to a new ticket number?

On Mac, you find any related output in the system.log (/Applications/Utilities/Console.app).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please enable debug logging and me any output in in the system.log (/Applications/Utilities/Console.app) after restarting Cyberduck and attempting to connect.

@cyberduck
Copy link
Collaborator Author

58c135a commented

Log file created and saved. How shall I get it to you? It is quite large and not appropriate to paste into this reply.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:10 lyne.eaker]:

Log file created and saved. How shall I get it to you? It is quite large and not appropriate to paste into this reply.

You can send it to [mailto:feedback@cyberduck.ch feedback@cyberduck.ch].

@cyberduck
Copy link
Collaborator Author

@dkocher commented

As of 9136327 files are displayed when case-sensitivity of login is different from owner of the document.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

With a43a94b and update of the core library in ef89232 now all documents reagardless of the document owner are listed.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug googledrive Google Drive Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants