Resolved Relay allocation created successfully but can't connect

I'm running into an issue setting up Unity Transport after configuring Relay.
Here is the code:

Code (CSharp):

1. var data = await relayConnection.HostGame(1);
2. var utp = NetworkManager.Singleton.GetComponent<UnityTransport>();
3. utp.SetHostRelayData(data.IPv4Address, data.Port, data.AllocationIDBytes, data.Key, data.ConnectionData, true);
4. Debug.Log(utp.ConnectionData.Address + " vs: " + data.IPv4Address);
5. Debug.Log(utp.ConnectionData.Port + " vs: " + data.Port);

After relayConnection.HostGame(1), which I simply took from the Netcode documentation, I get the JoinCode, I can see the allocation in the dashboard and I can even get the client to connect to it.

However, after calling SetHostRelayData and NetworkManager.Singleton.StartHost(), even though the internal m_RelayServerData parameters are being set, the NetworkManager doesn't actually connect to the Client (ie, I don't see any connected clients, and the NetworkManager on the client side says disconnected)
Question
Is there something else needed to make them setup correctly?

Also, the source code for netcode seems to suggest that ConnectionData is ignored if Relay is used (see here and snippet below), but SetClientRelayData does set the ConnectionData properties, which is why I initially thought that SetHostRelayData wasn't setting anything. I can't figure out where in the code the distinction is, as SetClientRelayData calls the same method internally as SetHostRelayData.

SetConnectionData

Code (CSharp):

1.         /// <summary>
2.         /// Sets IP and Port information. This will be ignored if using the Unity Relay and you should call <see cref="SetRelayServerData"/>
3.         /// </summary>
4.         /// <param name="endPoint">The remote end point</param>
5.         /// <param name="listenEndPoint">The local listen endpoint</param>
6.         public void SetConnectionData(NetworkEndPoint endPoint, NetworkEndPoint listenEndPoint = default)

HostGame (from docs)

Code (CSharp):

1.     public async Task<RelayHostData> HostGame(int maxConn)
2.     {
3.         //Initialize the Unity Services engine
4.         await UnityServices.InitializeAsync();
5.         //Always autheticate your users beforehand
6.         if (!AuthenticationService.Instance.IsSignedIn)
7.         {
8.             //If not already logged, log the user in
9.             await AuthenticationService.Instance.SignInAnonymouslyAsync();
10.         }
11.  
12.         //Ask Unity Services to allocate a Relay server
13.         Allocation allocation = await Unity.Services.Relay.RelayService.Instance.CreateAllocationAsync(maxConn);
14.  
15.         //Populate the hosting data
16.         RelayHostData data = new RelayHostData
17.         {
18.             // WARNING allocation.RelayServer is deprecated
19.             IPv4Address = allocation.RelayServer.IpV4,
20.             Port = (ushort)allocation.RelayServer.Port,
21.  
22.             AllocationID = allocation.AllocationId,
23.             AllocationIDBytes = allocation.AllocationIdBytes,
24.             ConnectionData = allocation.ConnectionData,
25.             Key = allocation.Key,
26.         };
27.  
28.         //Retrieve the Relay join code for our clients to join our party
29.         data.JoinCode = await Unity.Services.Relay.RelayService.Instance.GetJoinCodeAsync(data.AllocationID);
30.         return data;
31.     }

 

Update: It seems that I am failing to connect after all. The client eventually drops the following message, indicating that it was disconnected and got a disconnect event.

Failed to connect to server.

Code (CSharp):

1. UnityEngine.Debug:LogError (object)
2. Unity.Netcode.Transports.UTP.UnityTransport:ProcessEvent () (at Packages/com.unity.netcode.gameobjects@1.0.0-pre.10/Runtime/Transports/UTP/UnityTransport.cs:690)
3. Unity.Netcode.Transports.UTP.UnityTransport:Update () (at Packages/com.unity.netcode.gameobjects@1.0.0-pre.10/Runtime/Transports/UTP/UnityTransport.cs:739)

 

So it seems that when Unity says deprecated, they mean "it doesn't work anymore", even though they leave it on their docs as an example. Changing the above code to use endpoints worked for me:

Code (CSharp):

1. JoinAllocation allocation = await Unity.Services.Relay.RelayService.Instance.JoinAllocationAsync(joinCode);
2.  
3.         RelayServerEndpoint defaultEndPoint = new RelayServerEndpoint("udp", RelayServerEndpoint.NetworkOptions.Udp,
4.                 true, false, allocation.RelayServer.IpV4, allocation.RelayServer.Port);
5.  
6.         foreach (var endPoint in allocation.ServerEndpoints)
7.         {
8.             if (endPoint.Secure == true && endPoint.Network == RelayServerEndpoint.NetworkOptions.Udp)
9.                 defaultEndPoint = endPoint;
10.         }
11.  
12.        
13.         var serverEndpoint = NetworkEndPoint.Parse(defaultEndPoint.Host, (ushort)defaultEndPoint.Port);
14.         //Populate the joining data
15.         RelayJoinData data = new RelayJoinData
16.         {
17.             IPv4Address = defaultEndPoint.Host,
18.             Port = serverEndpoint.Port,
19.  
20.             AllocationID = allocation.AllocationId,
21.             AllocationIDBytes = allocation.AllocationIdBytes,
22.             ConnectionData = allocation.ConnectionData,
23.             HostConnectionData = allocation.HostConnectionData,
24.             Key = allocation.Key,
25.         };

 

https://docs-multiplayer.unity3d.com/netcode/current/relay/relay/index.html

There are 2 samples on that page and they have comments when creating RelayJoinData and RelayHostData about how using those properties is deprecated. With these samples as they are presented, I wasn't able to get a connection (although the allocation was detected by the Client).

I changed that code to the code above (which I got from one of the samples), so that IPv4Address and Port were read from the endpoint, and that made it work for me (I didn't do any digging to confirm that this was the reason, but it didn't work before and worked after those changes, so I assumed that it was the case).