Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0a5
Issue ID
900114
Regression
Yes
InvalidOperationException and Assert thrown when the Asset Store window is visible in 2017.1.0b1 editor
Steps to reproduce:
1. Open empty project
2. Open Asset Store window
3. Switch between A$ and Game View OR click 'Play' while the A$ window is visible
4. Following errors will be thrown in the console:
> InvalidOperationException: Operation is not valid due to the current state of the object
> Assertion failed: Assertion failed on expression: '!dest.m_MultiFrameGUIState.m_NamedKeyControlList'
Reproducible with: 2017.1.0b1, 2017.1.0a5 (only throws the Exception, Assert is not thrown in a5)
Doesn't reproduce with: 5.6.0f3
Comments (2)
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
DincaAlin
Dec 17, 2017 20:07
I have 2017.2.0f3 and it still appear, so is not fixed.
tswierkot
Nov 02, 2017 11:10
Not fixed - still occurs in 2017.2.0f3