Deploying and Optimizing UG for Meta Quest

How did you structure your build pipeline in Unity to support efficient VR deployment?

MM: The team uses Unity Version Control so members can work on branches concurrently and manage their own changes. We use main, live, dev, beta, and feature branches. Unity Version Control keeps the team in sync and makes it easy to push and pull changes.

For builds and deployments, we use Unity Hub to build Android Package Kits (APK) and Meta Quest Developer Hub to deploy them in minutes. From there, we promote or demote builds and release them to players or alpha testers.

Conrad Dugger: At launch, especially as UG gained traction, we needed visibility into what was happening at scale. The Editor could not simulate every scenario, so we uploaded debug symbols and used a Mixpanel dashboard to monitor errors continuously. We still check it daily and after every patch to make sure issues do not return. This helps us resolve issues before they affect players.

MM: We can access crash symbols directly through Meta, so we did not need a custom solution. Unity lets us build and upload them to Meta in the same or a separate step. For errors and exceptions that crash symbols do not capture, we built custom tools that rate-limit uploads per player and include full stack traces.

We review those reports alongside user history to pinpoint what users were doing before an event occurred. Mixpanel aggregates events so teams can build queries, flows, and visualizations, helping us spot and fix issues quickly.