Skip to content
New issue

Have a question about this project?Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of serviceand privacy statement.We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audio Player from expo-av crashes in Android after playing 41 short audio clips #30790

Open
MichaelHabermasopened this issue Aug 2, 2024 · 3 comments
Labels
needs review Issue is ready to be reviewed by a maintainer

Comments

@MichaelHabermas
Copy link

Minimal reproducible example

https://github /MichaelHabermas/React-Native-Expo-Audio-Test-App

What platform(s) does this occur on?

Android

Where did you reproduce the issue?

in a development build, in Expo Go

Summary

Expected: The Audio player from expo-av continues to play audio clips as they are loaded and unloaded, without issue.

Happening: The Audio player from expo-av crashes after 41 serial audio clip plays (but only in Android. Not iOS, don't know about web). On checking the status with soundObj.getStatusAsync(), it returns this error: { "code": "E_AUDIO_NOPLAYER" }

Environment

expo-env-info 1.2.0 environment info:
System:
OS: Windows 11 10.0.22621
Binaries:
Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: AI-241.18034.62.2411.12071903
npmPackages:
expo: ~51.0.24 => 51.0.24
expo-router: ~3.5.20 => 3.5.20
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.3 => 0.74.3
react-native-web: ~0.19.10 => 0.19.12
Expo Workflow: managed

Expo Doctor Diagnostics

npx expo-doctor@latest
WARNING: We recommend using PowerShell or Bash via WSL 2 for development with Expo CLI on Windows. You may encounter issues using cmd.exe.

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check for issues with metro config
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that native modules do not use incompatible support packages
✔ Check for legacy global CLI installed locally
✔ Check that packages match versions required by installed Expo SDK
✔ Check that native modules use compatible support package versions for installed Expo SDK

@MichaelHabermas MichaelHabermas added the needs validation Issue needs to be validated label Aug 2, 2024
@expo-bot expo-bot added needs review Issue is ready to be reviewed by a maintainer and removed needs validation Issue needs to be validated labels Aug 2, 2024
@brentvatne
Copy link
Member

hi there!@alanjhughesis currently working on revamping expo-audio. he may be able to provide some context here, but otherwise we can validate that this does not occur on the upcoming new version

@thespacemanatee
Copy link
Contributor

@brentvatne@alanjhughesSorry to have to ask for ETAs on this sort of thing but the audio recording has been broken for us recently. Firstly, we had to migrate away from our own Audio Recorder toexpo-avdue to a recent update toexpo-modules-corebreaking something in our implementation. After migrating toexpo-av,we found the library to be unstable, with errors such as accessing the player from the wrong thread, being unable to reliably clean up recordings (it keeps complaining we have an instance still in memory), and crashing on callingsound.unloadAsyncon iOS. I could create an issue for each of those bugs but we would most likely have to migrate toexpo-audiosoon anyway, so we're just wondering what's the timeline on that, thank you very much!

@brentvatne
Copy link
Member

Firstly, we had to migrate away from our own Audio Recorder to expo-av due to a recent update to expo-modules-core breaking something in our implementation

can you elaborate on this? resolving this may be the easiest path forward right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs review Issue is ready to be reviewed by a maintainer
Projects
None yet
Development

No branches or pull requests

4 participants