• axmol version: all versions up to 2.5
• devices test on: Samsung Galaxy S10 (Android 12), Pixel 4a 5G (Android 14), Pixel 8 (Android 15)
• developing environments
  • NDK version: r23c/r26d/r27c
  • Xcode version: 14.2+
  • Visual Studio:
    • VS version: 2022 (17.9+)
    • MSVC version: 19.39+
    • Windows SDK version: 10.0.22621.0+
  • cmake version:
    Steps to Reproduce:

Play music track (test tracks used are mp3, 2 to 4MB in size), and place app in the background. In one case, the app was brought back to the foreground approximately 10 hours later. No audio track could be heard, and attempting to play any further audio tracks of any size (from 20KB to several MB) resulted in invalid audio IDs being returned (-1/AudioEngine::INVALID_AUDIO_ID).

This only happens after the app is in the background for an extended period of time. Would it make sense to completely re-initialize the audio engine, such as by freeing then recreating it? Is this possible at the moment?

If there is no reliable way to detect when this happens, then having the ability to release and recreate the audio engine instance via a function call from the project would suffice. It would then be up to the developer to decide when to force this re-initialization.

Has anyone else experienced this issue at all in their application?