Warning: Executed RPC with unresolved references.

[oblm]

Description

A warning about RPCs being executed with unresolved references can occur in UnrealGDK projects when a client disconnects from the deployment.

Here's an example warning, triggered when I disconnected a client from an ExampleProject deployment:

[UnrealClient-PlayerId-f2e75a7e-1feb-4738-bbd8-2916eb5ed4df:UnrealClient] Executed RPC BP_GDK_PlayerController_C_2147482419::ClientReceiveLocalizedMessage with unresolved references ((entity ID: 7030, offset: 0)) after 1.416 seconds of queueing. Owner name: PersistentLevel

Expected behavior

Clients should be able to disconnect gracefully, without triggering warnings.

Possible solution

In isolation, an RPC being executed with unresolved references doesn't inherently imply a defect. It simply means that the client didn't get interest in something within the specified window. For this reason, this should likely not be a warning. We are considering lowering this to a log.

While irritating, this warning is benign in most cases.

We are currently investigating how to strike a balance between letting you know when an RPC has been executed with unresolved references in cases that you should care about, while avoiding warning spam such as this.

Steps to reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code snippets if relevant.

1. Deploy Example Project
2. Connect a clinet
3. Disconnect a client

Environment

UnrealGDK 0.12.0

Internal ticket reference

UNR-4768