The upstream library that implements urlDecodedString currently has a bug. It decodes the url first and then replaces "+" (plus) with a " "(space). This interferes with strings containing %2B (+ in hex form). Replacing it with stringByReplacingPercentEscapesUsingEncoding: until underlying library fixes the implementation.
Thanks again. I think that by using stringByReplacingPercentEscapesUsingEncoding we don't need the old category method anymore, so this should be considered a permanent replacement.
The upstream library that implements
urlDecodedString
currently has a bug. It decodes the url first and then replaces "+" (plus) with a " "(space). This interferes with strings containing %2B (+ in hex form). Replacing it withstringByReplacingPercentEscapesUsingEncoding:
until underlying library fixes the implementation.