"Local schema mismatch from server" - when defining multiple rooms/states

This error is reported often, and one of its causes is when multiple room/state classes are defined in the server with the same schema “context”.

Internally, every @type() call is going to register the property in a “global” context:

import { type, Schema } from "@colyseus/schema";

class State1 extends Schema {
  @type(...) my_prop
}

class State2 extends Schema {
  @type(...) my_prop
}

To avoid registering every schema in the global context, you can create a different context like this:

import { Context, Schema } from "@colyseus/schema"; // do not import "type" here

const type = Context.create(); // this is your @type() decorator bound to a context

class State2 extends Schema {
  @type(...) my_prop
}

---

Actions needed:

• Update documentation to encourage creating different contexts, especially in Unity because of the crash
• Throw WARNING on the client-side instead of ERROR when handshake sends more structures than necessary

[endel]

Hi @sorrow31812, for plain JavaScript it is a bit complicated, the general suggestion is to always use TypeScript:

// javascript
const schema = require("@colyseus/schema");

// create a new context
const context = new schema.Context();

class MyState extends schema.Schema {
}
schema.defineTypes(MyState, {
  currentTurn: "string"
}, context); // use the context

Make sure you use the specified context for every structure your state depends on, otherwise the “schema mismatch” is going to happen

[hdev72]

hello dear friends i have this error only in android build of unity (apk), in editor when i running game every thing is ok