-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Technical/unnecessary errors on federated sharing #1667
Comments
Well. no because it could be reached but the certificate is invalid. I mean we could print that. But saying it could not be reached is simply false. But a more understandable error message is a good idea.
Not showing up sounds like a bug. Tooltip also better indeed. |
@rullzer it should be a more explanatory message, but the question also is if the certificate of my friends’ server being invalid is even relevant to me. Because sharing was apparently successful after all. |
@jancborchardt yes that part I agree on. Also we need better error handling there. because sharing was not succesfull. We could not talk securely to your friends server. So we error out half way. When that happens we should cleanup things. CC: @schiessle |
Aah ok so that's why all the errors happen. The user is shown in the list but sharing was actually not successful. |
@schiessle I just helped a friend set up Nextcloud. Roughly 10 minutes after installation I wanted to share a file with him via federated sharing. Typing in his whole address brought up this error notification:
Then refreshing and trying it again gave me an error notification up top like:
Even though the user didn’t show up as an entry in the list. But it was apparently shared.
And now when I try to share the file with the same user it’s already shared with, I get a tooltip:
The text was updated successfully, but these errors were encountered: