# VersionIncompatible error after upgrading 1.0.5 -\> 1.1.x

**URL:** <https://community.coherence.io/t/versionincompatible-error-after-upgrading-1-0-5-1-1-x/481>\
**Category:** Bug reports\
**Created:** [March 25, 2024, 6:42pm UTC](https://community.coherence.io/t/versionincompatible-error-after-upgrading-1-0-5-1-1-x/481 "2024-03-25T18:42:43Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Neodamus](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Neodamus](https://community.coherence.io/u/Neodamus)\
**Post date:** [March 25, 2024, 6:42pm UTC](https://community.coherence.io/t/versionincompatible-error-after-upgrading-1-0-5-1-1-x/481/1 "2024-03-25T18:42:43Z")

</div>

## Description, details and error message(s)

After upgrading to 1.1.x versions from 1.0.5, attempting to connect to a room locally produces the following errors:

Editor:

 ![113issue-1](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/23959a14b717da63ba541277307a39bf77d08c35.png)

RS:

 ![113issue-2](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/efc7090b70af3df7ac9cbe6b7c11a8c583d08229.png)

After upgrading, I have tried:

- Deleting/rebuilding Unity Library folder
- Ensuring RS was not running during package upgrade (suggested by Miguel)

## Expected behaviour

I expect that no error would occur and the client would stay connected

## How to reproduce

**Steps:**

1. Run RS Server from Editor
2. Create room and try to connect to it (in my case, I’m using CoherenceScene to connect)

## Environment

SDK: VS 2017  
Unity: 2022.3.4f1  
OS/Platform: Win10

---

<div class="post-metadata">

**Author:** ![Filip](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/filip/32/142_2.png) [@Filip](https://community.coherence.io/u/Filip)\
**Post date:** [March 26, 2024, 8:11am UTC](https://community.coherence.io/t/versionincompatible-error-after-upgrading-1-0-5-1-1-x/481/2 "2024-03-26T08:11:09Z")

</div>

Hey Neodamus!

In the _Replication Server_ screenshot that you’ve provided I can see two connections being made, one that carries proper `RSVersion: v4.0.4` field (top log) and another one that has the `RSVersion` field empty.

Since SDK 1.1.0 _Replication Server_ requires clients to provide a [semver](https://semver.org/) compatible version, to prevent old, incompatible clients from connecting.

Is there any chance that there is a built client that tried to connect using older SDK version? Or perhaps some custom code that uses `IClient.Connect(EndpointData, ConnectionSettings)`?

---

<div class="post-metadata">

**Author:** ![Neodamus](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Neodamus](https://community.coherence.io/u/Neodamus)\
**Post date:** [March 26, 2024, 4:05pm UTC](https://community.coherence.io/t/versionincompatible-error-after-upgrading-1-0-5-1-1-x/481/3 "2024-03-26T16:05:12Z")

</div>

Thanks for the response!

I’m pretty sure I’ve discovered the issue with your help, but at the very least, this should help point in the right direction.

The first connection being made is a client connection, auto-connecting through CoherenceScene, this appears to work as expected.

This is an MRS setup, so the the second connection being made is an MRS connection and appears to be initiated by the **coherence Multi-Room Simulator Local Forwarder** as when I disable this component, the error is no longer produced.

Without knowing the code inside and out, I’m guessing the issue is at MultiRoomSimulatorLocalForwarder.cs (line 86):

var joinRoomRequest = JoinRoomRequest.FromEndpointData(endpointData);

It appears the JoinRoomRequest.FromEndpointData(endpointData) method does not provide the newly required RSVersion info, and maybe it should?

---

<div class="post-metadata">

**Author:** ![Filip](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/filip/32/142_2.png) [@Filip](https://community.coherence.io/u/Filip)\
**Post date:** [March 27, 2024, 12:37pm UTC](https://community.coherence.io/t/versionincompatible-error-after-upgrading-1-0-5-1-1-x/481/4 "2024-03-27T12:37:19Z")

</div>

Thanks a lot for the investigation!

> [@Neodamus](#):
>
> It appears the JoinRoomRequest.FromEndpointData(endpointData) method does not provide the newly required RSVersion info, and maybe it should?

Indeed, that was the part of the problem. You can expect fix in the nearest release.

For now, the only workaround I could come up with would be [embedding](https://docs.unity3d.com/Manual/upm-embed.html) the package and changing the source (`Coherence.Toolkit/CoherenceScene.cs : 201`)

from:

```auto
Client.Connect(data.EndpointData, settings, data.ConnectionType);

```

to

```auto
bridge.Connect(data.EndpointData, data.ConnectionType, settings);

```

---

<div class="post-metadata">

**Author:** ![Neodamus](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Neodamus](https://community.coherence.io/u/Neodamus)\
**Post date:** [March 27, 2024, 2:21pm UTC](https://community.coherence.io/t/versionincompatible-error-after-upgrading-1-0-5-1-1-x/481/5 "2024-03-27T14:21:31Z")

</div>

Awesome to hear, and I can wait until the release to upgrade, no rush here. Just want to be able to keep the version current in the chance case something really critical needs to be fixed.

Thanks again for the help 😄

---

<div class="post-metadata">

**Author:** ![Neodamus](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Neodamus](https://community.coherence.io/u/Neodamus)\
**Post date:** [May 23, 2024, 3:36pm UTC](https://community.coherence.io/t/versionincompatible-error-after-upgrading-1-0-5-1-1-x/481/6 "2024-05-23T15:36:54Z")

</div>

This is fixed.

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex017/uploads/coherence/original/1X/b3aa79eb9519fac7aad7eba18f15a1e8ce60f6e2.png) [@system](https://community.coherence.io/u/system)\
**Post date:** [May 23, 2025, 3:37pm UTC](https://community.coherence.io/t/versionincompatible-error-after-upgrading-1-0-5-1-1-x/481/7 "2025-05-23T15:37:32Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
