Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.10f1
2023.2.0b11
2023.3.0a7
Issue ID
UUM-53673
Regression
No
"Saving has no effect. Your class 'UnityEditor.WebGL.HttpServerEditorWrapper' is missing the FilePathAttribute" warning is thrown when building a WebGL Player
Reproduction steps:
1. Open the attached “ASDQWE” project
2. Build and run (File > Build And Run)
3. Observe the Console Window
Expected result: No errors or warnings are thrown
Actual result: “Saving has no effect. Your class 'UnityEditor.WebGL.HttpServerEditorWrapper' is missing the FilePathAttribute. Use this attribute to specify where to save your ScriptableSingleton” warning is displayed
Reproducible with: 2022.3.7f1, 2022.3.10f1, 2023.2.0a16, 2023.2.0b11, 2023.3.0a7
Not reproducible with: 2021.3.30f1, 2022.3.6f1, 2023.1.0a1, 2023.1.15f1, 2023.2.0a15
Reproducible on: Intel macOS 13.5
Not reproducible on: No other environment tested
Notes:
- The Player is built successfully
- Not reproducible on Standalone platform
Comments (2)
-
jgcalderon372
Mar 17, 2024 11:10
I can't create the web or windows build with this error. in 2022.3.10f1 version.
-
andrewkw
Jan 30, 2024 13:32
won't fix should not mean "won't comment" on the nature of the issue.
What does the message mean and is it a harmless bug?(It happens from the first build of a new project so it is weird not to fix)
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
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.