Search Issue Tracker
Fixed
Fixed in 1.21.17
Votes
0
Found in [Package]
1.21.15
Issue ID
ADDR-3503
Regression
No
Addressables.Release() throws ArgumentException when Play mode has been exited twice
Reproduction steps:
1. Open project “AddressablesReleaseIssue.zip”
2. Open the “SampleScene”
3. Go to “Window\Asset Management\Addressables\Groups”
4. Build the Addressable Group through “Build\New Build\Default Build Script”
5. Enter and exit Play mode twice
6. Observe Console
Expected result: No errors are thrown
Actual result: “ArgumentException: An item with the same key has already been added.” is thrown
Reproducible with: 1.20.5, 1.21.15 (2021.3.30f1, 2022.3.9f1, 2023.1.12f1, 2023.2.0b9, 2023.3.0a5)
Fixed in: 1.21.17 (2021.3.30f1, 2022.3.9f1, 2023.1.12f1, 2023.2.0b9, 2023.3.0a5)
Reproducible on: macOS Ventura 13.2.1 (Intel)
Not reproducible on: no other environment tested
Notes:
- The issue only reproduces when Enter Play Mode Options = On and Reload Domain = Off.
- The issue only reproduces when Play Mode Script = Use Existing Build. (Not reproduced with "Use Asset Database" or "Simulate Groups".)
- The issue reproduces when Addressables.Release() is called on OnDestroy() or OnApplicationQuit(). But does not reproduce in other MonoBehaviour events (such as Start(), Update(), etc.)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Add comment