Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.3.X, 2019.1.X, 2019.2.X
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
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