Issue running parallel audio files

Question

I am trying to set up a XIB with two buttons to play audio - one for music and one for narration.  Files for music are stored in a music directory within the resources bundle.  Files for narration (with names different than the music file names) are stored in a narration directory within the same resources bundle.
When I installed just the music portion, it played fine on both the Simulator and on my iPad.
After I added very parallel code for the narration portion, things got strange.
     IN THE SIMULATOR
          The NSLog for the music path was unchanged and the music played.
          The NSLog for the narration path showed NULL and obviously failed - OSStatus -50  
     ON THE IPAD (with no change of code)
          The NSLog for the music path now showed NULL and also failed - OSStatus -50
          The NSLog for the narration path showed NULL and failed - OSStatus -50  
I also commented out the code related only to the music path, but that made no change in the effect on the narration path.
A view of the essential code follows.  What do I need to do different to get the narration path to work?  And to keep the music path working on the iPad?
- (void)viewDidLoad
    [super viewDidLoad];
NSString *musicTrack = . . .; (defined here)
NSString *musicDirectory = . . .; (defined here)
NSString *narrationTrack = . . .; (defined here)
NSString *narrationDirectory = . . .;    (defined here)
NSString *resourcesBundlePath = [[NSBundle mainBundle]pathForResource:@"Resources" ofType:@"bundle"];
NSBundle *resourcesBundle = [NSBundle bundleWithPath:resourcesBundlePath];
NSString *pathToAudioMusicFile = [resourcesBundle pathForResource:musicTrackofType:@"m4a" inDirectory:musicDirectory];
NSLog ( @"Music path: %@", pathToAudioMusicFile);
// Now use same resourcesBundle for the Audio Narration Player
NSString *pathToAudioNarrationFile = [resourcesBundle pathForResource: narrationTrackofType:@"m4a" inDirectory:narrationDirectory];
NSLog ( @"Narration path: %@", pathToAudioNarrationFile);

Answer 1

This really sounds like a question for the Developer Forums.