Signing Error When Building

[myklam]

I have an Expo application and I have recently integrated the @iterable/expo-plugin. When developing everything works great, but I'm having some issues generating builds of our app both locally and on EAS. The commands we have been using to generate these builds are:

eas build --profile development --platform ios
eas build --profile development --platform ios --local
eas build --profile staging --platform ios 
eas build --profile staging --platform ios --local

Neither the development or staging builds will complete and they are all showing the exact same error:

error: Signing for "IterableExpoRichPush" requires a development team. Select a development team in the Signing & Capabilities editor. (in target 'IterableExpoRichPush' from project 'my-app')

I have tried everything I can think of with credentials to get this signed, but nothing seems to work. I've also tried altering the settings in XCode, but that doesn't seem to do anything either. I can't seem to figure out how to get Expo or the @iterable/expo-plugin package to sign the other Target that gets added in XCode. We have followed the guide for setting up Iterable in Expo, and tried some of the steps that were applicable in the docs for setting up a bare React Native project.

Do you happen to know what's going on? Is this a bug in the @iterable/expo-plugin?

Version Info:
"@iterable/expo-plugin": "^1.0.0"
"@iterable/react-native-sdk": "^2.0.0"
"expo": "~52.0.47"
"react-native": "0.76.9"

[lposen]

Hi @myklam,

Thanks for reporting this!

It looks like your build is missing a configured development team, building for iOS with EAS Build and a plugin like @iterable/expo-plugin, which introduces a native module with its own target. The key here is that Expo/EAS needs to know which Apple Developer Team to use for signing all native targets, not just your main app.

---

✅ Solution: Add developmentTeam to your app.json (or app.config.js)

You’ll need to explicitly set your Apple Developer Team ID so Xcode can sign both your main app and the IterableExpoRichPush target.

🔧 Example (app.json):

{
  "expo": {
    "name": "YourApp",
    "slug": "your-app",
    ...
    "ios": {
      "bundleIdentifier": "com.yourcompany.yourapp",
      "developmentTeam": "YOUR_TEAM_ID"
    },
    ...
  }
}

Replace "YOUR_TEAM_ID" with your actual Apple Developer Team ID.

You can find your Team ID by logging into Apple Developer and checking under Membership or Certificates, Identifiers & Profiles.

🧪 Additional Notes

• If you're using app.config.js, the field goes in the same place (expo.ios.developmentTeam).
• If you’re using EAS-managed credentials, make sure your App Store Connect account has access to this Team ID.
• You don’t need to manually change anything in Xcode for EAS builds — the settings will be overridden during build time.

❓Why this happens

The @iterable/expo-plugin adds a Notification Service Extension (IterableExpoRichPush) to enable rich push support. iOS treats this as a separate native target, and it must be signed just like your main app. Without the developmentTeam field, Xcode (or EAS) doesn’t know how to sign it.

---

Let us know if setting developmentTeam resolves it for you! I will create a documentation ticket so that this is documented as part of the setup instructions.

[myklam]

While you are correct about the developmentTeam this was actually not the issue. It ended up being Apple's fault, and not the Iterable plugin. What happened was:

1. I created a build for a profile before being invited to the Apple Developer team.
2. Expo autogenerated the provisioning profile for the build and uploaded to my personal Apple Developer account
3. I joined the Apple Development team
4. After you join a development team, Apple essentially walls off all of your personal account data, and it becomes inaccessible. So when I tried to create builds, the identifier was taken by the hidden personal account data. Very frustrating.

Had to call Apple support to have them release the identifier from my personal account.

[lposen]

Thanks for the detailed follow-up — that makes a lot of sense, and I can see how that would be incredibly frustrating. Really appreciate you sharing the root cause here — it’ll help others who might run into a similar situation.

Glad you were able to get it resolved (even if it took a support call!). Let us know if you hit any other snags.

[j3lev]

Hey @lposen, developmentTeam doesn't appear to be a valid option, I believe the correct option should be appleTeamId. Expo docs for reference: https://docs.expo.dev/versions/latest/config/app/#appleteamid

[j3lev]

Just to double tap on this, after adding my team ID I'm getting the following error in an EAS build:

/Users/expo/workingdir/build/my-app/ios/MyApp.xcodeproj: error: No profiles for 'com.my.app.IterableExpoRichPush' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.my.app.IterableExpoRichPush'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'IterableExpoRichPush' from project 'MyApp')

