Hi, a collegue is occasionally using an i9 Intel Mac but it's not working for him anymore. The 1st error is:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.TypeInitializationException: The type initializer for 'Try_000000B2$BurstDirectCall' threw an exception. ---> System.InvalidOperationException: Burst failed to compile the function pointer `Int32 Try$BurstManaged(IntPtr, Block ByRef)`
 at Unity.Burst.BurstCompiler.Compile (System.Object delegateObj, System.Reflection.MethodInfo methodInfo, System.Boolean isFunctionPointer, System.Boolean isILPostProcessing) [0x0015a] in ./Library/PackageCache/com.unity.burst@1.8.17/Runtime/BurstCompiler.cs:462

We used Metaplay 27 until August and that version works for him still. He reproduced the error using a new empty project and installing Metaplay SDK 30.2 from scratch: > - MBP Intel i9, Sonoma 14.5 > - Unity 2022.3.25f > - Metaplay SDK 30.2 > - Target platform Windows, Mac, Linux > - Universal 3D URP template > 1. Extract MetaplaySDK folder to project root > 2. Add the MetaplaySDK/Client/ folder as a local package > 3. Click Metaplay -> Initialize Project > 4. Observe a promt “Burst Package Update Detected” > 5. press OK > 6. observe warning “Metaplay SDK integration incomplete, editor functionality disabled” > 7. error 1 I think the error also surfaced as "unknown namespace Google" in the Google Sheets config builder stuff. Another new collegue tried to run our project yesterday on Linux (x86) and got that error, I'm not sure if it's the same or different error.

Hi! I'll ask around if we have an Intel Mac to verify, but the stack trace doesn't seem to point to anything Metaplay specific, which doesn't help much with figuring out what might be causing it. Are you able to try disabling burst and see if the error persists? I'm not sure if the unknown namespace is the same issue, at least it seems unlikely. Does Windows work normally?

Windows (on Intel) and Mac ARM work fully, yes

A colleague investigated the burst issue, it appears that Unity requires to be restarted if Burst is installed/updated, if that doesn't happen then things break. Just restarting should resolve the issue.