Skip to content

Possible Issues and Solutions

This page lists possible issues and solutions for common errors that can occur when using the Beam SDK and how to fix them.

Multiple Microservice Classes Detected

Explanation:
Only one Microservice class should exist per microservice project. Multiple classes marked with the [Microservice] attribute will cause conflicts in code generation and runtime behavior.

Example Code Triggering the Error: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice {}

[Microservice("MyOtherMicroservice")]
public partial class MyOtherMicroservice : Microservice {}

Example Error Message: 

Multiple Microservice classes detected. Make sure only a single class implementing Microservice exists in each service project. ClassNames=MyMicroservice, MyOtherMicroservice.

Solutions: - Ensure only one class is marked as a Microservice in your project.

Example of Solved Code: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice {}

Non-Partial Microservice Class Detected

Explanation:
Microservice classes must be marked as partial to allow code generation tools to extend them.

Example Code Triggering the Error: 

[Microservice("MyMicroservice")]
public class MyMicroservice : Microservice {}

Example Error Message: 

Non-Partial Microservice class detected. Make sure your Microservice class is marked as partial.

Solutions: - Add the partial modifier to the class.

Example of Solved Code: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice {}

Microservice Class Missing Microservice Id

Explanation:
The Microservice class must include the [Microservice("Id")] attribute to define its identifier.

Example Code Triggering the Error: 

public partial class MyMicroservice : Microservice {}

Example Error Message: 

Microservice class is missing the microservice id

Solutions: - Add the [Microservice("Id")] attribute to the class.

Example of Solved Code: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice {}

Async Void Callable Methods

Explanation:
Methods marked as [Callable], [ClientCallable], [ServerCallable] should not be async void. Using async void makes it impossible to track errors or await completion.

Example Code Triggering the Error: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice 
{
    [Callable]
    public async void CallMicroservice() {}
}

Example Error Message: 

Microservice Callable methods cannot be async voids. Ex: CallMicroservice.

Solutions: - Change the return type to Task.

Example of Solved Code: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice 
{
    [Callable]
    public async Task CallMicroservice() {}
}

Invalid Type Usage in Callable Method

Explanation:
Types used in [ClientCallable] methods must be available to both server and client. Declaring types inside the microservice class makes them inaccessible to the Unity client as we're not regenerating DTO for Client.

Example Code Triggering the Error: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice 
{
        [ClientCallable]
    public async Task<DTO> CallServiceAsync() => new DTO { x = 1 };

    [ClientCallable]
    public void CallService(DTO data) {}
}

public class DTO
{
    public int x;
}

Example Error Message: 

Microservice Callable method `CallServiceAsync` uses a Type that cannot be inside microservice scope. Type: `DTO`.

Solutions: - Move shared types (DTOs, Enums, etc.) to a shared project referenced by both Unity and the server.

Example of Solved Code (Microservice): 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice 
{
    [ClientCallable]
    public async Task<DTO> CallServiceAsync() => new DTO { x = 1 };

    [ClientCallable]
    public void CallService(DTO data) {}
}

Shared Project Code: 

public class DTO
{
    public int x;
}

Callable Method Types usage are Nested

Explanation:
Types used in [ClientCallable] methods must be declared in outer scope so the Source Code Generator can handle it properly.

Example Code Triggering the Error: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice 
{
    public class DTO
    {
        public int x;
    }

    [ClientCallable]
    public void CallService(DTO data) {}
}

Example Error Message: 

{nameof(Server.Microservice)} Callable method CallService uses a Type that is Nested, which is not supported by the Source Code Generator. Please move DTO to outer scope.

Solutions: - Move named types used by Callable methods to a non-nested scope.

Example of Solved Code: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice 
{
    [ClientCallable]
    public void CallService(DTO data) {}
}

public class DTO
{
    public int x;
}

Beam Generated Schema Class is a Nested Type

Explanation:
Classes that uses the attribute [BeamGenerateSchema] cannot be declared as nested type because the Source Generator Cannot handle it.

Example Code Triggering the Error: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice 
{
    [BeamGenerateSchema]
    public class DTO
    {
        public int x;
    }
}

Example Error Message: 

