Codesigning failure starting with 11.14.0

[sberrevoets]

Description

Starting with version 11.14.0 (and also 11.15.0), our codesigning on CI (Xcode 16.3) fails:

error: exportArchive "Speak-V2.app" requires a provisioning profile with the App Groups, Associated Domains, Communication Notifications, Push Notifications, and Sign in with Apple features.

error: exportArchive "SpeakNotificationExtension.appex" requires a provisioning profile with the App Groups feature.

error: exportArchive "SpeakWidgetExtension.appex" requires a provisioning profile with the App Groups feature.

The provisioning profiles haven't changed, and reverting Firebase to 11.13 builds the app correctly. I noticed there were quite a few dependency changes for 11.14, is it possible any of the changes there causes this issue for us?

I realize the information I'm providing here is sparse, mostly because I don't have much more info myself, but let me know what would be helpful!

Reproducing the issue

This is specific to our setup unfortunately

Firebase SDK Version

11.14.0+

Xcode Version

16.4

Installation Method

Swift Package Manager

Firebase Product(s)

Authentication, Analytics, Messaging

Targeted Platforms

iOS

Package.resolved

Relevant Package.resolved info

    {
      "identity" : "firebase-ios-sdk",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/firebase-ios-sdk.git",
      "state" : {
        "revision" : "fdc352fabaf5916e7faa1f96ad02b1957e93e5a5",
        "version" : "11.15.0"
      }
    },
    {
      "identity" : "googleappmeasurement",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleAppMeasurement.git",
      "state" : {
        "revision" : "45ce435e9406d3c674dd249a042b932bee006f60",
        "version" : "11.15.0"
      }
    }

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[matteolongeri-ovolab]

Hi @sberrevoets,
I confirm that with version 11.14.0 we have started to experience exactly the same issue. I have just tested 11.15.0 with the same result, so for now we are also stuck to version 11.13.0.

Matteo

[ncooke3]

Apologies for the trouble. What Firebase products are you using, @matteolongeri-ovolab?

[matteolongeri-ovolab]

Hi @ncooke3,

Currently we are using:

• FirebaseAnalytics
• FirebaseAppCheck
• FirebaseCrashlytics
• FirebasePerformance

We use SPM to add them to our project.

Matteo

[mmoser-hw]

Hello, we face the same issue. We had this specific error on previous versions when trying to integrate the OnDeviceMeasurement SDK. Our solution at the time was to fork this specific library and embark it in our project, without loading it via SPM. Now that this library is included in the 11.14 version of Firebase Analytics, the issue re-emerged in our project too.
So it seems strongly related to the OnDeviceMeasurement SDK.

[adozenlines]

For Apple 12 it is all of the modules is the code signing missing an intermediary certificate or is being signed with an Enterprise Certificate?

[Cedrick84]

Experiencing the same from 11.14 up to latest (12) using

• FirebaseAnalytics
• FirebaseCrashlytics

[ncooke3]

Hi everyone, as I'm understanding this, 11.14.0+ (including 12.0.0 now) has this issue for projects using Analytics?

Is anyone able to reproduce this issue without Analytics present?

[ncooke3]

I so far have been unable to reproduce this using SwiftPM. I tried using the analytics/ project in the Firebase Quickstart repo (https://github.com/firebase/quickstart-ios/tree/main/analytics). I added Analytics, Messaging, and Auth via SPM and was able to successfully archive the project without running into any signing issues.

[sberrevoets]

I'm not overly familiar with Firebase's suite of frameworks, but we believe it's related to FirebaseAnalyticsOnDeviceConversion or GoogleAdsOnDeviceConversion (or both) specifically. We get the same problem when using 11.13.0 with those frameworks, and 11.14.0+ automatically includes those hence the error there too.

[mikehaydan]

hello. getting the same. Seems like Firebase SDK "forces" to use manual signing instead of automatic