chore: Added PlayStation and Xbox as build targets for integration tests#2519
chore: Added PlayStation and Xbox as build targets for integration tests#2519bitsandfoxes wants to merge 1 commit intochore/follow-up-switchfrom
PlayStation and Xbox as build targets for integration tests#2519Conversation
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. This PR will not appear in the changelog. 🤖 This preview updates automatically when you update the PR. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| { | ||
| Debug.Log("Builder: Building Xbox Series X|S IL2CPP Player"); | ||
| BuildIl2CPPPlayer(BuildTarget.GameCoreXboxSeries, BuildTargetGroup.GameCoreXboxSeries, BuildOptions.StrictMode); | ||
| } |
There was a problem hiding this comment.
Xbox target naming mismatch across tooling
High Severity
The new Xbox path uses the platform identifier GameCoreScarlett in PowerShell and plugin meta generation, but the Unity build uses BuildTarget.GameCoreXboxSeries/BuildTargetGroup.GameCoreXboxSeries. If Unity treats these as distinct platform identifiers, the copied native plugin can be excluded from the build or the build can target the wrong platform.
Additional Locations (2)
1 participant
Following the book on what we did for Switch in #2509
#skip-changelog