[Vivox] Critical Config Data Missing in DevOps Builds
Under Audit
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.
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.
- Ensure the
Unity Cloud Projectis correctly linked within yourUnity Services DevOpsproject settings. - Confirm that all required
Unity ServicesandVivoxpackages are installed and up-to-date in your project’sPackage Manager. - Explore
Cloud Buildenvironment variables for a method to inject configuration values directly, rather than throughIConfigurationProvider.
Editor's Note:
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.