Search Issue Tracker
Active
Votes
0
Found in
6000.0.33f1
6000.1.0a10
Issue ID
UUM-91571
Regression
No
“You may not pass in objects that are already persistent” error is thrown when entering the Play Mode and the "Active Input Handling" system was changed in a custom Build Profile
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Open the Build Profiles Window (Files > Build Profiles)
3. In the “New Android Profile 1” custom Build Profile, change “Active Input Handling” to a different value
4. In the pop-up window, agree to restart the Editor
5. Once the Editor is restarted, enter the Play Mode
6. Observe the Editor
Expected result: No errors are thrown
Actual result: “You may not pass in objects that are already persistent” error is thrown
Reproducible with: 6000.0.33f1, 6000.1.0a10
Could not test with: 2021.3.47f1, 2022.3.56f1 (Build Profiles are not available in this Stream)
Reproducible environment: MacOS 15.1.1 Intel, Windows 10 (user’s)
Not reproducible environment: No other environment tested
Workaround: Use the default Build Profile
Notes:
- The issue occurs:
each time the Play Mode is entered
when switching build profiles
regardless of the Active Input Handling system chosen
regardless of the platform of the custom Build Profile
- The issue is reproducible on a blank project
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crash when resetting Quality settings after adding "New Group" in Mipmap Limit Groups
- AndroidManifest.xml detects the “<” symbol between tags as invalid and outputs an "System.Xml.XmlException" error failing the build
- Lightmaps are darker than should be when they are generated through Lightmapper.BakeAsync in batchmode
- Crash on ScriptableBatchRenderer::GenerateBuiltInCBuffer when opening a project after adding HDRP Samples to a specific project
- ArgumentException is thrown and reference is missing when deserializing and using MultiColumnListView
Add comment