Provisioning profile "main app profile" has app ID "com.main.app", which does not match the bundle ID "com.main.app.ImageNotification".

[Khairul989]

If you are looking for help, please confirm the following...

• I confirm I have searched the Docs, Codemagic Sample Projects, and GitHub Discussions.
• I confirm the software versions on my local computer match the ones in CI environment (e.g. Xcode version, Gradle version). See here
• I confirm I am able to do a fresh clone of the repository and build the project on my local computer.

Which mobile framework are you using?

Flutter (Dart)

Steps to reproduce

❗ Issue: Image Notification Extension Fails to Build on Codemagic
Description
I'm trying to add image notifications to my Flutter app using a Notification Extension Service. After adding the extension, I was able to build the project locally, but the build fails on Codemagic with the following error:

Error (Xcode): Provisioning profile "main app profile" has app ID "com.main.app",  
which does not match the bundle ID "com.main.app.ImageNotification".

It appears there is a code signing issue during the installation process.

Steps Taken
I confirmed that the Bundle Identifier for the extension matches its provisioning profile in Xcode.
The app builds successfully on my local machine but fails on Codemagic.
The setup for code signing identities in Codemagic includes the provisioning profile for the Image Notification extension.
However, in the build step, Codemagic only uses the main app's provisioning profile, which leads to a mismatch.
Codemagic Build Configuration
Below are the generated export options during the build:

Generated options for exporting the project:
  - Method: app-store
  - Provisioning Profiles:
      - com.main.app: main app profile
  - Signing Certificate: Apple Distribution
  - Signing Style: manual
  - Team ID: xxxx

Expected Behavior
Codemagic should correctly use the provisioning profile for both the main app and the Image Notification extension, allowing the build to succeed.

Request for Help
Has anyone encountered this issue before? Any insights on how to configure Codemagic to properly sign the notification extension?

Expected results

Codemagic should correctly use the provisioning profile for both the main app and the Image Notification extension, allowing the build to succeed.

Actual results

Codemagic only use one of the provisioning profile resulting to build failure

Build id (optional)

67b5a91eb782ef9859b793bb

[dam-ease]

Hello @Khairul989,
I went through your builds and I see that your recent build was successful, all good now?

[Khairul989]

Hi, I'm still facing the issue. The recent build is from another branch after I removed the notification service extension

[Khairul989]

more information on this issue @dam-ease

I'm following these guides to set up the notification extension service:

• Firebase documentation
• Medium tips

My app uses flavors, and I’ve already set up the bundle ID and App Group accordingly for each flavor.

[Khairul989]

I've tried both manual and automatic signing, but I'm still getting the same result.

[Khairul989]

The issue was caused by using PRODUCT_BUNDLE_IDENTIFIER in the global environment, which overrides the PRODUCT_BUNDLE_IDENTIFIER for all other targets.

[abhijain2472]

@Khairul989 so how you fixed this issue ?
I am also getting the same issue for one of my extension