You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the real solution via a proper server timeout will take some time (NC 13, nextcloud/server#4510 (comment)) I suggest to just enhance the timeout to > 30s, probably 45s. This way all "blocked" users will connect again and the other have to wait just a little bit longer to get the "connection timed out" message. @mario@AndyScherzinger
Activity
AndyScherzinger commentedon Apr 26, 2017
Yes, please! This might prevent some recurring questions coming in via the forum, tracker, etc. due to the lack of given information by the app.
AndyScherzinger commentedon Apr 27, 2017
Would help with #433 for example
tobiasKaminsky commentedon Apr 27, 2017
As a small brainstorm with Lukas:
mario commentedon Apr 27, 2017
Sure, this was discussed at the last hack week.
tobiasKaminsky commentedon Apr 27, 2017
Then an issue with such an info and roadmap would have been nice to not redo the work ;-)
mario commentedon Apr 27, 2017
I would have expected my friend @LukasReschke has done it already :P
tobiasKaminsky commentedon Apr 27, 2017
At least not here in android repo ;-)
LukasReschke commentedon Apr 27, 2017
Evil evil Lukas 😉
tobiasKaminsky commentedon May 16, 2017
As the real solution via a proper server timeout will take some time (NC 13, nextcloud/server#4510 (comment)) I suggest to just enhance the timeout to > 30s, probably 45s. This way all "blocked" users will connect again and the other have to wait just a little bit longer to get the "connection timed out" message.
@mario @AndyScherzinger
AndyScherzinger commentedon May 16, 2017
Sounds good to me 👍
joshtrichards commentedon Oct 4, 2024
Fixed in nextcloud/android-library#65
The balance is a duplicate of #1178