[Bug] Desktop managed DLLs marked Required32Bit fail to load on ARM64 CoreCLR (Unity 7 alpha)
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- backend, mobile-dev
Research direction
Start by inspecting the desktop managed assembly build configuration in the Firebase Unity SDK v14.1.0 source at commit bd5b1261a3d563d13bece1c3ef3cf6a52202dd5c; the report identifies the eight affected DLLs and confirms an AnyCPU rebuild loads in an ARM64 .NET 10 loader. Check how those assemblies are built and packaged, then validate that official desktop packages load in the ARM64 CoreCLR reproduction. Done when the published assemblies load successfully and Unity 7/CoreCLR support status is clarified.
Written by the indexing model from the issue text.
Description
Description
The desktop managed assemblies in the official Firebase Unity SDK 14.1.0 UPM archives are marked ILOnly | Required32Bit (CLR flags 0x3). We encountered this while preparing an integration for the native Apple Silicon Unity 7 alpha Editor (7000.0.0a16, CoreCLR).
A small standalone .NET 10 ARM64 loader on the same machine rejects the original Google.MiniJson.dll with System.IO.FileLoadException: “The assembly architecture is not compatible with the current process architecture.” Rebuilding that assembly from the corresponding source as AnyCPU (ILOnly, flags 0x1) makes the same loader succeed.
Expected: the IL-only managed SDK assemblies can load in a 64-bit ARM64 CoreCLR process, without requiring a project-maintained rebuild. If Unity 7/CoreCLR is not supported yet, could you confirm the intended support status and whether publishing AnyCPU desktop managed assemblies is planned?
This report concerns managed assembly architecture flags, rather than a missing ARM64 native library, iOS simulator support, or the Play Mode lifecycle changes in #1534.
Reproducing the issue
The following reproduction isolates the managed loader problem; it does not require a Firebase project, credentials, native SDK initialization, or starting Unity.
- On an Apple Silicon Mac with the native ARM64 .NET 10 SDK, download and extract the official Firebase App 14.1.0 archive:
repro_dir="$(mktemp -d)"
cd "$repro_dir"
curl -fL https://dl.google.com/games/registry/unity/com.google.firebase.app/com.google.firebase.app-14.1.0.tgz -o firebase-app.tgz
tar -xzf firebase-app.tgz
dotnet new console --framework net10.0 -n Loader
- Replace
Loader/Program.cswith:
using System;
using System.Runtime.InteropServices;
using System.Runtime.Loader;
Console.WriteLine($"Runtime: {Environment.Version}, architecture: {RuntimeInformation.ProcessArchitecture}");
try
{
var assembly = AssemblyLoadContext.Default.LoadFromAssemblyPath(args[0]);
Console.WriteLine($"Loaded: {assembly.FullName}");
}
catch (Exception exception)
{
Console.WriteLine(exception.GetType().FullName + ": " + exception.Message);
Environment.ExitCode = 1;
}
- Run:
dotnet run --project Loader -- "$PWD/package/Firebase/Plugins/Google.MiniJson.dll"
Actual result: architecture incompatibility, exit code 1. The equivalent loader was compiled and executed locally with .NET SDK 10.0.100, runtime 10.0.0, process architecture Arm64, on macOS 15.8.3.
Official App archive SHA-256:
934c52d39cac8465d13f530cab4ebe2e1e336ed4b35286691a08c6854574cb6f
Using Mono.Cecil to inspect the official App, Analytics, and Crashlytics 14.1.0 archives, all eight of these non-iOS managed assemblies have ILOnly, Required32Bit:
Google.MiniJson.dllFirebase.Platform.dllFirebase.TaskExtension.dllFirebase.App.dllFirebase.Analytics.dllFirebase.Crashlytics.dllFirebase.Editor.dllFirebase.Crashlytics.Editor.dll
Firebase Unity SDK Version
14.1.0
Unity editor version
7000.0.0a16 (native Apple Silicon / ARM64 Editor)
Installation Method
Unity Package Manager — official Google .tgz archives for App, Analytics, and Crashlytics were inspected. The standalone reproduction above uses the unmodified official App archive directly.
Problematic Firebase Component(s)
Analytics, Crashlytics, and the shared App/Platform/Editor managed assemblies.
Other Firebase Component(s) in use
None beyond App, Analytics, and Crashlytics for this investigation.
Additional SDKs you are using
Unity External Dependency Manager com.unity.external-dependency-manager 2.1.1 in the Unity project. No additional SDK is involved in the standalone reproduction.
Targeted Platform(s)
Desktop — the immediate problem is loading managed assemblies on the macOS ARM64 CoreCLR host/Editor. Android and iOS runtime behavior is outside this reproduction.
Unity editor platform
Mac — macOS 15.8.3, Apple Silicon (ARM64).
Scripting Runtime
CoreCLR in the Unity 7 alpha Editor. The current issue form offers only Mono and IL2CPP, which do not describe this Editor configuration. The independent minimal loader uses .NET 10.0.0 ARM64.
Release Distribution Type
Pre-built SDK from Google's official Firebase Unity UPM archives.
Relevant Log Output
Original 14.1.0 Google.MiniJson.dll (local path redacted):
Runtime: 10.0.0, architecture: Arm64
System.IO.FileLoadException: Could not load file or assembly '<path>/original/Google.MiniJson.dll'. The assembly architecture is not compatible with the current process architecture.
The same loader with the AnyCPU rebuild:
Runtime: 10.0.0, architecture: Arm64
Loaded: Google.MiniJson, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
If using CocoaPods for Apple platforms, the project's Podfile.lock
Not applicable to the managed loader reproduction.
Workaround investigated and validation limits
We rebuilt the eight desktop managed assemblies from the matching Firebase Unity SDK v14.1.0 source (bd5b1261a3d563d13bece1c3ef3cf6a52202dd5c) with /platform:anycpu. Native libraries and the iOS-specific managed assemblies were not rebuilt.
Static comparisons against the official assemblies passed for assembly identities, public/protected APIs, assembly references, friend assemblies, embedded resources, and P/Invoke declarations. All 291 unique native imports matched the original ARM64 FirebaseCppApp-14_1_0.bundle exports. These checks support the workaround investigation; they do not establish full Unity/Firebase runtime compatibility or mobile qualification.
Could the desktop managed build configuration be changed to AnyCPU, and could the supported/planned Unity 7 CoreCLR configuration be clarified?
- Dominant language
- C#
- Stars
- 325
- Forks
- 62
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/firebase-unity-sdk
-
api: core
Difficulty 4/5 3-5 days Newbie friendliness 43/100
firebase/firebase-unity-sdk#1562 · 1 comment ·
Maintainers usually reply within 1 day
-
api: crashlytics type: question
Difficulty 4/5 3-5 days Newbie friendliness 45/100
firebase/firebase-unity-sdk#1560 · 2 comments ·
Maintainers usually reply within 1 day
-
[Bug] App Check (iOS): crash in TokenChangedMethod because AppCheckToken.expire_time_millis is left uninitializedPossibly taken @AustinBenoit claimed this 7 days ago. Openapi: appcheck type: bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
firebase/firebase-unity-sdk#1556 · 6 comments · 1 reaction · 1 assignee ·
Maintainers usually reply within 1 day
-
api: firestore type: feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
firebase/firebase-unity-sdk#1543 · 1 comment ·
Maintainers usually reply within 1 day
-
api: appcheck desktop production type: bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
firebase/firebase-unity-sdk#1530 · 3 comments ·
Maintainers usually reply within 1 day
All issues in firebase/firebase-unity-sdk
Similar issues
-
Support Flux ignore rules (drift detection ignore paths) in Microsoft.KubernetesConfiguration schemaOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Azure/azure-resource-manager-schemas#3921 ·
Maintainers usually reply within 1 day
-
text-align: justify is ignored in HTML to PDF conversionPossibly taken @PrzemyslawKlys claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 4 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100