Type DTO contains [BeamGenerateSchema] attribute and is a Nested type, which is not supported by the Source Generator. Please move DTO to outer scope.

Solutions: - Move classes that contains [BeamGenerateSchema] attribute to a non-nested scope.

Example of Solved Code: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice { }

[BeamGenerateSchema]
public class DTO
{
    public int x;
}

Invalid Microservice ID

Explanation:
Microservices IDs must match the <BeamID> property on csproj. If there is none <BeamID> property it needs to match the project's name.

Example Code Triggering the Error: 

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice {}

Example CSProj Triggering the Error: 

<Project Sdk="Microsoft.NET.Sdk">
    ...
    <PropertyGroup Label="Beamable Settings">
        ...
        <BeamId>OtherBeamId</BeamId>
        ...
    </PropertyGroup>
    ...
</Project>

Example Error Message: 

Microservice ID: `MyMicroservice` is invalid, it needs to be the same as <BeamId> csharp property (or as csproj name if none exist): `OtherBeamId`

Solutions: - Switch Microservice attribute parameter to use the same value as <BeamId> Example of Solved Code: 

[Microservice("OtherBeamId")]
public partial class MyMicroservice : Microservice { }

[BeamGenerateSchema]
public class DTO
{
    public int x;
}
- Update <BeamId> property to match the Microservice attribute value Example of Solved CSProj: 
<Project Sdk="Microsoft.NET.Sdk">
    ...
    <PropertyGroup Label="Beamable Settings">
        ...
        <BeamId>MyMicroservice</BeamId>
        ...
    </PropertyGroup>
    ...
</Project>

Static Field in Microservice

Explanation:
Non-readonly static fields in Microservices are discouraged because they do not behave reliably in horizontally scaled environments. Their state is not shared across instances.

Example Code Triggering the Warning: 

public partial class MyMicroservice : Microservice
{
    public static string ContentId = "coins.gems";
}

Example Warning Message: 

Consider making 'ContentId' a readonly field. Otherwise the value may be inconsistent in production environments.

Solutions: - Make the static field readonly if it's intended to be constant after initialization. Example of Solved Code: 

public partial class MyMicroservice : Microservice
{
    public static readonly string ContentId = "coins.gems";
}
- Or convert it to a non-static field if it should be instance-bound.

Missing Serializable Attribute on Type

Explanation:
All types used in Microservice method signatures or marked with [BeamGenerateSchema] must be annotated with [Serializable] to ensure correct serialization and code generation.

Examples Code Triggering the Error:

[BeamGenerateSchema]
public class MyDto
{
    public int x;
}
public class MyOtherDto
{
    public int x;
}
[Microservice("OtherBeamId")]
public partial class MyMicroservice : Microservice 
{
    [ClientCallable]
    public void CallService(MyOtherDto data) {}
}

Example Error Messages: 

Add the [Serializable] attribute to type 'MyDto'

Add the [Serializable] attribute to type 'MyOtherDto'

Solution: - Add the [Serializable] attribute. Example of Solved Code: 

[Serializable]
[BeamGenerateSchema]
public class MyDto
{
    public int x;
}
[Serializable]
public class MyOtherDto
{
    public int x;
}
[Microservice("OtherBeamId")]
public partial class MyMicroservice : Microservice
{
    [ClientCallable]
    public void CallService(MyOtherDto data) {}
}

Property Found in Serializable Type

Explanation:
Properties in types used in Microservice method signatures or marked with [BeamGenerateSchema] are ignored by the client code generator. Fields should be used instead.

Example Code Triggering the Warning: 

[Serializable]
public class MyDto
{
    public int X { get; set; }
}

Example Warning Message: 

Consider changing property 'X' to a field to include it in client-generated code

Solution: - Use fields instead of properties. Example of Solved Code: 

[Serializable]
public class MyDto
{
    public int X;
}

Nullable Field in Serializable Type

Explanation:
Fields with nullable types (e.g., int?, string?) are not supported in types used in Microservice method signatures or marked with [BeamGenerateSchema]. Use Optional<T> instead to ensure predictable behavior.

Example Code Triggering the Error: 

[Serializable]
public class MyDto
{
    public int? Score;
}

Example Error Message: 

