Unity iOS build failure on Xcode 27.2 – Missing Firebase SPM module maps
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- build-system, mobile
Research direction
Start by comparing the Unity-exported iOS project’s Xcode 26.2 and 27.2 build settings and dependency resolution; the report does not include the build log or Package.resolved needed to trace the missing module maps. Reproduce with Firebase Unity SDK 13.17.0 and Swift Package Manager, then identify which dependency module maps are not generated or found. Done means the project builds with Xcode 27.2 or the compatibility limitation and a reliable workaround are documented.
Written by the indexing model from the issue text.
Description
Description
Subject: Unity iOS build failure on Xcode 27.2 – Missing Firebase SPM module maps
Hello Firebase Support Team,
We are experiencing an iOS build issue with our Unity project when building with Xcode 27.2. The same Unity-generated iOS project builds successfully using Xcode 26.2.
Environment:
- Unity: 6000.3.12f1
- Firebase Unity SDK: 13.17.0 (we initially tested 14.1.0 as well)
- Firebase Apple SDK: 12.19.0
- Integration: Swift Package Manager
- Xcode: 27.2 (Build 27B52)
- CocoaPods: 1.17.0 (used separately for other SDKs)
Issue:
After Unity successfully exports the iOS project, the Xcode 27.2 build fails while compiling UnityFramework.
The compiler reports missing module maps under:
DerivedData/.../Build/Intermediates.noindex/GeneratedModuleMaps-iphoneos/
There are 14 missing module-map errors in the build log, including:
- GoogleUtilities-UserDefaults
- GoogleUtilities-NSData
- GoogleUtilities-Logger
- GoogleUtilities-Environment
- GoogleUtilities-AppDelegateSwizzler
- GoogleUtilities-Reachability
- third-party-IsAppEncrypted
- GoogleDataTransport
- nanopb
- FirebaseCore
- FirebaseInstallations
- FirebaseMessaging
These module maps are referenced during compilation but are not generated or found by Xcode.
Troubleshooting already performed:
- Compared builds using Xcode 26.2 and Xcode 27.2. The project builds successfully only with Xcode 26.2.
- Disabled explicit module builds for both
Unity-iPhoneandUnityFramework. - Tested changes to User Script Sandboxing.
- Removed the unsupported
-disable-explicit-module-buildSwift flag. - Cleared DerivedData and re-resolved dependencies.
- Downgraded Firebase Unity SDK from 14.1.0 to 13.17.0, using Firebase Apple SDK 12.19.0. The same missing module-map errors remain.
We also reviewed the relevant Firebase issues, release notes, developer forums and discussions, but haven't found a solution matching this SPM-related failure.
Could you please help us with the following?
- Is Firebase Apple SDK 12.19.0 compatible with Xcode 27.2 (Build 27B52)?
- Are there any known issues with Xcode 27.2 generating or resolving Clang module maps for Firebase's Swift Package Manager dependencies?
- Is there a recommended workaround, configuration change or SDK update to resolve this issue?
We can provide the complete Xcode build log, Package.resolved, Podfile and other project configuration details if required.
Thank you for your help. We would appreciate your guidance, as this issue is currently blocking our iOS release.
Best regards
Reproducing the issue
No response
Firebase SDK Version
13.17.0
Xcode Version
27.2 (Build 27B52)
Installation Method
Swift Package Manager
Firebase Product(s)
Messaging
Targeted Platforms
iOS
Relevant Log Output
If using Swift Package Manager, the project's Package.resolved
Expand Package.resolved snippet
Replace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand Podfile.lock snippet
Replace this line with the contents of your Podfile.lock!
- 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
-
[Bug] Desktop managed DLLs marked Required32Bit fail to load on ARM64 CoreCLR (Unity 7 alpha)Possibly taken @AustinBenoit claimed this today. Openapi: core desktop production type: bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
firebase/firebase-unity-sdk#1566 · 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