-
Notifications
You must be signed in to change notification settings - Fork 279
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
Can view folders, but can't view files #818
Comments
uniq log line in nginx:
|
Hello, Or any chance a patch could be made one day ? I tried with version 2.2.39 and 2.2.44 on a Max Lumix tablet Log line in Nginx access.log:
When I try to use this URL, I get this JSON content (which is not the actual file content):
|
I have a possible lead to correct this issue. When clicking on a text file, I get the error and get a log entry:
If I use this request and use it in my browser (logged in to my seafile server), I get the actual URL of the file: Request:
Answer:
The download is not done from this point. So it seems that for some reasons, the answer is not taken into account and calls the method Hope it helps |
I managed to reproduce the bug using Android Studio 2021.1.1 with a Nexus 9 API 29 emulator (x86_64) However, I would like to know where in the code each item displayed in browser is initialized Any lead ? |
I'm using Seadroid 2.2.15, and I'm able to browse the heirarchy of my seafile server, and can even decrypt encrypted stores, but I am unable to download any files, including images or text files.
Every time I tap on a file, I am presented with an endless stream of:
(Note the missing close-quote)
I don't see anything relevant in the logs, though occasionally see the following occurring every 50ms for about a minute, which I suspect is it trying to upload photos:
I don't see any logs on the server, either.
The server is behind a Traefik proxy that is adding https. I have no problems with the desktop client, web client, or Syncthing.
How can I debug errors that Seadroid is throwing?
The text was updated successfully, but these errors were encountered: