iOS - Audio only comes out internal speaker (ear speaker) when Prepare iOS for recording is set

I have both these checked/enabled:
7541032--931549--upload_2021-10-2_16-42-33.png

But since this bug below was fixed it seems to have introduced a new bug where the audio ALWAYS comes out of the internal speaker. I rolled back to Unity 2021.1.2 (before the bug fix) and the audio works correctly out of the normal speakers.

Unity Issue Tracker - [iOS] Microphone.Start() method invocation causes high ping spikes (unity3d.com)

5 Likes

Same bug here, is there any workaround for this?

Sound like a bug. If you can, please open a bug report. We will look into it.

Sorry and thank you!

@hlorenzo93 can you please log this, I’ve moved off this project.

I filed a report and was directed to Unity Issue Tracker - Sound is playing through the ear speaker if using "Force iOS Speakers when Recording" when "Prepare iOS for Recording" is on

Not sure if the bluetooth headphone bug is separate, but the issue was marked as not a regression (it is, we can’t upgrade until resolved)

1 Like

we also encountered this problem, when both are selected, the sound output only from earphone, unity 2022.2.7, is this a bug???

If you select both, the sound should play normally, but you can’t get this result This is a problem that spans several versions and has not been officially solved

2020.3.18f is the last version you can use both microphone and speaker… so this is the version we stay on

For visibility @The_Island , the issue was marked as fixed but is still broken: https://issuetracker.unity3d.com/is…ecording-when-prepare-ios-for-recording-is-on

And I assume you upgraded to 2022.2.0a17 and above to test the fix? I am away next week but I will let a note to the dev so he can check with you.

@marnsmith There seems to be something wrong with our tooling sometimes that is matching changesets to Unity releases. I’m sorry for the confusion this is causing.

It looks like these fixes are actually in 2020.3.38f1 (which is not out yet) and 2021.3.8f1 (which is out).

2 Likes

Thanks for your replies, I can confirm the fix in 2020.3.38f1.

1 Like