Post not yet marked as solved
Hi folks!
I'm looking to see if anyone has had any luck adding their own private Cocoapods as Additional Repositories with granted access in Xcode Cloud?
My understanding was that Xcode Cloud would be able to pick up on these additional requirements, and to an extent it has been able to capture the top level private Cocoapod repository specified has a source in my Podfile.
However when it comes to the private Cococapods specified as dependencies, no dice. I have ensured that the private Cocoapods are in the same repo ecosystem as detailed by the documentation.
Any insight anyone might have on the subject would be greatly appreciated!
Is there any option to access to archived IPA using env variables?
Looking at docs we can access just to xcarchive, using:
CI_AD_HOC_SIGNED_APP_PATH
CI_APP_STORE_SIGNED_APP_PATH
CI_ARCHIVE_PATH
CI_DEVELOPMENT_SIGNED_APP_PATH
I'm trying to build my project with Xcode Cloud but run into this problem:
Cannot update Package.resolved because automatic resolution is disabled
The log shows this line prior to that:
Set default com.apple.dt.Xcode IDEDisableAutomaticPackageResolution to true
Any idea how to fix this?
Post not yet marked as solved
When trying to build other branch than develop it says that my branch may only exist locally. All branches are published in the remote, so i don't know why is this happening...
here is a screenshot of what i'm getting
same goes for the scheme which is marked as shared and pushed to the repo...
Post not yet marked as solved
Today, playing with Xcode cloud I came across a really nasty, undesirable effect of executing steps in an undocumented order.
I had a project with a brand new workflow, I had it linked to my SCM (gitlab self-hosted) and it worked.
Today, it didn't work so I thought, OK, this thing is beta and something must not be working that well, let's reset everything and start over.
I deleted the workflow, then cleared the Xcode cloud data (this removes everything from your Xcode cloud tabs on your product and, unfortunately, from your profile as well).
Then proceed to navigate to your profile to unlink the SCM connection and it appears to be empty.
Because of this, I removed my application in gitlab (which is the token provider for oath) to start again, thinking I did something wrong and I want to follow the steps brand new again.
I went to Xcode, tried to create a new workflow and link my source control provider and... I get a "continue to authorise your repository" button, which is now broken because that application doesn't exist.
The question is, does anybody know of a way to unlink my SCM from my account? The Xcode cloud tab under my profile tells me I need to create a workflow to access anything from there, but I am completely unable to complete that creation as the workflow requires it to be connected to a self hosted instance.
This was extremely easy to get wrong.
Post not yet marked as solved
Hi,
My name is Bin, software engineer at VBreathe in Sydney. We have a mobile app developed in Ionic Angular framework and managed to use xcode cloud to build and deploy the app to TestFlight. It worked well, but the speed is a bit slow, takes around 1 hour to finish the build. After checking the logs, the ci_post_clone.sh script took over 20 minutes to finish, because it installs bunch of tools and node packages, which are necessary to build the app. My question is that is there a way to cache these tools and node packages on xcode cloud, so no need to download & install them in every build?
Cheers,
Bin
Post not yet marked as solved
Frequently when Xcode builds our app we end up (after two hours) getting a build failure: The archive action was stopped because it has exceeded the maximum time allowed to run. Actions are limited to 120 minutes.
Other times, it completely successfully in about 35 minutes. It seems to randomly happen. Is this a known issue?
Post not yet marked as solved
Hi,
I'm trying out Xcode Cloud but can't get it to build in my scenario. The use case is the following:
My project has multiple swift packages that depend on each other. "App" has a local package dependency called "SPMKit". "SPMKit" has a local package dependency called "SPMKit2".
The issue I run into is if "SPMKit2" has any dependencies, it doesn't resolve in Xcode Cloud.
Are local dependencies like this not supported in Xcode Cloud? All the packages are in the same directory as my app. I'd like to not have to put each package in it's own git..
Post not yet marked as solved
Is it possible to set up Xcode Cloud so it distributes the app to different bundle id? (for example, mock, test and release environment)
Right at the moment we are only limited to deploy TestFlight for the bundle ID that configured Xcode Cloud? I would really like to be able automate several different build with different bundle id's...
When i try to archive using Xcode Cloud to a different bundle id that the one configuring Xcode Cloud i get the following errors:
ITMS-90054: This bundle is is invalid.
ITMS-90345: Metadata.Info.plist Mismatch.
When I archive manually it works perfectly fine.
Post not yet marked as solved
When I try to build my iOS app using Xcode Cloud, it encounters an error when trying to resolve packages:
an out-of-date resolved file was detected at [path to package.resolved], which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies
Looking at my package.resolved file, it all seems to be in order.
What can I do to fix it?
I've been building our app to make a release in App Store with Xcode Cloud
Currently the builds are failing with the following error:
The value of CFBundleShortVersionString in your WatchKit app's Info.plist (3.9.0) does not match the value in your companion app's Info.plist (4.7.0). These values are required to match.
This is strange, as in our ci_pre_xcodebuild script we have an invocation of the code
echo "Version: ${versionNumber}"
echo "Setting version string in plists"
echo "iOS Version:"
/usr/libexec/PlistBuddy -c "Set :CFBundleShortVersionString $versionNumber" $CI_WORKSPACE/MainApp/Resources/Plists/Info.plist
/usr/libexec/PlistBuddy -c "Print :CFBundleShortVersionString $versionNumber" $CI_WORKSPACE/MainApp/Resources/Plists/Info.plist
echo "Watch Version:"
/usr/libexec/PlistBuddy -c "Set :CFBundleShortVersionString $versionNumber" $CI_WORKSPACE/WatchApp/Info.plist
/usr/libexec/PlistBuddy -c "Print :CFBundleShortVersionString $versionNumber" $CI_WORKSPACE/WatchApp/Info.plist
echo "Watch Extension Version:"
/usr/libexec/PlistBuddy -c "Set :CFBundleShortVersionString $versionNumber" $CI_WORKSPACE/WatchAppExtension/Resources/Info.plist
/usr/libexec/PlistBuddy -c "Print :CFBundleShortVersionString $versionNumber" $CI_WORKSPACE/WatchAppExtension/Resources/Info.plist
On which the command executes correctly and shows the right output.
Then I don't understand what's going on.
This workflow was working a couple weeks ago and we haven't done a change to it since then.
Any ideas of what could it be?
Post not yet marked as solved
Hi!
In my Xcode Cloud workflow, I have the TestFlight Internal Testing post-action with “App Store Connect Users” included in Groups.
I expected the action would make the builds available for internal testing automatically (just as the builds uploaded from Xcode are). However, they don’t appear in TestFlight: in build history, I don’t see the ASC Users group next to my Xcode Cloud build, and in order to make it available for testing, I have to add the group manually.
After the group is added, the build is published right away, without any extra steps (e.g. export compliance certification, etc.).
Am I doing something wrong here? I’ve tried removing and re-adding the group in the post-action, and even re-creating the entire workflow—all to no avail.
Post not yet marked as solved
HI there,
I just started using Xcode cloud.
When building Xcode cloud, two archives are being generated: iOS and macOS.
The macOS archive always errors out with:
xcodebuild: error: Unable to find a destination matching the provided destination specifier: {generic:1, platform:macOS}
I have no intention of my app running on macOS, but if I knew how to fix that, it might be kinda neat.
But really, it's unnecessary, so how do I turn it off?
Thanks,
Kim
Post not yet marked as solved
All of my builds get stuck on Archive action - it keeps running forever (10+ hours where it took 30 minutes before for a clean build), and never finishes despite having all subtasks finished (green check).
This started to happen on a workflow that has worked reliably for months, right after WWDC22 start - is there a problem with a new version of Xcode Cloud?
Hello,
I am trying out Xcode Cloud for the first time. I could connect to Github in the initial setup and had a few failed builds (package resolution error), which I resolved fairly quickly.
Now whenever I am trying to build, I get the following error:
Xcode Cloud is unable to connect to the repository “<respository-name>”. Reconnect the repository to resume builds.
I am unable to remove the connection from settings as well because it's stuck in a loading state. Is there a way to fix this?
Post not yet marked as solved
I am using Xcode cloud to build flutter app and report error
Post not yet marked as solved
It seems I used the wrong Bitbucket account when setting up my project with Xcode Cloud.
Now when I proceed with the "Grant Access" step, all I get is this error:
Bitbucket Cloud installation was incomplete
Repository was not found. Either the repository does not exist or you do not have permission to access it.
Is there any way to reset this and start over?
Post not yet marked as solved
Hi,
I'm currently researching if we are able to migrate to Xcode Cloud in our project. I encountered one issue.
I run unit tests on Xcode Cloud and I see that they finish in ~150 seconds, but the whole step takes ~530s and there is no information in logs why. I even run the same command on my local computer and it doesn't take that long. Any ideas? Any way to optimize it?
Also one more thing: it looks like Xcode Cloud is not running on M1 machines. Do you know guys if there are plans for Xcode Cloud to take advantage of M1/M2?
We started using Xcode Cloud and also started uploading a build to the TestFlight for internal distribution, it works great. How do i go about adding a changelog (TestFlight Test Details) or is that not supported yet? i'd like to notify internal testers on what's changed. thanks in advance
Without this, we'd either have to update it manually or have to look at Fastlane just for adding changelog.
What machines are used for Xcode Cloud builds? I couldn't find any information on that in the documentation.
Is Xcode Cloud using M1/M2? Or is it going to use Apple CPU in the future?
