Search Issue Tracker
Won't Fix
Votes
2
Found in
2018.3.4f1
2019.1.0a1
2019.2.0a1
Issue ID
1123444
Regression
No
Inconsistent results between the Build Settings window and values, returned via selectedBuildTargetGroup and activeBuildTarget
How to reproduce:
1. Make sure that the Facebook/WebGL components are installed
2. Open user-submitted project (bugrep_1)
3. Open the custom window Dummy > Show Window
4. Follow the steps provided via the custom window
Expected result: Build Settings window settings and values, returned via script are consistent
Actual result: Build Settings window settings and values, returned via script vary
Reproducible with: 2018.3.5f1, 2019.1.0b2, 2019.2.0a4
Could not test with: 2017.4, 2018.3.0a1
Comments (1)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Gulliver
Feb 05, 2019 16:30
Missed 1.3. Bug #3.
After building the project for Facebook/WebGL target via BuildPipeline.BuildPlayer() -- build target group was reset from Facebook to WebGL.