You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the step, it starts ignoring the project path I configure the step with (points to a workspace file, not an xcodeproj file), and tries to use the xcodeproj instead, resulting in a failure due to package resolution issues.
Looking for artifact name as field is empty
[20:32:19] Reading build settings...
[20:32:19] $ xcodebuild "-workspace" "/Users/[REDACTED]/git/overwatch-ios.xcworkspace" "-scheme" "Ignis" "-configuration" "Release" "-showBuildSettings"
[20:32:24] Read target settings.
Preparing code signing assets (certificates, profiles) before Archive action
[20:32:24] Reading build settings...
[20:32:24] $ xcodebuild "-project" "/Users/[REDACTED]/git/Ignis.xcodeproj" "-target" "Ignis" "-configuration" "Release" "-showBuildSettings"
failed to fetch code signing info from target (Ignis) settings: xcodebuild "-project" "/Users/[REDACTED]/git/Ignis.xcodeproj" "-target" "Ignis" "-configuration" "Release" "-showBuildSettings" command failed, output: Command line invocation:
/Applications/[Xcode-16.2.0.app/Contents/Developer/usr/bin/xcodebuild](https://xcode-16.2.0.app/Contents/Developer/usr/bin/xcodebuild) -project /Users/[REDACTED]/git/Ignis.xcodeproj -target Ignis -configuration Release -showBuildSettings
User defaults from command line:
IDEPackageSupportUseBuiltinSCM = YES
Resolve Package Graph
Packages are not supported when using legacy build locations, but the current project has them enabled.
2025-02-14 20:32:25.277 xcodebuild[6203:21198] Writing error result bundle to /var/folders/f6/wf2hj3cj75qdwmt5rn814r_00000gn/T/ResultBundle_2025-14-02_20-32-0025.xcresult
xcodebuild: error: Could not resolve package dependencies:
Packages are not supported when using legacy build locations, but the current project has them enabled.
Code signing asset management by Bitrise
Reason: Using Bitrise-managed code signing assets with API key because Automatically managed signing is disabled in Xcode for the project.
[20:32:26] Analyzing project
Configuration: Release
[20:32:26] Reading build settings...
[20:32:26] $ xcodebuild "-project" "/Users/[REDACTED]/git/Ignis.xcodeproj" "-target" "Ignis" "-configuration" "Release" "-showBuildSettings"
Failed to execute Step main logic:
failed to manage code signing: failed to read project platform: failed to fetch project (/Users/[REDACTED]/git/Ignis.xcodeproj) build settings: xcodebuild "-project" "/Users/[REDACTED]/git/Ignis.xcodeproj" "-target" "Ignis" "-configuration" "Release" "-showBuildSettings" command failed, output: Command line invocation:
/Applications/[Xcode-16.2.0.app/Contents/Developer/usr/bin/xcodebuild](https://xcode-16.2.0.app/Contents/Developer/usr/bin/xcodebuild) -project /Users/[REDACTED]/git/Ignis.xcodeproj -target Ignis -configuration Release -showBuildSettings
User defaults from command line:
IDEPackageSupportUseBuiltinSCM = YES
Resolve Package Graph
Packages are not supported when using legacy build locations, but the current project has them enabled.
2025-02-14 20:32:26.886 xcodebuild[6204:21231] Writing error result bundle to /var/folders/f6/wf2hj3cj75qdwmt5rn814r_00000gn/T/ResultBundle_2025-14-02_20-32-0026.xcresult
xcodebuild: error: Could not resolve package dependencies:
Packages are not supported when using legacy build locations, but the current project has them enabled.
Steps to reproduce
You'll need to try building the project through support.
FWIW, I can't get the same error to reproduce locally.
The text was updated successfully, but these errors were encountered:
Troubleshooting
Useful information
Issue description
When running the step, it starts ignoring the project path I configure the step with (points to a workspace file, not an xcodeproj file), and tries to use the xcodeproj instead, resulting in a failure due to package resolution issues.
Bitrise info
Steps to reproduce
You'll need to try building the project through support.
FWIW, I can't get the same error to reproduce locally.
The text was updated successfully, but these errors were encountered: