Search Issue Tracker
Fixed in 5.3.9
Votes
2
Found in
5.3.1p1
Issue ID
757642
Regression
Yes
[FMOD] Building stops with compilationIOException: Error creating standard error pipe
1. Open project "repro_757642.zip"
2. Build to iOS or standalone
3. Building will stop on compiling scripts with error
"Could not start compilationIOException: Error creating standard error pipe"
"Error: Cannot create FMOD::Sound instance"
4. Delete all audio files and building will succeed
Note: repro on both mono and il2cpp backend
Regression from 5.3.0f1
Comments (3)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph window icon is blurry and low quality when the Shader Graph is created using the Universal 2D template
- “Export HDRP Sky to Image” command error message does not indicate that Game view must be visible
- Adaptive Performance Settings Framerate field doesn't display the "supported without VSync" warning, when the field is collapsed in Build Profiles
- “MissingReferenceException”, “NullReferenceException” and GUI errors are spammed in the Console when selecting “Boris” GameObject in the Prefab field of the “Plunkah” GameObject in the “_IK” Sample scene
- "Upload Symbols Failed" is thrown when Archive validation is being done in Xcode
mpete
Apr 26, 2016 09:19
I had a similar problem. Converted a lot of sounds from Compressed in Memory to Streaming. Then Unity crashed during iOS export. Converting back to Compressed.. - all fine!
Nabren
Mar 29, 2016 17:48
Apparently can't edit my previous comment, so here is a new one:
So in my case this actually happened because we were using the Unity cache server and we had all of our audio files cached using Unity 5.2.4.
When upgrading to Unity 5.3.4, it didn't invalidate the assets on the cache server and downloaded the imported audio from the cache server and would break with the above error when trying to create a build.
I ended up selecting all audio files (you can multi-edit now!) changing a setting they all shared to something different and then back again, which seems to have forced a fresh import and fixed my issue.
Nabren
Mar 29, 2016 16:23
I have noticed it has something to do with the "preload audio data" flag on audio files. I turned this off and built successfully. I reverted that flag and it broke again.
I am not clear if this is due to using the cache server or not. As turning that flag off forced a re-import, but when I reverted the flag it imported the assets using the cache server again.