> Actually don’t do the substitution by hand. Let NSString URL-encode it
for you. Otherwise your URL will break again when someone decides to type a
“/“ or “#”, etc. into your text field.
This is an interesting point. A / is actually legal in a URL but has
specific semantics, while space just isn'
Thank you so much!
On Fri, Jun 16, 2017 at 3:15 PM Jens Alfke wrote:
>
> On Jun 16, 2017, at 8:00 AM, Eric E. Dolecki wrote:
>
>let modified = supplied.replacingOccurrences(of: " ", with: "+")
>
>
> Don’t use “+”, use “%20”. The “+” is only valid in some contexts IIRC,
> like form v
> On Jun 16, 2017, at 8:00 AM, Eric E. Dolecki wrote:
>
>let modified = supplied.replacingOccurrences(of: " ", with: "+")
Don’t use “+”, use “%20”. The “+” is only valid in some contexts IIRC, like
form values.
Actually don’t do the substitution by hand. Let NSString URL-encode it
That makes perfect sense. I was talking to a tvOS engineer @ WWDC 2017 and
was told I don't have to worry about URLencoding app to app URLs. I thought
that sounded weird, tried it, sure didn't work ;)
Thanks Aandi.
On Fri, Jun 16, 2017 at 12:48 PM Aandi Inston wrote:
> Spaces are not legal in a
Spaces are not legal in a URL. So failure or unpredictable results is
expected. See for example discussion here
https://stackoverflow.com/questions/497908/is-a-url-allowed-to-contain-a-space
On 16 June 2017 at 16:00, Eric E. Dolecki wrote:
> I have deep linking working, but if I introduce spaces
