Description

The ensure in APlayerState::OnRep_bIsInactive may be hit due to the player state being replicated before the game state. The check is necessary for making sure the game state is available, but the ensure is not needed since this is an expected possibility.

Steps to Reproduce

Immediately change the bIsInactive flag on a player state to something other than the default when a multiplayer game starts.
Depending on replication order or network conditions, the OnRep for bIsInactive may be called on a client before the game state has been created on that client.

Expected: The player state's OnRep would skip updating the game state's player array, and the game state would create a correct player array in PostInitializeComponents after its created on the client.
Actual: The ensure is hit.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to AnswerHub just mention UE-105202 in the post.

0
Login to Vote

Fixed
ComponentNetworking
Affects Versions4.25
Target Fix5.0
Fix Commit15003749
Release Commit15003749
CreatedJan 6, 2021
ResolvedJan 6, 2021
UpdatedJan 8, 2021