Bug scmCommitId is not being set correctly in the Unity Cloud Build manifest duing the build.

Seen on iOS (we only build iOS)
VersionControl Perforce


Before and After build log comparison for manifest generation

Code (CSharp):

1. Before:
2. [2023-05-17T03:39:18Z - Unity] {"cloudBuildTargetName":"ios","buildNumber":2209,"scmCommitId":"201429","buildStartTime":"2023-05-16 20:19:57 -0700","projectId":"xxxx","bundleId":"xxxx","scmBranch":null,"xcodeVersion":"14.1","unityVersion":"2021.3.22f1"}
3. [2023-05-17T03:39:18Z - Unity] Creating Build Manifest text asset at Assets/__UnityCloud__/Resources/UnityCloudBuildManifest.json.txt
4. [
5.  
6. After:
7. [2023-05-18T03:38:27Z - Unity] {"cloudBuildTargetName":"ios","buildNumber":2211,"scmCommitId":null,"buildStartTime":"2023-05-17 20:22:34 -0700","projectId":"xxxx","bundleId":"xxxx","scmCommitId":null,"xcodeVersion":"14.1","unityVersion":"2021.3.22f1"}

The timing for this issue starting appears to correlate with a UCB service update made yesterday

Created an endpoint that returns the SDK values that the Unity Version can be configured for
2023-05-17 17:49:04
Added support for publishing visual studio solution files, added support for non-english branch names, updated CCD version to 11.15, general refactorings and stability improvements
2023-05-17 17:48:54


Although these builds are not failing, they cannot be uploaded to the app store due to incorrect versioning.

 

Hi @UnityPeterD
Thank you, we are still seeing this issue on-going - most recently in a build which completed 30 mins ago.
All our iOS builds from today still have this issue.
I've tried clean builds to see if it was a caching issue but that didn't resolve it.
We have been running two separate build automation projects today and both are having this issue.