Search Issue Tracker
Fixed in 2018.1.X
Votes
2
Found in
5.4.4f1
Issue ID
915971
Regression
No
[iOS] Minimizing app during its initialization breaks the sound, error "FMOD failed to initialize the output device" displayed
Steps to reproduce:
1. Open user's attached project
2. Build "Test" scene to iOS platform
3. In Xcode, Build and Run
4. When app starts launching in iOS, instantly click home button
5. Notice that debug console has this error: "FMOD failed to initialize the output device, attempting to initialize the null output."
6. Bring back the app to foreground
Expected results: No error, sound plays
Actual results: Error mentioned in step 5, no sound playing
Reproduced on: 5.4.5p1, 5.5.4p1, 5.6.2f1, 2017.1.0f1, 2017.2.0b1
Notes:
- Issue reproduces with and without developer mode enabled in build settings
- Opening the app through iOS device instead of Xcode does not reproduce the issue
___
This bug cannot be completely fixed. FMOD initialization failed when an application is being sent to the background. With this fix, FMOD would be automatically reinitialized after bringing an application back to the foreground. However sounds will not be restarted, unfortunately, this is simply impossible with current FMOD based architecture. Developers should subscribe to the OnAudioConfigurationChanged event to restore sounds manually.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment