Search Issue Tracker
Active
Under Consideration for 2.7.X
Votes
0
Found in [Package]
2.7.3
Issue ID
ADDR-4078
Regression
Yes
[Addressables] Error "Destroy may not be called from edit mode! Use DestroyImmediate instead." is thrown when exiting the Play Mode
Reproduction steps:
1. Open the attached “IN-116318” project
2. Open the Package Manager window (Window > Package Manager)
3. Make sure a custom Addressables package isn’t used
4. Open the Addressables Groups window (Window > Asset Management > Addressables > Groups)
5. Create a new build (Build > New Build > Default Build Script)
6. Enter the Play Mode, pause and unpause it
7. Observe the Console window or the Editor.log
Expected result: No errors are thrown
Actual result: “Destroy may not be called from edit mode! Use DestroyImmediate instead.” is thrown
Reproducible with: 1.22.2 (2022.3.66f1, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1), 1.27.0 (2022.3.66f1), 2.7.3 (6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1)
Not reproducible with: 1.21.21 (2022.3.66f1, 6000.0.58f1, 6000.2.6f1, 6000.3.0b3, 6000.4.0a1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Repeat step 6 in-case the error does not show up
- The error is too big, so it is added in the internal comments
- A workaround is provided in the internal comments, by changing the Addressables “AtlasSpriteProvider.cs” code
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Depth of Field doesn't apply correctly to Canvas UI when it is set to World Space Render Mode
- Crash on GetElementMapKey when "None" is assigned to a field with binding path "m_GameObject"
- Stereoscopic skybox renders as monoscopic when using Multi-pass render mode in XR plugin while using URP
- Parameterized Tests with ValueSource fail when supplied parameter is an System.Object
- Error Message "Broken text PPtr in file" is not informative enough to locate the problematic asset
Add comment