Open tvwenger opened 5 months ago
This is a duplicate of https://github.com/haiwen/seadroid/issues/1009
@zhwanng just bumping this issue, as it is pretty functionality-breaking! I'll poke around in the code and see if I can help.
Can you test if this issue happens with the v3.0.0-alpha version?
@zhwanng we have multiple issues here with the same Problem and according to: https://github.com/haiwen/seadroid/issues/1009#issuecomment-2136552334 the problem exists in the v3.0.0, too...
Hello, attached is a logcat extract when opening the above view which shows "Could not connect with server". It contains a stackstrace, maybe it ihelps for debugging.
@zhwanng Thanks for working on this! Any updates, or any other info we can provide?
For me the issue started appearing on v2.3.7 and downgrading to v.2.3.6 fixes the problem, so both v2.3.5 and v2.3.6 work in my case.
Same here. Before this a "refresh" (pulling down from the top of the screen) fixed this, but now it shows the same error every time.
Hi, same issue here - I use an samsung s24 (Android 14) and seafile App v2.3.7.
A installed 3.0.4 from https://github.com/haiwen/seadroid/releases and this works.
Starting with the latest update, I am no longer able to access my seafile drive using the default system file selection tool. I have tested this both attempting to browse to a password database via Keepass2Android as well as attaching a file to an email via Gmail.
The account shows up in the options on the side/menu panel and under "browse files in other apps", but no files are able to be loaded. Clicking on the account loads either a listing of directories and a "Could not connect to server" error, or a "Can't load content" error. Refreshing alternates between the two error messages.
See the attached photos.
Downgrading to v2.3.5 fixes the issue.