Different Behaviour of URL(_ : FilePath) across Xcode 26.x and Xcode 16.x

[tsra0ne]

On Xcode 16.x - prints

http:/example.xox --
file:///private/var/folders/hs/w21j_vrd0kq96xyd57vxwrkh37h_f5/T/com.apple.dt.Xcode.pg/containers/com.apple.dt.playground.stub.iOS_Simulator

On Xcode 26.x - prints

http%3A/example.xox --
file:///private/var/folders/hs/w21j_vrd0kg96xyd57vxwrkh37h_f5/T/com.apple.dt.Xcode.pg/containers/com.apple.dt.playground.stub.iOS Simulator
•MyPlayground-04F92754-0C6A-4742-9C05-295065ADEB75/

You can see it is getting percent-encoding
Can i know what changed this behaviour and how can i fix this?

[jrflat]

Hi @tsra0ne, the above code is using the URL.init?(_ path: FilePath) initializer, which was deprecated in iOS 16 because it's unclear that the initializer requires a file path like "/path/to/my/file", not an HTTP URL string. For non-file paths, you'll want to use URL(string: "http://example.xox").

In the Xcode 16.x example, we see that it's actually treating http:/example.xox as a relative path, relative to a file URL representing the current working directory. This is problematic because if we re-parsed relative string, we'd suddenly get a "http" scheme instead of the "file" scheme that is usually expected. For a clearer example, if we had "some:relative:file:name" relative to "file:///current/directory/" and parsed just the relative string, we'd get a URL with the scheme "some", which is unexpected. That's why the new implementation percent encodes ":" in the first path segment so that its not mistaken as the scheme separator.