Search Issue Tracker
Won't Fix
Won't Fix in 1.13.X
Votes
0
Found in [Package]
1.11.2
1.13.0
Issue ID
ISXB-1419
Regression
No
the callbacks registered on Actions are triggered when the Action Map is disabled during the start callback or the first update callback
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the "/Assets/Scenes/SampleScene.unity" Scene
3. Enter the Play Mode
4. Press the "Enter" key
5. Observe the Console
Expected result: No log messages exist
Actual result: Log message "Submit action performed!" is s present
Reproducible with: 1.11.2 (2022.3.56f1), 1.13.0 (6000.0.37f1, 6000.1.0b5, 6000.2.0a2)
Reproducible on:
Play Mode
Not reproducible on:
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- Not reproducible after waiting for at least one frame before disabling the action map
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (1.13.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.