Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0f3
Issue ID
824064
Regression
No
[Matchmaking] Connection drop on the second connection attempt
Reproduction steps:
1) Open user's attached project
2) Configure Multiplayer settings in "Services" window
3) Build and run project on an Android device
4) Enter playmode in Editor (or use second device)
5) Press "Start Matchmake" on a device, then in Editor
-- Wait till two white buttons appear
6) Press lower button on device and Editor
7) Press "Back To Screen0" button on device and Editor
8) Press "Start Matchmake" again
Expected results:
Should start matchmaking (should two white buttons appear)
Actual result:
Connection is being dropped (goes back to step 6)
Note:
If you would wait for ~30 seconds between step 6 and step 7, this issue wont reproduce on that attempt.
Issue reproduces on iOS, Android and Standalone.
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 (2018.2.X):
Mass closure of UNET Bugs.
As UNET is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.
Closing this bug as part of cleaning-up the Bug List.
If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.