Search Issue Tracker
Won't Fix
Votes
1
Found in
5.5.1f1
Issue ID
881939
Regression
No
NetworkConnection.isConnected is true after server was stopped and client was disconnected
To reproduce:
1. Open the project, attached by the user (Agar2.zip)
2. Build the project for standalone
3. Open the build and press Start Server
4. In the Editor, enter Play mode and press Start Client
5. In the Editor, press Connect
6. Select Network game object in the Hierarchy
7. In the build, press Stop
8. In the Inspector, in Network Client Manager component, observe that Is Connected is still true
Expected: stopping the server makes isConnected property be set to false
Actual: NetworkConnection.isConnected is still true even though the server is disconnected
Reproduced in 5.5.1f1, 5.6.2f1, 2017.1.0f1, 2017.2.0b1
Could not check for regression due to Unity not supporting backwards compatibility
-
clever
Jul 10, 2017 02:22
It should be also noted that this happens also if the app loses focus. In fact, the connection actually drops if the app loses focus on iOS/Android. Even when the player opens their status bar to adjust brightness or even does an in-app purchase. It's a serious flaw that the player gets disconnected when they're doing an in-app purchase or adjusting brightness ...etc
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Resolution Note:
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.