Crash when using URL fragment() (macOS 13, iOS 16)

Development Core Libraries
, ,
1

Hi all,

I was updating my usage of URL's fragment to fragment(percentEncoded:) due to the former being marked as deprecated, but seem to have encountered a bug in the latter's implementation. This function crashes (EXC_BREAKPOINT) whenever the URL contains no fragment, instead of returning nil as documented. I'm encountering this when running on macOS 13.2.1 and simulator for iOS 16.1. A very simple example can exhibit the crash:

if let url = URL(string: "https://www.google.com"),
   let fragment = url.fragment() /* this crashes */ {
    print(fragment)
} else {
    print("No fragment")
}

I actually can't seem to find a way to use fragment() on a URL without a fragment without it crashing.

I wasn't able to find any other posts regarding this issue, so definitely let me know if this is a known issue and/or there's already progress on fixing it.

2

You'll want to report this to Apple using their Feedback reporter. They may be able to help you find a work around. Or perhaps fix it in the next release.

3

Does the old API also crash? Or the new API when you pass "percentEncoded: false"?

Also worth trying using components:

print(url.fragment(percentEncoded: false))
let components = URLComponents(url: url, resolvingAgainstBaseURL: false)!
print(components.fragment)
print(components.percentEncodedFragment)
4

Old API worked fine for me.

5

@Jon_Shier Sure thing, will do

@tera The old API works fine, it's the new API that is crashing

6

Then the solution is easy: file a bug, optionally post the bug id here, and use the old call in the meantime, unless you need to do something with escaping / unescaping that the old API doesn't provide, in that case reach out for one of the alternatives mentioned above or use some explicit escaping conversion functions.

(It's interesting though how the situation like this can surface in the first place; whoever implemented the new fragment() API didn't bother implementing a trivial unit test?)

7

I think the real problem is they fixed it, but never updated the available documentation. This api should be marked unavailable for versions where it will cause a crash if the host is nil.