# Manage iOS Code Signing issue

**URL:** https://discuss.bitrise.io/t/manage-ios-code-signing-issue/25771
**Category:** iOS
**Tags:** code-signing
**Created:** [February 13, 2026, 2:34pm UTC](https://discuss.bitrise.io/t/manage-ios-code-signing-issue/25771 "2026-02-13T14:34:34Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![yevgenPaykey](https://avatars.discourse-cdn.com/v4/letter/y/e68b1a/32.png) [@yevgenPaykey](https://discuss.bitrise.io/u/yevgenPaykey)
#### Post date: [February 13, 2026, 2:34pm UTC](https://discuss.bitrise.io/t/manage-ios-code-signing-issue/25771/1 "2026-02-13T14:34:35Z")

</div>

Hi everyone!

I’m struggling with Manage iOS Code Signing step. It doesn’t pick up proper bundle id (staging) and tries to sign with production one. Bundle id in my app is set using xcconfig files. The step has proper configuration (Release-Staging). In logs I can see it builds first using proper config:

```auto
[14:13:25] $ xcodebuild "-project" "/Users/[REDACTED]/git/[REDACTED]/[REDACTED]/[REDACTED].xcodeproj" "-target" "[REDACTED]" "-configuration" "Release-Staging" "-showBuildSettings"

```

but then tries to use default bundle ids:

```auto
Local code signing assets not found for:
Archivable targets (2)
- com.company.app
- com.company.app.AppExtension

```

I tried to add “Replaces Xcode’s project PRODUCT\_BUNDLE\_IDENTIFIER” step before Signing step. It helped a but but crashed because entitlements still must be replaced with staging ones.

Also switching this step to “Xcode Archive & Export for iOS” doesn’t help (configuration is not applied)

How can I dynamically pick proper bundleId, entitlements based on configuration?

---

<div class="post-metadata">

### Author: ![yevgenPaykey](https://avatars.discourse-cdn.com/v4/letter/y/e68b1a/32.png) [@yevgenPaykey](https://discuss.bitrise.io/u/yevgenPaykey)
#### Post date: [February 16, 2026, 1:05pm UTC](https://discuss.bitrise.io/t/manage-ios-code-signing-issue/25771/2 "2026-02-16T13:05:53Z")

</div>

found a bug on my side. Topic can be closed
