Search Issue Tracker
Fixed
Fixed in 2020.3.45f1, 2021.3.18f1, 2022.1.25f1, 2022.2.4f1, 2023.1.0b1
Votes
0
Found in
2020.3.44f1
2021.3.17f1
2022.1.24f1
2022.2.3f1
2023.1.0a26
Issue ID
UUM-24666
Regression
No
Editor freezes when entering the Play Mode if Remote Config package is installed
Reproduction steps:
1. Open the “Rift Wars“ project
2. Open the Package Manager and observe that the “Remote Config” package is installed
3. Enter the Play Mode
Expected results: The Play Mode is entered
Actual results: The Editor freezes
Reproducible with: 3.2.2 (2020.3.44f1, 2021.3.17f1, 2022.1.24f1), 3.3.1 (2020.3.44f1, 2021.3.17f1, 2022.1.24f1, 2022.2.3f1, 2023.1.0a26)
Reproduced on: Intel MacOS 13.1
Notes:
The package is only installed, however, it is not used
Removing the package prevents the freeze from happening
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2023.1.0b1):
This bug was fixed in versions 4.x and above since they include the Remote Config Runtime Vlatko mentioned above. I think we can close this ticket.
Resolution Note (fix version 2022.2.4f1):
This bug was fixed in versions 4.x and above since they include the Remote Config Runtime Vlatko mentioned above. I think we can close this ticket.
Resolution Note (fix version 2022.1.25f1):
This bug was fixed in versions 4.x and above since they include the Remote Config Runtime Vlatko mentioned above. I think we can close this ticket.
Resolution Note (fix version 2021.3.18f1):
This bug was fixed in versions 4.x and above since they include the Remote Config Runtime Vlatko mentioned above. I think we can close this ticket.
Resolution Note (fix version 2020.3.45f1):
This bug was fixed in versions 4.x and above since they include the Remote Config Runtime Vlatko mentioned above. I think we can close this ticket.