Search Issue Tracker
By Design
By Design in 1.1.X
Votes
0
Found in [Package]
1.1.3
Issue ID
MTTB-1373
Regression
No
Lobby Password property for SessionOptions has hard minimum length limit of 8
Steps to reproduce:
- Open the attached project
- Open the MainMenu Scene
- Enter Play mode
- Enter a session name
- Enter '1234' password
- Click the Create button
Actual results: The Password property has a hard minimum length limit of 8 and throws a 'SessionException: request failed validation password in body should be at least 8 chars long'
Expected results: The Password property has a lower minimum length, allowing more flexibility
Reproducible with versions: 1.1.0(6000.0.51f1), 1.1.3(6000.2.0b5)
Tested on (OS): macOS 15.5
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
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.1.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.