After updating Github iOS build workflow to Xcode 16.3, it hangs at Resolving package dependency step.

[nmehta-septa]

Description

After updating to Xcode 16.3 version in our iOS build pipeline file, it hangs at Resolving package dependency step every time at a different package. I am able to successfully build all the packages locally on my Mac running macOS 15.4.1 and Xcode 16.3 (16E140).
The build pipeline was working successfully with Xcode 15.3.

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 22.04
• Ubuntu 24.04
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• macOS 15
• macOS 15 Arm64
• Windows Server 2019
• Windows Server 2022
• Windows Server 2025

Image version and build link

Current runner version: '2.323.0'

Is it regression?

no

Expected behavior

Builds to be generated successfully after the build pipelines runs with updated Xcode version 16.3.

Actual behavior

Build action fails after timing out at Resolving Package Dependency step.

Repro steps

Update Xcode version to 16.3 and macOS version to macos-15, build pipeline fails.
deploy:
runs-on: macos-15
name: Select Xcode
uses: maxim-lobanov/setup-xcode@v1
with:
xcode-version: '16.3'

[ijunaidm1]

Hi @nmehta-septa - We will start investigating on this issue and will update you accordingly. Can you please share the workflow run you have tried for this issue.

[nmehta-septa]

Hi @nmehta-septa - We will start investigating on this issue and will update you accordingly. Can you please share the workflow run you have tried for this issue.

Here is the run for resolving package dependency.
run: |
echo "[XCode-Deploy]: Resolving Package Dependencies..."
xcodebuild
-resolvePackageDependencies
-disableAutomaticPackageResolution
-project iosApp.xcodeproj
-clonedSourcePackagesDirPath .

[ijunaidm1]

@nmehta-septa - can you please send me the details about which image version you are using for testing your CI builds.

[nmehta-septa]

@nmehta-septa - can you please send me the details about which image version you are using to testing your CI builds.

Current runner version: '2.323.0'

macOS
15.4.1
24E263

Image: macos-15-arm64
Version: 20250428.1341

[ijunaidm1]

@nmehta-septa - Can you try removing " -clonedSourcePackagesDirPath . " from your below workflow run step and re-run build

Here is the run for resolving package dependency.
run: |
echo "[XCode-Deploy]: Resolving Package Dependencies..."
xcodebuild
-resolvePackageDependencies
-disableAutomaticPackageResolution
-project iosApp.xcodeproj
-clonedSourcePackagesDirPath .

[nmehta-septa]

@nmehta-septa - Can you try removing " -clonedSourcePackagesDirPath . " from your below workflow run step and re-run build

Here is the run for resolving package dependency. run: | echo "[XCode-Deploy]: Resolving Package Dependencies..." xcodebuild -resolvePackageDependencies -disableAutomaticPackageResolution -project iosApp.xcodeproj -clonedSourcePackagesDirPath .

Tried this step now. But, still hangs while resolving package dependency.

[nmehta-septa]

@nmehta-septa - Can you try removing " -clonedSourcePackagesDirPath . " from your below workflow run step and re-run build
Here is the run for resolving package dependency. run: | echo "[XCode-Deploy]: Resolving Package Dependencies..." xcodebuild -resolvePackageDependencies -disableAutomaticPackageResolution -project iosApp.xcodeproj -clonedSourcePackagesDirPath .

Tried this step now. But, still hangs while resolving package dependency.

Also, to mention that after updating Xcode to 16.3 locally on my Mac, i had to manually delete all the packages from Xcode and add them again with newer versions supporting 16.3 to run my project successfully. How can this be achieved on the runner macs?
Of all the package, there is an ElertsKit package which resides in the private repo.
Hope this helps figuring out any solution.

[nmehta-septa]

Is there any other resolution from the one i tried above which was not a success.

[ijunaidm1]

@nmehta-septa - Can you please provide me more information -> can you send me your complete workflow, build logs - for both successful and unsuccessful builds attempts to investigate further more on this issue.
And without this information we won't be able to resolve the issue.

[nmehta-septa]

Can you make this conversation private so that i can share the details.