IPhone SDK - files in wrong spot (was can't open file)

Question

Ok, so I figured out why I can't open my audio file, but it doesn't make any sense to me at all.
You see, if I place my file at the root of my file system, it reads it fine. This is odd, I would have guessed that the simulator would read files based on the bundle. This can't be right, how can I test? Here's my code:
CFStringRef fileString = (CFStringRef) [NSString stringWithFormat: @"test.caf"];
CFURLRef fileURL = CFURLCreateWithFileSystemPath (
kCFAllocatorDefault,
fileString,
kCFURLPOSIXPathStyle,
false
AudioFileID audioFileID;
OSStatus result = AudioFileOpenURL((CFURLRef) fileURL, kAudioFileReadPermission, 0, &audioFileID);
if (result != noErr) {
// lets try writing the file, see where it goes
char buf[8] = "1234567";
CFDataRef data = CFDataCreate (NULL, (const UInt8*)buf, 8);
long writeErr = noErr;
CFURLWriteDataAndPropertiesToResource(fileURL, data, nil, &writeErr);
NSLog(@"bad file open");
return ;
When I run this, the AudioFileOpen fails with a -43. When I catch this and then try to write to the file, I find that the file is created at my filesystems root, I get /test.caf with the contents "1234567" in it!
And, of course, if I delete that file and put my audio file there, then the AudioFileOpenURL works.
This is not useful.
Can anyone see what I'm doing wrong?
Thanks

Answer 1

Don't assume the current directory is anything sensible--construct an absolute path with -\[NSBundle pathForResource:ofType:\]. (After all, should the current directory be the sandbox's root, the application bundle, the Documents directory, or the tmp directory? I can come up with arguments for all four, but the app bundle's argument is probably the weakest.)