Open Radar

 
Summary:
I have a script to generate localized XIB files from my English XIBs and .strings files. The script has been run the first time since updating to Xcode 5 (5.0.1) and started complaining that it can't find the xib I have specified. Interestingly not always, after wild navigation in the Terminal and coming back to the original directory the script worked – sometimes. Upon checking I found something very weird with "ibtool":

Steps to Reproduce:
1. Install Xcode 5
2. Create an arbitrary XIB file and name it "View.xib"
3. Open Terminal and navigate to the folder that contains your new XIB
3. Execute "ibtool --write Test.xib View.xib"

Expected Results:
A XIB file named Test.xib is created and looks the same as View.xib

Actual Results:
"ibtool" can't find my XIB file (FVC_APGAR.xib) which is right there, Bash output:

$ ls -ahl
total 56
drwxr-xr-x   5 pp  staff   170B Oct 18 08:22 .
drwxr-xr-x  11 pp  staff   374B Oct 18 08:12 ..
-rw-r--r--   1 pp  staff   884B Oct 17 20:44 FVC_APGAR.strings
-rw-r--r--   1 pp  staff    17K Oct 18 08:14 FVC_APGAR.xib
-rw-r--r--   1 pp  staff   442B Oct 17 20:44 FVC_APGAR.xib.strings
$ ibtool --write FVC_TEST.xib FVC_APGAR.xib
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.ibtool.errors</key>
	<array>
		<dict>
			<key>description</key>
			<string>The file “FVC_APGAR.xib” couldn’t be opened because there is no such file.</string>
			<key>failure-reason</key>
			<string>The file doesn’t exist.</string>
			<key>underlying-errors</key>
			<array>
				<dict>
					<key>description</key>
					<string>The operation couldn’t be completed. No such file or directory</string>
					<key>failure-reason</key>
					<string>No such file or directory</string>
				</dict>
			</array>
		</dict>
	</array>
</dict>
</plist>


Version:
Xcode 5.0.1 (5A2034a), OS X 10.9 GM (13A598)

Notes:


Configuration:
I have no idea why the script sometimes goes through without complaining and sometimes not. No difference if the Terminal is being restarted, but the above error definitely doesn't make sense in any circumstance.

Attachments: