Bug 26038 – Webkit will not launch, 'path contains unsupported character'?

• Component: Platform
• Status: RESOLVED FIXED

[Adam Lounds]

"WebKit is located at a path containing an unsupported character.  Please move WebKit to a different location and try again."

Just had this after auto-updating latest nightly, worked yesterday, no colons in paths here (see bug 23527)

Tried dtrace to look at file opens, couple of suspects:
open_nocancel:entry WebKit /Users/adam/Desktop/WebKit.app (note: no colon in path to webkit...)

open:entry WebKit /var/folders/W+/W+YgonaqFSy37tzOonOgYk+++TI/-Caches-/com.apple.IntlDataCache.le
open:entry WebKit /var/folders/W+/W+YgonaqFSy37tzOonOgYk+++TI/-Caches-/com.apple.IntlDataCache.le.sbdl
open_nocancel:entry SFLSharedPrefsT /Users/adam/Library/Preferences/cfx#coBHrra

[Adam Lounds]

revision was r44111, safari beta 4 (5528.17).

Downloaded 44174 from webkit website and launched OK. Can still reproduce with r44111 webkit, but looks like it may have been fixed between r44111 and 44174...

[Mark Rowe (bdash)]

The only reason this error message is *ever* displayed is if the path to WebKit.app contains a colon.  In the Finder these paths will appear to have a "/" character in them, but at the Unix-level it will be displayed as ":".  The code that takes care of this is:

    if ([frameworkPath rangeOfString:@":"].location != NSNotFound ||
        [pathToEnablerLib rangeOfString:@":"].location != NSNotFound)
        displayErrorAndQuit(@"Unable to launch Safari",
                            @"WebKit is located at a path containing an unsupported character.  Please move WebKit to a different location and try again.");

[Adam Lounds]

Webkit.app was on the desktop, in /Users/adam/Desktop/Webkitbroken.app. I can launch it from terminal with "open /Users/adam/Desktop/WebKitbroken.app" and the error appears. A newly-downloaded webkit in the same dir works. Copying it to / and opening it from there still gives me the error (sudo cp -R /Users/adam/Desktop/Webkitbroken.app /; open /Webkitbroken.app ).

As I say, it only happens with the auto-updated one - Info.plist within the app dir has revision number 44111.

[Mark Rowe (bdash)]

If you still have that application around and it still reproduces the problem, can you please zip it up and email it to me so I can see if there's anything weird about it?