FYI I anonymized my app name and bundle. Any idea what the fix could be for this? It looks like I need to set up a separate provisioning profile for the native extension? This was working before via a custom plugin I wrote myself.

[msh1997]

Running into the same issue as @j3lev, after adding appleTeamId as part of the app config, I'm running into the automatic signing issue. Building through xcode directly with automatic signing enabled works, but building through the EAS cli is failing on both local and remote.

[facundo-serfe]

Hello everyone, there is some news regarding the last problem mentioned by @msh1997 ?

[lposen]

Apologies for missing earlier comments — I didn’t see them after this ticket was closed.

Build failures are likely because IterableExpoRichPush isn’t configured in your app.json, which is required for EAS builds. Add this to expo.extra.eas:

{
	"projectId": "EAS_PROJECT_ID",
	"build": {
		"experimental": {
			"ios": {
				"appExtensions": [
					{
						"targetName": "IterableExpoRichPush",
						"bundleIdentifier": "BUNDLE_IDENTIFIER.IterableExpoRichPush"
					}
				]
			}
		}
	}
}

Example (EAS_PROJECT_ID = xyz, BUNDLE_IDENTIFIER = my.app):

{
	"expo": {
		"ios": { 
			"bundleIdentifier": "my.app" 
		},
		"extra": {
			"eas": {
				"projectId": "xyz",
				"build": {
					"experimental": {
						"ios": {
							"appExtensions": [
								{
									"targetName": "IterableExpoRichPush",
									"bundleIdentifier": "my.app.IterableExpoRichPush"
								}
							]
						}
					}
				}
			}
		}
	}
}

I’m working on updating the Expo documentation to include these steps — apologies again for the oversight.

If you’ve added this configuration and builds are still failing, please comment here or reach out to support so I can help troubleshoot further.

[facundo-serfe]

Don't worry, thanks for the reply, I got it working another way, obviously this app.config setup is more correct, but basing on my issue, the main issue it's was with the provisioning profile, so basically:

1. execute npx expo prebuild
2. create a new provisioning profile with the prebuild made (to recognize IterableExpoRichPush)
3. remove the ios and android folder
4. use this provisioning profile to make the EAS builds.

[sgtbrunner]

Apologies for missing earlier comments — I didn’t see them after this ticket was closed.

Build failures are likely because IterableExpoRichPush isn’t configured in your app.json, which is required for EAS builds. Add this to expo.extra.eas:

{
"projectId": "EAS_PROJECT_ID",
"build": {
"experimental": {
"ios": {
"appExtensions": [
{
"targetName": "IterableExpoRichPush",
"bundleIdentifier": "BUNDLE_IDENTIFIER.IterableExpoRichPush"
}
]
}
}
}
}
Example (EAS_PROJECT_ID = xyz, BUNDLE_IDENTIFIER = my.app):

{
"expo": {
"ios": {
"bundleIdentifier": "my.app"
},
"extra": {
"eas": {
"projectId": "xyz",
"build": {
"experimental": {
"ios": {
"appExtensions": [
{
"targetName": "IterableExpoRichPush",
"bundleIdentifier": "my.app.IterableExpoRichPush"
}
]
}
}
}
}
}
}
}
I’m working on updating the Expo documentation to include these steps — apologies again for the oversight.

If you’ve added this configuration and builds are still failing, please comment here or reach out to support so I can help troubleshoot further.

I've been having this issue for months now and can confirm this fixes it 😀
Thank you!

[jwernisch]

We are having a similar issue where the bundleIdentifier my.app.IterableExpoRichPush cannot be created on Apple's servers.
We have a ticket open with Apple to fix the issue, but continue to debug.

There are no issues creating an alternate Identity using my.app.IterableExpoRichPush1 as the bundleIdentifier on Apple's server, but the expo build fails (app ID does not match the bundle ID). It appears that the iterable-expo-plugin build process is hard coded to expect IterableExpoRichPush and is not pulling the targetName & bundleIdentifier values from app.json?

iterable-expo-plugin/plugin/src/withPushNotifications/withIosPushNotifications.constants.ts

Line 2 in 2263e4d

export const NS_TARGET_NAME = 'IterableExpoRichPush';