Search Issue Tracker
Third Party Issue
Third Party Issue in 2023.3.X
Votes
0
Found in
2021.3.31f1
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
Issue ID
UUM-52676
Regression
No
AssemblyReloadEvents.afterAssemblyReload can't be called
How to reproduce:
1. Open the user-attached project “UnityBugReport”
2. Open the “SampleScene” scene
3. In the upper menu click Platform → Test
4. Observe the Console
Expected result: Both “Before” and “After” events are logged into the Console
Actual result: Only the “Before” event is logged
Reproducible with: 2021.3.31f1, 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
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
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
Resolution Note:
When assembly reload is invoked, all bindings get reset in code, so afterAssemblyReload is already empty at that time. To get that script working you could use InitializeOnLoadMethod for ensuring bindings are setup at proper time.
Resolution Note (2023.3.X):
When assembly reload is invoked, all bindings get reset in code, so afterAssemblyReload is already empty at that time. To get that script working you could use InitializeOnLoadMethod for ensuring bindings are setup at proper time.