just_audio：首次播放正常，返回重进后音频源为null无法播放求助

Possible Causes #

• Player Instance Disposal: When you pop the page with Navigator.pop(), if your page's state disposes the justAudioPlayer in its dispose() method, the player instance is destroyed. When re-entering the page, you might create a new player but forget to reassign the audio source.
• Missing Reinitialization: The code that sets up the ProgressiveAudioSource only runs once (e.g., in initState() for the first page load) and doesn't trigger again when the page is recreated after popping back.
• Rushed Playback Trigger: You might be calling play() immediately on re-entry without first loading the audio source, leading to the player being in an idle state with a null source.

Solutions #

1. Fix Player Lifecycle Management #

If you want to retain player state across navigations, avoid disposing the player when the page is popped. Use a singleton or state manager to keep the player instance alive at a higher level:

// Singleton player instance
class AudioPlayerManager {
  static final AudioPlayer instance = AudioPlayer();

  // Call this only when the app exits
  static void dispose() => instance.dispose();
}

Use this singleton in your page instead of creating a new player each time—this way, the player and its audio source stay alive even when you pop the page.

2. Reinitialize Audio Source on Page Load #

If you prefer a new player instance per page load, ensure you re-set the audio source every time the page initializes. Example in initState():

late AudioPlayer justAudioPlayer;
String audioFilePath = "path/to/your/audio/file"; // Fetch this path each time the page loads

@override
void initState() {
  super.initState();
  justAudioPlayer = AudioPlayer();
  _loadAndPlayAudio();
}

Future<void> _loadAndPlayAudio() async {
  try {
    final source = ProgressiveAudioSource(Uri.parse(audioFilePath));
    await justAudioPlayer.load(source);
    await justAudioPlayer.play();
  } catch (e) {
    print("Error loading audio: $e");
  }
}

@override
void dispose() {
  justAudioPlayer.dispose(); // Dispose only when the page is permanently removed
  super.dispose();
}

Make sure audioFilePath is fetched fresh each time the page loads—don't rely on a cached value that might be cleared when popping.

3. Avoid Premature Playback Calls #

Never call play() before loading the audio source. Always load the source first, wait for it to be ready, then trigger playback. This prevents the player from being stuck in an idle state with a null source.

4. Check State Persistence #

If using state management (like Riverpod or Provider), ensure the audio source path and player state are persisted across navigations. For example, use a StateNotifier to hold audio source info so it isn't lost when popping the page.

Additional Checks #

• Verify the audio file path is still valid on re-entry (permissions changes are unlikely if it worked the first time, but worth confirming).
• Ensure no code resets the justAudioPlayer instance or its audio source when the page is popped.

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