I have a situation where I am loading arbitray data from network-
supplied URLs. Sometimes the URLs contain Kanji unicode
characters. When they do, my HTTP loading mechanism (which is built
around NSURL* frameworks) dies with an exception deep inside of
CFURLGetString.
That indicates either a bug in the frameworks, or that you're passing
in illegal values.
Also, what do you mean by a URL containing Kanji characters? URLs can
only contain ASCII; anything else should be escaped using "%". If you
try to construct an NSURL from an invalid string, you'll get nil, and
passing that nil URL into other framework calls could definitely cause
exceptions/crashes.
Pasting in the backtrace from a crash log would be useful for
diagnosing this.
