Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.45f1
2021.3.19f1
2022.2.8f1
2023.1.0b5
2023.2.0a3
Issue ID
UUM-27770
Regression
No
[iOS] Wired headphones microphone is not recognised when listing all connected devices
Steps to reproduce:
# Open the attached project
# In the Build Settings switch to the iOS Platform
# In the Edit > Project Settings > Player > Other Settings make sure that the setting "Prepare iOS for Recording" is enabled
# Build and Run
# Connect wired headphones to the device
# Press "List" button in the application
# Open "In Game Debug Console" from the right side and observe listed devices
*Expected:* Both built-in and wired headphones microphones are listed
*Actual:* Only built-in microphone is listed
Reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.8f1, 2023.1.0b5, 2023.2.0a3
Reproducible with devices:
- VLNQA00352 - iPhone 12 Pro (MGML3ET/A), CPU: A14 Bionic, GPU: Apple designed, OS: 16.2
- VLNQA00258 - iPhone Xs Max (MT502ET/A), CPU: A12 Bionic, GPU: Apple designed, OS: 13.2
Notes:
- When wired headphones are connected, audio is recorded only using a wired headphones microphone, no matter what option is selected to record (Start-1/End-1 is for built-in microphone, Start-2/End-2 is for external device microphone)
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.