Closed ben-p-commits closed 2 years ago
I think this is the commit which caused the issue?
EDIT:
woops- i mean the commit following that one!
Great catch! I guess none of our tests flushed this one out. It looks like there's just a redundant URL Encoding happening somewhere which is encoding the %
in %20
. We're working on it now.
Fix implemented on version 8.10.3
❤️ Love the SDK btw- you do a great job! @DuncanBeutler - you seem to be the guy to talk to tag for this.
It appears that there is a bug that has been introduced sometime after version 8.8.7. It is working when I revert to 8.8.7, but broken in the latest version.
Reproduction
Make any request with the US autocomplete API that uses a selection string. View the string in the logs.
Expected Behavior
The query param for the selection should use proper %20 space escaping when viewed in the lldb logs:
112%20Nc%2054%20Apt%20(192)%20Carrboro%20NC%2027510
returns 200 with valid results
✅Actual Behavior (in latest version of the SDK)
The query param for the selection is using aberrant escaping for spaces (%2520?) when viewed in the lldb logs:
112%2520Nc%252054%2520Apt%2520(192)%2520Carrboro%2520NC%252027510
returns 200 with null result
⚠️