Note that there are some explanatory texts on larger screens.

plurals
  1. POthis app was developed and works fine under ios 5.0, but crashes under ios 4.3
    text
    copied!<p>I developed an iPhone app under iOS 5.0, and it works fine. But when it comes to iOS 4.3(Base SDK = latest iOS 5.0, compiler = Apple LLVM 3.0, Deployment Target = iOS 4.3), it crashes after launching.</p> <p>The output around crash point looks like:</p> <pre><code>2011-12-06 16:25:08.177 FMWei[466:c203] -[AVAudioSession setMode:error:]: unrecognized selector sent to instance 0x706a7f0 2011-12-06 16:25:08.181 FMWei[466:c203] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[AVAudioSession setMode:error:]: unrecognized selector sent to instance 0x706a7f0' </code></pre> <p>It looks like that <code>AVAudioSession</code> doesn't have a member function <code>setMode:error:</code> while I invoked it. But what's strange is that I didn't invoke a function whose name is <code>setMode:error:</code>. The code about audio processing is:</p> <pre><code>audio_session = [[AVAudioSession sharedInstance] retain]; audio_session_err = nil; [audio_session setCategory: AVAudioSessionCategoryPlayAndRecord error:&amp;audio_session_err]; NSLog(@"!"); UInt32 audioRouteOverride = 1; AudioSessionSetProperty(kAudioSessionProperty_OverrideCategoryDefaultToSpeaker,sizeof (audioRouteOverride),&amp;audioRouteOverride); UInt32 allowMixing = 1; AudioSessionSetProperty(kAudioSessionProperty_OverrideCategoryMixWithOthers, sizeof(allowMixing), &amp;allowMixing); if (audio_session_err) { NSLog(@"audioSession: %@ %d %@", [audio_session_err domain], [audio_session_err code], [audio_session_err description]); } else { audio_session_err = nil; [audio_session setActive:YES error:&amp;audio_session_err]; if (!audio_session_err) NSLog(@"audio session is activated successfully"); } </code></pre> <p>Please help me figure out why it crashes under iOS 4.3 with the strange error. Thank you!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload