Codemagic build failed which was successfully published with the same codebase

[Kutbi-dev]

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?

React Native

Steps to reproduce

Start the build from codemagic
on step "Set up code signing settings on Xcode project" getting below error
Configure code signing settings
Searching for files matching /Users/builder/Library/MobileDevice/Provisioning Profiles/.mobileprovision
Searching for files matching /Users/builder/Library/MobileDevice/Provisioning Profiles/.provisionprofile
List available code signing certificates in keychain /Users/builder/Library/codemagic-cli-tools/keychains/09-01-25_4d2yglhg.keychain-db
Searching for files matching /Users/builder/clone/**/*.xcodeproj
Failed to set code signing settings for apps/responder-app/node_modules/react-native-fast-image/ios/FastImage.xcodeproj

Build failed :|
Step 15 script Set up code signing settings on Xcode project exited with status code 1

Expected results

build should be published successfully

Actual results

Earlier build was successfully published and all artifacts generated
Successfull build logs for the same step

Configure code signing settings
Searching for files matching /Users/builder/Library/MobileDevice/Provisioning Profiles/.mobileprovision
Searching for files matching /Users/builder/Library/MobileDevice/Provisioning Profiles/.provisionprofile
List available code signing certificates in keychain /Users/builder/Library/codemagic-cli-tools/keychains/07-01-25_6h4i6z11.keychain-db
Searching for files matching /Users/builder/clone/**/*.xcodeproj
Completed configuring code signing settings

• Using profile "AURA RESPONDER ios_app_store 1715869068" [48cd3e4c-5eed-4295-8e2f-e44fd7cb23ea] for target "AURAResponderApp" [Debug] from project "AURAResponderApp"
• Using profile "AURA RESPONDER ios_app_store 1715869068" [48cd3e4c-5eed-4295-8e2f-e44fd7cb23ea] for target "AURAResponderApp" [Release] from project "AURAResponderApp"
• Using profile "XC com aura responder production OneSignalNotificationServiceExtension ios_app_store 1713444874" [4fce8007-0f52-4c7b-ae78-181fac6c2d3e] for target "OneSignalNotificationServiceExtension" [Debug] from project "AURAResponderApp"
• Using profile "XC com aura responder production OneSignalNotificationServiceExtension ios_app_store 1713444874" [4fce8007-0f52-4c7b-ae78-181fac6c2d3e] for target "OneSignalNotificationServiceExtension" [Release] from project "AURAResponderApp"
  Generated options for exporting the project
• Method: app-store
• Provisioning Profiles:
  • com.aura.responder.production: AURA RESPONDER ios_app_store 1715869068
  • com.aura.responder.production.OneSignalNotificationServiceExtension: XC com aura responder production OneSignalNotificationServiceExtension ios_app_store 1713444874
• Signing Certificate: Apple Distribution
• Signing Style: manual
• Team Id: 27XW93998V
  Saved export options to /Users/builder/export_options.plist

Build id (optional)

677fbeb2ec8e639834f180e4

[dam-ease]

Hello @Kutbi-dev,
From the error message:

Failed to set code signing settings for apps/responder-app/node_modules/react-native-fast-image/ios/FastImage.xcodeproj

.xcodeproj for the FastImage is being code signed instead of the actual project. In order to solve it, you can add --project to use-profiles cli targeting the actual xcodeproj. It will look like this:

xcode-project use-profiles --project=ios/YOUR_PROJECT_NAME.xcodeproj

or

xcode-project use-profiles --project ios/*.xcodeproj

Re-run the build and please share how it goes.

[dam-ease]

Hello @Kutbi-dev,
You currently don't have any Provisioning Profile added to your Teams > Personal Account > codemagic.yaml settings > Code Signing Identities. You will need to add one since you are currently using the manual code signing method. Also you need to add the Push Notifications and OneSignalNotificationServiceExtension capabilities to the Provisioning Profile as requested. Also, there is a Codemagic CLI command, which allows you to add capabilities to your provisioning profile without needing to visit the Apple Developer page. And you can add it inside your workflow.
Please refer to this documentation
Here's an example of how this step would look if you add it to your workflow pipeline:

- name: Install capabilities script: |
app-store-connect bundle-ids enable-capabilities \
B5J6V3KQ94 \
--capability "Associated Domains" "Push Notifications"

Just keep in mind that you need to use the BUNDLE_ID_RESOURCE_ID, not the actual identifier, and you can find it in the URL after opening the actual ID in the Apple Developer portal: https://developer.apple.com/account/resources/identifiers/bundleId/edit/BUNDLE_ID_RESOURCE_ID. But you will need to firstly get the Provisioning Profile from App Store connect

[Kutbi-dev]

Hello @dam-ease
Now I am getting below error on build ipa step:

❌ error: Couldn't load -exportOptionsPlist: Failed to decode "provisioningProfiles". Expected to decode Dictionary<String, Any> but found an array instead.

Raw xcodebuild logs stored in /tmp/xcodebuild_logs/AURAResponderApp.log
Failed to export archive build/ios/xcarchive/AURAResponderApp_yt43eabl.xcarchive
Do I need to re-upload the provisioning profile in codemagic?

[Kutbi-dev]

Hello @dam-ease, Earlier build was successfully completed without any error in build IPA step.
Id for that build is: 677ceecc489d0850eb0f8186 (successfully completed all the steps)
Just after that build, when we published the build 2 days after (build id: 677fbeb2ec8e639834f180e4) it gave the error of (Failed to set code signing settings for apps/responder-app/node_modules/react-native-fast-image/ios/FastImage.xcodeproj) that I have mentioned in the above thread, after integrated that change in code, it was started asking about the provisioning profile in build ipa step.
Alos, build is successfully published with the old repo having the same yaml configuration.

[dam-ease]

Hello @Kutbi-dev,
I'm not so sure I got you last message fully but I looked through your team builds and can see that your last build failed in the publish step with error message:

Google Play failed to upload artifacts. Version code 1068 has already been used.: {
    "error": {
        "code": 403,
        "message": "Version code 1068 has already been used.",
        "status": "PERMISSION_DENIED"
    }
}

which means the version code exists in Google Play, you can add the script in the docs- https://docs.codemagic.io/yaml-quick-start/building-a-native-android-app/#conclusion to increment the version code based off what you currently have in the stores.