https://metaplay.io logo
Compile Error right after Metaplay SDK init into U...
# questions-and-feedback
k
Right after doing the SDK init from CLI, in Unity I get this compile error.
Copy code
MetaplaySDK\Client\Core\Base\MetaplayCore.cs(327,17): error CS0103: The name 'Generated' does not exist in the current context
This immediately blocks following the tutorial, and any integration for that matter, I would think.
j
Which unity version are you using? The SDK requires Unity 2022.3 or later.
k
Oh, hey, I HAVE done a mistake.
Very good call!
j
If you are using the Trash Dash tutorial, unfortunately you need first to update the project to 2022.3. The conversion is automatic but will take a few minutes for Unity to update the project.
k
Yeah, I only did upgrade within the same minor version of Unity and totally glossed over a critical requirement. This is on me - quick check while I retry and verify if that was all.
j
No worries. Let us know if updating doesn't fix it. The SDK has an automated version check in the source that is supposed to give better error messages. But in this case when the code generators fail, the check fails to run and we get the ugly error message. We are fixing the error check in the next release.
k
Actually - the tutorial could make a mention of the Unity version requirement and spend a small chapter of text to mention about "sample project is on version x, upgrade it first to version y" as the first step of the tutorial.
I'll let you know if this was a false alarm other than tutorial feedback when the 2022.3 LTS install finishes.
j
j
Thanks, I just pushed a small fix to that guide, it's missing that you need to call
MetaplayClient.Update()
in your update loop
k
About this post: I can now verify that upgrading Trash Dash to Unity 2022.3.62f1 cleared the immediate compile error after SDK init, and now [I only have the Compile errors in the tutorial (same link as before)](https://discord.com/channels/1161294508152070165/1448622290509103165).