Search Issue Tracker
By Design
Votes
0
Found in
6000.0.37f1
6000.1.0b5
6000.2.0a3
Issue ID
UUM-97143
Regression
No
"Build And Run" the project for Web is allowed even though the directory for the non-default browser is not selected
How to reproduce:
1. Create a new project
2. Go to the Build Profiles -> Web -> Platform Settings -> Client Browser Type -> any non-default browser
3. Leave the "Path to the client Browser" empty
4. Observe the "Build And Run" button
Expected results: The button is inactive because without the missing directory the build can't be run anyway
Actual results: The button is active and errors are thrown when it tries to run the project
Reproducible with: 6000.0.37f1, 6000.1.0b5, 6000.2.0a3
Can't be tested with: 2022.3.57f1 (no browser option)
Reproducible on: macOS Sequoia 15.1 (M1)
Not reproducible on: No other environment tested
Note: The option to "Build And Run" is also available for the browsers that can't be used on the current OS (e.g. Microsoft Edge on macOS)
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note:
Thank you for reporting a bug to Unity.
This is the expected behaviour. We have reviewed the issue carefully, and at this time, the team is unable to prioritize further improvements for this feature. 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.