Unity-Technologies / Unity-Technologies/com.unity.netcode.gameobjects
Closing the game on Android doesn't properly disconnect the client
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.3k
- Forks
- 461
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 20
Description
Description
On Android, when quitting the app, the server and other players don't get notified. Eventually it will time out due to heartbeats, but that is not ideal. When quitting the game on other platforms, such as Windows, it correctly notifies the server, and the player prefab gets destroyed.
Environment
- OS: Android
- Unity Version: 6000.0.25f1
- Netcode Version: 2.1.1
Additional Context
Specifically tested on:
- Samsung galaxy J5 2017
- Meta quest 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce quitting the game on Android, then compare the observed disconnect behavior with Windows; trace the Android application-quit lifecycle and the existing client disconnect path. Done means the server and other players are notified promptly and the player prefab is destroyed rather than waiting for heartbeat timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp, unity
- Domain
- game-dev, mobile, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100