Change field 'Score' to use Optional<T> instead of a nullable type

Solution: - Use Optional<T> instead of nullable types. Example of Solved Code: 

[Serializable]
public class MyDto
{
    public Optional<int> Score;
}

Invalid ContentObject Used

Explanation: Using ContentObject or its subtypes directly in serializable fields or parameters is discouraged, as it may lead to large data payloads. Instead, prefer using ContentRef<T> to reference content objects efficiently.

Example Code Triggering the Error:

[BeamGenerateSchema]
public class MyDTO
{
    public MyItem item; 
}

public class MyItem : ContentObject {}

Example Error Message:

Change 'item' to use ContentRef<MyItem> instead of MyItem

Solution:

  • Replace the direct ContentObject usage with ContentRef<T>.

Example of Solved Code: 

[BeamGenerateSchema]
public class MyDTO
{
    public ContentRef<MyItem> item;
}

public class MyItem : ContentObject {}

Type Used in BeamGenerateSchema is Missing Attribute

Explanation:
When a class is marked with [BeamGenerateSchema], all custom types used in its fields must also be annotated with [BeamGenerateSchema].

Example Code Triggering the Error: 

[BeamGenerateSchema]
public class MyDTO
{
    public MyOtherDTO otherDTO;
}
public class MyOtherDTO
{
    public int Value;
}

Example Error Message: 

Add the [BeamGenerateSchema] attribute to type 'MyOtherDTO'

Solution: - Add [BeamGenerateSchema] to all nested field types. Example of Solved Code: 

[BeamGenerateSchema]
public class MyDTO
{
    public MyOtherDTO otherDTO;
}
[BeamGenerateSchema]
public class MyOtherDTO
{
    public int Value;
}

Dictionary Key Must Be String on Serializable Types

Explanation:\ When using a Dictionary field in a type marked with [BeamGenerateSchema], the key must be of type string. Other key types are not supported.

Example Code Triggering the Error:

[BeamGenerateSchema]
public class MyDTO
{
    public Dictionary<int, string> InvalidDict;
}

Example Error Message:

Change the dictionary key of field 'InvalidDict' to string instead of type 'int'

Solution:

  • Change the dictionary key type to string.

Example of Solved Code:

[BeamGenerateSchema]
public class MyDTO
{
    public Dictionary<string, string> ValidDict;
}

Field on Serializable Type Is Subtype From Dictionary

Explanation:\ Types that subclass Dictionary are not supported as field types in [BeamGenerateSchema] annotated classes.

Example Code Triggering the Error:

public class MyDict : Dictionary<string, string> {}

[BeamGenerateSchema]
public class MyDTO
{
    public MyDict customDict;
}

Example Error Message:

Replace field 'customDict' to Dictionary instead of type 'MyDict'

Solution:

  • Use Dictionary<string, T> directly instead of a subclass.

Example of Solved Code:

[BeamGenerateSchema]
public class MyDTO
{
    public Dictionary<string, string> customDict;
}

Field on Serializable Type Is Subtype From List

Explanation:\ Types that subclass List<T> are not supported as field types in [BeamGenerateSchema] annotated classes.

Example Code Triggering the Error:

public class MyList : List<string> {}

[BeamGenerateSchema]
public class MyDTO
{
    public MyList customList; 
}

Example Error Message:

Replace field 'customList' to List instead of type 'MyList'

Solution:

  • Use List<T> directly instead of a subclass.

Example of Solved Code:

[BeamGenerateSchema]
public class MyDTO
{
    public List<string> customList;
}

Callable Method Declaration Type Is ContentObject Subtype

Explanation:\ Types used in Callable methods cannot inherit from ContentObject. Only the base ContentObject is supported.

Example Code Triggering the Error:

public class MyContent : ContentObject {}

public class MyMicroservice : Microservice
{
    [Callable]
    public Task DoSomething(MyContent input) => Task.CompletedTask;
}

Example Error Message:

Change type 'MyContent' to use the base ContentObject type instead of a subtype

Solution:

  • Use ContentObject instead of a derived type.

Example of Solved Code:

public class MyMicroservice : Microservice
{
    [Callable]
    public Task DoSomething(ContentObject input) => Task.CompletedTask;
}

