Search Issue Tracker
Not Reproducible
Votes
0
Found in
6000.1.0b2
Issue ID
UUM-92609
Regression
Yes
Crash on RaiseException when entering Play Mode with a Material that has been upgraded from Built-In to URP when the Web Platform is enabled
Steps to reproduce:
- Open the attached Project
- Open Scene "SampleScene"
- Navigate to File > Build Profiles > Web and select "Switch Platform"
- Select "Housefly Nom" in the Project Browser
- Navigateand to Edit > Rendering > Materials > Convert Selected Built-In Materials to URP and observe the Console
- Enter Play Mode
Actual results: *
Errors logged when converting Material:
"UnityException: GetActiveBuildProfile can only be called from the main thread."
"Could not add platformSupportModule UnityEditor.Android.TargetExtension, try rebuilding the module: Exception has been thrown by the target of an invocation."
Errors like the second one are also present mentioning other installed platforms
When entering Play Mode the Editor crashes on:
RaiseException
CleanupAfterLoad
LoadSceneOperation::CompletePreloadManagerLoadSceneEditor
LoadSceneOperation::IntegrateMainThread
PreloadManager::UpdatePreloadingSingleStep
Expected results:* No crash occurs
Reproducible with versions: 6000.1.0a9, 6000.1.0b2
Not reproducible with versions: 2022.3.56f1, 6000.0.34f1, 6000.1.0a8
Tested on (OS): Windows 11
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Tested on the latest trunk 6000.1.0b4. And it doesn't reproduce anymore. There is probably something that fixed it between 6000.1.0b2 and 6000.1.0b4.