I'm seeing that the getFingerprintHashForPlatformAsync in the github action return a different runtime version than what gets determined when createEASBuildAsync is triggered in the same action. This is not occurring when I pass in "development" for profile and branch, but does occur when passing in "preview".
Expected behavior
These two internal Github action functions should produce the same runtime output as they have access to the same data regardless of what profile or branch get's passed in.
Actual behavior
getFingerprintHashForPlatformAsync returns a different runtime version versus the one attached to the build kicked off by createEASBuildAsync.
Additional context
The update that gets trigger does match what gets returned from getFingerprintHashForPlatformAsync.
As a side note, Is there a way to see the fingerprint sources output from `createEASBuildAsync'?
Description of the bug
I'm seeing that the
getFingerprintHashForPlatformAsyncin the github action return a different runtime version than what gets determined whencreateEASBuildAsyncis triggered in the same action. This is not occurring when I pass in "development" for profile and branch, but does occur when passing in "preview".Expected behavior
These two internal Github action functions should produce the same runtime output as they have access to the same data regardless of what profile or branch get's passed in.
Actual behavior
getFingerprintHashForPlatformAsyncreturns a different runtime version versus the one attached to the build kicked off bycreateEASBuildAsync.Additional context
The update that gets trigger does match what gets returned from
getFingerprintHashForPlatformAsync.As a side note, Is there a way to see the fingerprint sources output from `createEASBuildAsync'?