Callable Method Declaration Type Is Invalid Dictionary

Explanation:\ Dictionaries in [Callable] method parameters are only valid if their keys are of type string.

Example Code Triggering the Error:

public class MyMicroservice : Microservice
{
    [Callable]
    public Task DoSomething(Dictionary<int, string> input) => Task.CompletedTask;
}

Example Error Message:

Change the dictionary key of 'input' to string instead of type 'int'

Solution:

  • Change dictionary key to string.

Example of Solved Code:

public class MyMicroservice : Microservice
{
    [Callable]
    public Task DoSomething(Dictionary<string, string> input) => Task.CompletedTask;
}

Callable Method Declaration Type Is Subtype From Dictionary

Explanation:\ Types used in [Callable] methods that subclass Dictionary are not supported.

Example Code Triggering the Error:

public class MyDict : Dictionary<string, string> {}

public class MyMicroservice : Microservice
{
    [Callable]
    public Task DoSomething(MyDict input) => Task.CompletedTask;
}

Example Error Message:

Replace 'input' to Dictionary instead of type 'MyDict'

Solution:

  • Use Dictionary<string, T> directly.

Example of Solved Code:

public class MyMicroservice : Microservice
{
    [Callable]
    public Task DoSomething(Dictionary<string, string> input) => Task.CompletedTask;
}

Callable Method Declaration Type Is Subtype From List

Explanation:\ Types used in [Callable] methods that subclass List<T> are not supported.

Example Code Triggering the Error:

public class MyList : List<string> {}

public class MyMicroservice : Microservice
{
    [Callable]
    public Task DoSomething(MyList input) => Task.CompletedTask;
}

Example Error Message:

Replace 'input' to List instead of type 'MyList'

Solution:

  • Use List<T> directly.

Example of Solved Code:

public class MyMicroservice : Microservice
{
    [Callable]
    public Task DoSomething(List<string> input) => Task.CompletedTask;
}

Invalid Generic Type in Microservice

Explanation:
Generic types are not supported in Microservice [Callable] methods or in classes marked with [BeamGenerateSchema], except for a specific set of allowed generic types. The code generator cannot properly handle custom generic types for client-side code generation. The only permitted generic types are: List<T>, Dictionary<TKey, TValue>, Optional<T>, and ContentRef<T>.

Example Code Triggering the Error:

// Custom generic class
public class GenericContainer<T>
{
    public T Value;
}

[BeamGenerateSchema]
public class MyDTO
{
    public GenericContainer<int> container; // Error: GenericContainer is not an allowed generic type
}

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice
{
    [ClientCallable]
    public Task<GenericContainer<string>> GetData() // Error: GenericContainer is not an allowed generic type
    {
        return Task.FromResult(new GenericContainer<string>());
    }
}

Example Error Message:

Generic Types on Microservice Callable methods or classes with [BeamGenerateSchema] are not supported. The only generic types allowed are: List<T>, Dictionary<TKey, TValue>, Optional<T>, ContentRef<T>. Please change 'GenericContainer<int>' in 'MyDTO.container' to a non-generic type.

Solutions:

  • Replace custom generic types with concrete types.
  • Use one of the allowed generic types (List<T>, Dictionary<string,T>, Optional<T>, ContentRef<T>) if they fit your use case.

Example of Solved Code:

// Option 1: Use a concrete type
public class IntContainer
{
    public int Value;
}

[BeamGenerateSchema]
[Serializable]
public class MyDTO
{
    public IntContainer container; // Fixed: Using concrete type
}

// Option 2: Use allowed generic types
[BeamGenerateSchema]
[Serializable]
public class MyOtherDTO
{
    public List<int> values; // Allowed: List<T> is permitted
    public Optional<int> optionalValue; // Allowed: Optional<T> is permitted
}

[Microservice("MyMicroservice")]
public partial class MyMicroservice : Microservice
{
    [ClientCallable]
    public Task<IntContainer> GetData() // Fixed: Returns concrete type
    {
        return Task.FromResult(new IntContainer());
    }

    [ClientCallable]
    public Task<List<string>> GetStrings() // Allowed: List<T> is permitted
    {
        return Task.FromResult(new List<string>());
    }
}