UnityRef is currently in early development. Some features may be incomplete and/or not functioning.

UNITYREF

Your Pit Stop For Solving ANYTHING in Unity

architecture

[Vivox] Critical Config Data Missing in DevOps Builds

Under Audit

cloud services

Unity 2021.3.x - Unity 6.1.x

Published Wed, Mar 11

Vivox configuration keys, such as server, domain, and issuer, are often missing in Unity Services DevOps builds, preventing the Vivox service from initializing correctly. This discrepancy arises because cloud build agents may not fully link to the Unity Cloud Project.

Issue

 In Unity Services DevOps builds, the Vivox service may fail to initialize due to missing configuration keys. Specifically, the com.unity.services.vivox.server, com.unity.services.vivox.domain, and com.unity.services.vivox.issuer configurations are found to be empty. This occurs because DevOps build agents do not establish the same Unity Cloud Project link as local builds, preventing automatic population of VivoxSettings from the dashboard. This absence renders the Vivox implementation unable to locate the correct environment for connection.

Experimental Fixes
  • Ensure the Unity Cloud Project is correctly linked within your Unity Services DevOps project settings.
  • Confirm that all required Unity Services and Vivox packages are installed and up-to-date in your project’s Package Manager.
  • Explore Cloud Build environment variables for a method to inject configuration values directly, rather than through IConfigurationProvider.

Editor's Note:

The above fixes have not been verified by our audit team yet. They are provided exclusively for your own technical research. We recommend creating a backup of your project before proceeding with any attempts. Utilize at your own discretion!

Related Posts Haven't quite found a solution to your problem? We think these posts might help you.

Content inspired by a Unity discussion post.