特定通知音效播放（无视静音）：开发环境正常，生产环境失效

It’s a super common gotcha when audio playback works flawlessly in debug but falls flat in production—let’s break down the most likely issues and fix them step by step:

1. Verify Background Audio Entitlement Configuration #

The #1 culprit here is usually missing background audio permissions in your production build. Even if you set the correct audio session category, iOS will block playback (especially in silent mode or background) if this entitlement isn’t properly configured:

• Open your project in Xcode, navigate to the Signing & Capabilities tab.
• Add the Background Modes capability, then check the box for Audio, AirPlay, and Picture in Picture.
• If you prefer manual plist editing, add this to your Info.plist:

  <key>UIBackgroundModes</key>
  <array>
      <string>audio</string>
  </array>
  

Debug builds sometimes bypass strict entitlement checks, but production builds enforce this rule rigidly.

2. Optimize AVAudioSession Setup & Error Handling #

Your current setup in didFinishLaunchingWithOptions is a good start, but it’s often too early (the session might get deactivated by system processes later) and lacks actionable error handling. Here’s an improved approach:

• Create a reusable method to configure the audio session right before you need to play the sound (e.g., the moment the notification arrives), not just at app launch:

  - (void)prepareAudioSessionForPlayback {
      AVAudioSession *session = [AVAudioSession sharedInstance];
      NSError *error = nil;
  
      // Set Playback category with options to ensure audio plays over silent mode
      BOOL categorySuccess = [session setCategory:AVAudioSessionCategoryPlayback
                                        withOptions:AVAudioSessionCategoryOptionInterruptSpokenAudioAndMixWithOthers
                                              error:&error];
      if (!categorySuccess) {
          NSLog(@"Audio session category setup failed: %@", error.localizedDescription);
          return;
      }
  
      // Activate the session with proper options to notify other apps
      BOOL activateSuccess = [session setActive:YES
                                     withOptions:AVAudioSessionSetActiveOptionNotifyOthersOnDeactivation
                                           error:&error];
      if (!activateSuccess) {
          NSLog(@"Audio session activation failed: %@", error.localizedDescription);
      }
  }
  

• Call this method immediately before triggering your sound playback when the notification comes in. This ensures the session is active and ready exactly when you need it.

3. Check for Production-Specific Code/Resource Issues #

• Double-check if your sound playback code is wrapped in #ifdef DEBUG macros—this would accidentally disable it in production builds.
• Verify that your audio file is included in the production target: Select the audio file in Xcode, open the File Inspector, and make sure the correct target is checked under Target Membership. Missing resources will silently fail to play in production.

4. Handle iOS Version Compatibility & Session Interruptions #

• For iOS 13+, register for the AVAudioSessionRouteChangeNotification to reactivate the session if it’s interrupted by another app (like a phone call):

  [[NSNotificationCenter defaultCenter] addObserver:self
                                           selector:@selector(handleAudioRouteChange:)
                                               name:AVAudioSessionRouteChangeNotification
                                             object:nil];
  

  Then implement the handler to re-prepare the session when needed:

  - (void)handleAudioRouteChange:(NSNotification *)notification {
      NSDictionary *userInfo = notification.userInfo;
      AVAudioSessionRouteChangeReason reason = [userInfo[AVAudioSessionRouteChangeReasonKey] integerValue];
      if (reason == AVAudioSessionRouteChangeReasonOldDeviceUnavailable) {
          // Reactivate session after route change
          [self prepareAudioSessionForPlayback];
      }
  }
  

• Stick to modern AVAudioSession APIs (avoid deprecated methods like setCategory:error: without options, especially for iOS 10+).

5. Debug Production Builds #

• Use TestFlight or an Ad Hoc build to reproduce the issue on a physical device.
• Connect the device to Xcode, open Window > Devices and Simulators, select the device, and view the Console to capture any audio-related errors when the notification is received. This will help you pinpoint if the session is failing to activate or if the sound file is missing.

内容的提问来源于stack exchange，提问作者Chronisch