NullPointerException in unregisterNoisyReceiver about audio_session HOT 11 CLOSED

Hi @ened , thanks for the report. I will look into it.

from audio_session.

Can you try the latest commit? Tracing the logic that could cause this, I would guess your app has at least 2 FlutterEngines/isolates, and the second one was shutdown, followed by a loss of audio focus. The other possibility (which doesn't seem to be the case here) is that the first isolate was shut down. The latest commit should hopefully handle both situations, although since I wasn't actually able to reproduce the error, hopefully you can try it out and let me know how it goes.

from audio_session.

2 isolates, correct - either of which can be stopped at any time and started at any time (Android Activity + Foreground Service).
This is happening in our production App - appreciate if you can cut a new release for this.

from audio_session.

Just to confirm, did the latest commit work for you?

from audio_session.

Note that I would normally want to do more testing before publishing a new release with a substantial change to the logic like this. However, if you are happy with that commit, I would recommend until then that you pin your app to that specific commit as follows:

dependencies:
  audio_session:
    git:
      url: https://github.com/ryanheise/audio_session.git
      ref: e40d76dcda985fea4a42c06839f30f37af1c7781

(You may need dependency_overrides if you are also using other plugins that use audio_session such as audio_service or just_audio.)

from audio_session.

@ryanheise looks good - thank you for your help. I've tested this on our app locally and did not observe any crashes.

from audio_session.

Great! I'll probably do the next release this coming weekend. If you encounter any further issues during that time, let me know and I'll try to address them before the release.

from audio_session.

@ryanheise Hi are you still planning a release?

from audio_session.

Sure, I can do that now; I assume you didn't run into any further crashes with this commit?

from audio_session.

Yes looks good so far. We will pass the release candidate to our testers this week - will report if more issues are found.

from audio_session.

Thanks, I also haven't run into any issues on my end so I've published 0.0.11.

I'll close this for now but if you do run into further issues, do let me know and I will reopen.

from audio_session.