Hello,
The OnlyOffice Android app no longer works with Seafile 7.1.
Whenever I switch to the Clouds tab I get the error message "Connection error. Try again later."
There is no error in the Seafile / nginx logs.
Also none in the OnlyOffice logs.
Other WebDAV applications work with my Seafile server without problems.
onlyoffice android don't work anymore with Seafile 7.1
-
- Posts: 3
- Joined: Fri Dec 25, 2020 1:13 am
Re: onlyoffice android don't work anymore with Seafile 7.1
Hello privnote42,
Could you please specify if the connection worked previously with the same Seafile version or with an older version?
Could you please specify if the connection worked previously with the same Seafile version or with an older version?
-
- Posts: 3
- Joined: Fri Dec 25, 2020 1:13 am
Re: onlyoffice android don't work anymore with Seafile 7.1
yes, the connection worked with the earlier seafile version 6.3.13
Is there a logfile in the onlyoffice android app?
I could not find one so far
Is there a logfile in the onlyoffice android app?
I could not find one so far
Re: onlyoffice android don't work anymore with Seafile 7.1
Hello privnote42,
We have managed to reproduce the issue and registered a bug in our tracking system. It will be fixed in one of the future updates for ONLYOFFICE Android app. Sorry for the inconvenience.
We have managed to reproduce the issue and registered a bug in our tracking system. It will be fixed in one of the future updates for ONLYOFFICE Android app. Sorry for the inconvenience.
-
- Posts: 3
- Joined: Fri Dec 25, 2020 1:13 am
Re: onlyoffice android don't work anymore with Seafile 7.1
Hi Carl,
thanks, thats very good news.
Is there an ETA for the fix?
thanks, thats very good news.
Is there an ETA for the fix?
Re: onlyoffice android don't work anymore with Seafile 7.1
Hello privnote42,
We have fixed the issue and it will be definitely fixed in the next update for the Android app, but unfortunately I cannot specify any time frames of the release at the moment.
We have fixed the issue and it will be definitely fixed in the next update for the Android app, but unfortunately I cannot specify any time frames of the release at the moment.