Spatial Audio: <<<< FigAudioSession(AV) >>>> signalled err=-19224 at <>:612

Thanks so much for the post. Can you provide as much information as possible so the visionOS engineers can take a look about the error in the Audio Session including the code you are using to reproduce the issue.

Is it happening on unmodified sample code on a physical Vision Pro?

As a developer, you are likely mirroring your Vision Pro to your Mac while debugging with Xcode? When you mirror your screen, visionOS attempts to route audio to the AirPlay receiver (your Mac). The spatial audio engine cannot render 3D audio over a standard stereo AirPlay connection, causing FigAudioSession to crash or throw the -19224 error.

Can you provide information is you are AirPlay mirroring from the Vision Pro Control Center. Have you tried the device by itself? How are you using the audio session? Can you post the code? If another app recently used the audio session, or if the system defaulted to .ambient? Add the AVAudioSession.sharedInstance().setCategory(.playback) code.

All those details will help engineers figure it out.

Albert
  Worldwide Developer Relations.

Unmodified code from here https://developer.apple.com/documentation/visionos/playing-spatial-audio-in-visionos

I am not mirroring my screen.

No sound connected to Xcode and I get the error in the log.

No sound if my VisionPro is not connected to Xcode.

I have a Gen 1 Vision Pro and using Xcode 26.4.1

I have added the AVAudioSession.sharedInstance().setCategory(.playback) code. It makes no difference.

Is there a current sample app that I could try that should work with iOS 26?

I've been blocked on this for weeks.

Hey [@Just Looking](https://developer.apple.com/forums/profile/Just Looking),

I just tried this sample code project on visionOS 26 and on visionOS 27.0 Beta 1. I saw this error message as well, however, the app functioned on both versions. I heard a difference in sound as I moved the application far away and close to myself. Are you experiencing any functional issues, or are you just noting the issue by watching the console? I believe you might be able to ignore this system level log.

I'd greatly appreciate it if you could open a bug report with this information and I can work with the teams to resolve this error log message. Please post the FB number here once you do.

Bug Reporting: How and Why? has tips on creating your bug report.

Thanks,
Michael

Michael,

Discovered that something in my setup sets my master volume down to 0. This appears to be a separate control than what the knob sets. No idea what is the root cause of that, but if I go in and increase the volume from there I can hear the sounds. So the error was a red herring.