[!IMPORTANT]
Photon Voice and Photon Fusion are already set up as part of the private repository MirageXR-Conciliator, so configuration is not normally required -- only when there are package updates, as part of updating, configuration files are overwritten and they need to be reconfigured.

Any updates to the Photon packages Fusion and Voice will have to be done via the private Conciliator repo. When updating, typically the configuration assets are overwriten, requiring re-configuration.

The best way to update Fusion is:

• delete the old library, clearing out the Packages/com.wekit-ecs.MirageXR-Conciliator/Fusion folder
• import the package (this will likely overwrite some additional libraries in the conciliator in the PhotonLibs folder - Websocket and NetStandard2.0)
• move all files under Photon/Fusion down to Packages/com.wekit-ecs.MirageXR-Conciliator/Fusion

The last package update for Photon Voice was straightforward:

• import the package, and it updates all files
• patch Photon/PhotonVoice/PhotonVoiceLibs/VisionOS/device/Libopus_egpv and select CPU > ARM64 under Platform settings
• patch Photon/PhotonVoice/PhotonVoiceLibs/VisionOS/simulator/Libopus_egpv and select CPU > X64 under Platform settings

The assets to configure are two, network project config (build / runtime config) and photon app settings (API keys). Additionally, it might require to update the API keys in PhotonServerSettings.asset

Network Project Configuration

NetworkProjectConfig.fusion

Under Assemblies To Weave, re-add MirageXR as last item.

Check if the settings are still the same:

Photon App Settings

PhotonAppSettings.asset

Set AppIdFusion and AppIdVoice to the API keys from the dashboard (use the live keys, not the develop keys for builds)

Errors that can be ignored

Because the Photon packages are moved to the Conciliator package in Packages/com.wekit-ecs.MirageXR-Conciliator/ (and thus not at their original location in the Assets/ folder), a Photon editor runtime routine throws an errors that can safely be ignored (it is trying to write the settings file). The routine writes the settings out to an Application.DataPath location, which in editor is Assets/, but in on other targets is somewhere in a more accessible path, so far it does not seem to affect builds.

Would be nice if the Photon packages would fix this at some point.