Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2020.1
2020.1.0b15
2020.2
Issue ID
1261662
Regression
No
[Remote Config] Multiple windows turn black on minimizing Config window after switching variant type in Rule information
Multiple windows turn black on minimizing a window after switching variant type in Rule information. Refer the attached video
Steps to reproduce:
1) Create a new project
2) Window > Package Manager > Install Remote Config
3) Create Environment > Add rule
4) Dock Remote Config Window > Maximize window
5) Change variant > Minimize window
Actual result: Multiple windows turn black on minimizing Remote Config window
Expected result: Windows should not turn black on minimizing Remote Config window
Occurring on: 2020.2.0a17 and 2020.1.0b16 with Remote Config package version 1.2.3, 1.2.2, 1.2.1
Note: Variant type in Remote Config window was introduced in 1.2.1
Environment: Seen on Windows and Mac
Stack trace:
OnGUIDepth changed: was 2 is 3. Event type was 7
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Unity.RemoteConfig.Editor.RemoteConfigWindow:OnDestroy () (at Library/PackageCache/com.unity.remote-config@1.2.1/Editor/RemoteConfigWindow.cs:457)
UnityEditor.GenericMenu:CatchMenu (object,string[],int)
OnGUIDepth changed: was 3 is 4. Event type was 7
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Unity.RemoteConfig.Editor.RemoteConfigWindow:OnDestroy () (at Library/PackageCache/com.unity.remote-config@1.2.1/Editor/RemoteConfigWindow.cs:457)
UnityEditor.GenericMenu:CatchMenu (object,string[],int)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Rules editing has been removed from the package, so this will not be an issue.
We are currently evaluating which versions to backport this removal to, but it is available already in version 3.0.x