Open dennis-eisen opened 4 years ago
Briefly explained, as you can also see in the server logs above, the iOS app fails to encode #
to %23
, as it should, and the server therefore truncates the URL at the #
. This might also happen for other special characters, please check.
Doesn't happen for Android App, Web UI or Sync Clients on Windows and MacOSX.
This is a problematic bug and not a feature request. Would you mind to add the "bug" label?
Not sure if this is related to the same issue, but lately I've been seeing 405's being thrown all the time when using the iOS app. I even tried a fresh install of the app but I'm still greeted by the pesky 405s.
At a first glance it appears to me that the issue here might be solved with processing the string with .addingPercentEncoding(withAllowedCharacters: .urlQueryAllowed)
.
I don't know exactly where to look since it's a big project and I haven't touched it in a few years 🙈, but I'm happy to try it out and submit a PR - I must first find where the "offending" text is though... any hints appreciated :)
Regarding my pool of 405s,
Build the app from the develop branch Login with an empty test user Go to files
No error
Error with message "Request failed: method not allowed (405)"
To reproduce it several times, you can for instance switch from the tab More to Media.
I can move this to a new ticket if not related to #1196.
@rygen du you have try with the version 3 in TestFlight?
@marinofaggiana regarding my device - I was still on the App Store version. I've now tried the TestFlight version as you suggested and the 405s seem to be gone. 🎉 However, the reproduction steps above were done after building from the latest commit on develop.
Expected behaviour
open folder containing # sign
Actual behaviour
405 error message
hash is not encoded right. Works perfectly in Android App.
Server error message
Steps to reproduce
open folder containing # in iOS Nextcloud App
Reasoning or why should it be changed/implemented?
its a bug
iOS version
13.3.1
App version
2.25.9.2