C# SDK 1.7.0: missing LICENSE.txt / orphaned LICENSE.txt.meta / repeated warning logs

[jan]

I'm getting these two warning logs in Unity 6.2 (6000.2.10f1) with SpacetimeDB SDK 1.7.0 (21684636cbcf30f31352bdd0a1dd8d951f7cd8bc):

A meta data file (.meta) exists but its asset 'Packages/com.clockworklabs.spacetimedbsdk/LICENSE.txt' can't be found. When moving or deleting files outside of Unity, please ensure that the corresponding .meta file is moved or deleted along with it.

Couldn't delete Packages/com.clockworklabs.spacetimedbsdk/LICENSE.txt.meta because it's in an immutable folder.

They are repeated every time I tab into Unity.

Admittedly just a nuisance, but would appreciate a fix.

Here's what Claude suggests:

The Problem

The SpacetimeDB SDK package has an orphaned meta file:

• File exists: LICENSE.txt.meta (with GUID a9576a820941d4473b81734019e6bae4)
• File missing: LICENSE.txt (the actual license file)

Unity detects the .meta file but can't find the corresponding LICENSE.txt asset, causing repeated warnings every time Unity refreshes.

Root Cause

The package at commit 21684636cbcf30f31352bdd0a1dd8d951f7cd8bc has a packaging issue where:

1. Either LICENSE.txt was removed but LICENSE.txt.meta was left behind
2. Or the packaging process excluded LICENSE.txt but included the meta file

Note: The package.json also has an empty license field, which might indicate intentional license file removal.

Fix for Maintainers

The SpacetimeDB SDK maintainers need to do one of the following:

Option 1: Add the missing LICENSE.txt file

• Add a LICENSE.txt file to the repository root
• Ensure it's included in the Unity package distribution

Option 2: Remove the orphaned meta file (recommended if no license file is intended)

• Delete LICENSE.txt.meta from the repository
• This will prevent Unity from expecting a LICENSE.txt file

[jan]

rm Library/PackageCache/com.clockworklabs.spacetimedbsdk@21684636cbcf/LICENSE.txt.meta

Does fix the issue.

[bfops]

Thank you for filing this! We'll work on getting it fixed soon.

[bfops]

@jan Did you get this error on previous versions, or only on 1.7.0?

[jan]

@bfops I don't think I had it in 1.5, not sure about 1.6. Not sure duper sure about this though.