Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2022.3.9f1
2023.1.12f1
Issue ID
UUM-48347
Regression
No
MonoBehaviours are not recognized when using a custom package
Reproduction steps:
1. Open project “UnityProj”
2. Select “ButtonAdapter.cs” in the Project window
3. Observe the Inspector window
Expected result: The script is recognized as a MonoBehaviour and the script contents are shown
Actual result: "No MonoBehavior scripts in the file, or their names do not match the file name." message is shown
Reproducible with: 2022.3.9f1, 2023.1.12f1
Couldn’t test with: 2021.3.30f1, 2023.2.0b8, 2023.3.0a4 (compiler errors)
Reproducible on: macOS Ventura 13.2.1 (Intel)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Based on the observation that the issue becomes non-reproducible following the reimportation of the script that triggers the warning, coupled with the fact that there are no ways to recreate this issue from scratch, it was decided to close it as won't fix.
Resolution Note (2023.1.X):
Based on the observation that the issue becomes non-reproducible following the reimportation of the script that triggers the warning, coupled with the fact that there are no ways to recreate this issue from scratch, it was decided to close it as won't fix.