Inconsistent status updates on Android compared to iOS

[0minKoh]

I encountered an issue where status updates behave inconsistently on Android compared to iOS using the example code provided on the official package page

Reproduction steps:

1. I implemented the statusListener as follows to track and print the status changes:

void statusListener(String status) {
    print("status: $status");
    setState(() {
      lastStatus = status;
    });
  }

2. Testing on an iOS device, the status changes work as expected and print clearly in the console:

flutter: status: listening
...
flutter: status: done

3. However, when testing on an Android emulator, I observed an extra "notListening" status and duplicate "done" status in the output:

I/flutter (11189): status: listening
...
I/flutter (11189): status: notListening
I/flutter (11189): status: done
I/flutter (11189): result: SpeechRecognitionResult words: [SpeechRecognitionWords words: 네 물론이죠,  confidence: 0.8676231, SpeechRecognitionWords words: 네 물론이지요,  confidence: 0.89166784], final: true
I/flutter (11189): status: done

Expected behavior:

On Android, the status updates should behave similarly to iOS, where the sequence would be listening -> done without the extra notListening and duplicate done statuses.

Actual behavior:

On Android, the status output shows an unexpected notListening followed by two done statuses.
listening -> notListening -> done -> (ResultListener Executed) -> done

Additional Information:

Issue only observed on Android (tested on emulator: Pixel 7 Pro API 14 arm64-v8a, Android 14.0).
iOS status updates function as expected.
Please let me know if further details or logs are needed. Thank you for your assistance!

[sowens-csd]

Thanks for the very detailed issue report, this is helpful. I agree that the behaviour should be the same and it sure sounds like the Android behaviour isn't correct. I'll investigate.

[sowens-csd]

I haven't been able to reproduce this on a real device. I'm wondering if it is an artifact of the emulator. Can you reproduce?

I'm still not happy with the way that status updates are handled and am planning a revamp, partly to ensure that the done status is only sent after the last results are delivered but I'd like to know if duplicate status notifications are a problem.