To test the build manifest functionality locally, name your file Unit圜 (but don’t commit this file to your project’s Assets/Unit圜loud/Resources folder in your code repository, because it might interfere with the Unity Cloud Build manifest file). The manifest TextAsset, called Unit圜loudBuildManifest.json, is written to the Assets/Unit圜loud/Resources folder.
The name of the build target that was built. The version of XCode used to build the project (iOS only). The version of Unity that Unity Cloud Build used to create the build. The bundleIdentifier configured in Unity Cloud Build (iOS and Android only). The UTC timestamp when the build process was started. The Unity Cloud Build “build number” corresponding to this build. The build manifest contains the following values: Value: Builds can now be downloaded as Artifacts in the Actions tab. Example: - uses: actions/upload-artifactv2. By default, Builder outputs it's builds to a folder named build.
This is stored as a game resource, accessible via Resources.Load(). To do this it is recommended to use Github Actions official upload artifact action after any build action. The Unity Cloud Build manifest is provided as a JSON formatted TextAsset. To help facilitate this, Unity Cloud Build injects a “manifest” into your game at build time, so that this key data can be accessed later at runtime. Unity Cloud Build monitors your source control repository (e.g. Information like the name and number of the build is very useful when reporting bugs or tracking analytics. It’s often useful for your game’s run-time code to know key information about the build itself.
0 kommentar(er)
