Unity iOS build failure on Xcode 27.2 – Missing Firebase SPM module maps

Open
#1,562 1 comment 0 reactions 0 assignees View on GitHub

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
Tech stack
firebase, ios, swift, unity

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

api: core
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:

  1. Compared builds using Xcode 26.2 and Xcode 27.2. The project builds successfully only with Xcode 26.2.
  2. Disabled explicit module builds for both Unity-iPhone and UnityFramework.
  3. Tested changes to User Script Sandboxing.
  4. Removed the unsupported -disable-explicit-module-build Swift flag.
  5. Cleared DerivedData and re-resolved dependencies.
  6. 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?

  1. Is Firebase Apple SDK 12.19.0 compatible with Xcode 27.2 (Build 27B52)?
  2. Are there any known issues with Xcode 27.2 generating or resolving Clang module maps for Firebase's Swift Package Manager dependencies?
  3. 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/firebase-unity-sdk

All issues in firebase/firebase-unity-sdk

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.