Search Issue Tracker
Fixed in 2019.3
Fixed in 2018.3, 2019.1, 2019.2
Votes
0
Found in
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1114593
Regression
Yes
Facebook Gameroom target uses Standalone target player settings and fails in some cases
Steps to reproduce:
1. Create a new project
2. Switch to Facebook target
3. Set Scripting backend to IL2CPP in Standalone target settings
4. Build Facebook build
Expected result: build uses mono as it is the only available in Facebook gameroom settings
Actual result:
2018.3: build finishes, but following error is thrown:
FileNotFoundException: C:\Unity\Instalations\2018.3\2018.3.0a1_d734fac073ec\Editor\Data\PlaybackEngines\Facebook\Variations\win64_nondevelopment_il2cpp\WindowsPlayer.exe does not exist
2019.x build fails with error:
UnityException: Build target 'StandaloneWindows64' not supported
Reproduced on 2018.3.0a1, 2018.3.3f1, 2019.1.0a14, 2019.2.0a2
Not reproduced on 2017.4.18f1
Regression introduced in 2018.3.0a1
Notes:
- Setting scripting backend is not necessary it just makes it more evident that it uses it
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Sub Emitter particle's width is twice its height when Separate Axes in the Size over Lifetime module is enabled and set to 1
- Animation does not play correctly when Optimized Game Object functionality is used and a Child GameObject is added to bone
- An object created via "Create Empty Child" of Hierarchy panel in Prefab Mode is always a child of the main prefab
- [VCS] Version Control window could use a search field to filter down contents
- [VCS] Importing .unitypackage with version control enabled fails
Resolution Note (fix version 2019.3):
It won't be fixed for 2019.3, where Facebook Gameroom platform is removed. But the bug will be fixed for 2018.3, 2019.1, 2019.2