[Camji55]

This change allows building and distributing with Xcode Cloud which I have been doing on my personal branch for some time now. The intent is that existing workflows for browser builds with GitHub Actions and all Continuous Integration actions should still work as-is since Fastlane should override these code-signing settings. This will need some testing before it gets adopted but having the option to build and deploy within Xcode itself would be beneficial for users who'd like to take advantage of it especially if other options still remain available.

I'm also working on a write up on how to setup Xcode Cloud as an alternative to GitHub Actions for browser builds.

Please let me know what I can do to help verify all Fastlane and GitHub Actions remain working!

dev clone of #2476

[marionbarker]

In all other places in this file, where the syntax

DEVELOPMENT_TEAM = "$(LOOP_DEVELOPMENT_TEAM)";

is used, you see this syntax:

				CODE_SIGN_IDENTITY = "$(LOOP_CODE_SIGN_IDENTITY_DEBUG)";
				CODE_SIGN_STYLE = "$(LOOP_CODE_SIGN_STYLE)";
				DEVELOPMENT_TEAM = "$(LOOP_DEVELOPMENT_TEAM)";
--
				CODE_SIGN_IDENTITY = "$(LOOP_CODE_SIGN_IDENTITY_RELEASE)";
				CODE_SIGN_STYLE = "$(LOOP_CODE_SIGN_STYLE)";
				DEVELOPMENT_TEAM = "$(LOOP_DEVELOPMENT_TEAM)";

Where those environment variables are configured in Loop.xcconfig

// Code signing and provisioning [DEFAULT]
LOOP_CODE_SIGN_IDENTITY_DEBUG = Apple Development
LOOP_CODE_SIGN_IDENTITY_RELEASE = Apple Development
LOOP_CODE_SIGN_STYLE = Automatic

I expect @ps2 will request that you follow that model, so I am requesting changes. If he says it is not important, then I will withdraw my request for changes.

[marionbarker]

Test

The functional behavior is independent of whether "Apple Development" is entered directly for the CODE_SIGN_IDENTITY, so these tests are valid and successful.

✅ Mac-Xcode build: no issues building with this change.
✅ Browser Build: Successful Build

[marionbarker]

Having a write up for how to use Xcode Cloud will be excellent. Thank you for doing this.

[Camji55]

@marionbarker thank you for testing! Yes, with this change there can be some variables removed from the xcconfig in the LoopWorkspace repo including:

LOOP_CODE_SIGN_IDENTITY_DEBUG
LOOP_CODE_SIGN_IDENTITY_RELEASE
LOOP_CODE_SIGN_STYLE

Let’s definitely let @ps2 chime in!

Edit: No changes to LoopWorkspace needed

[ps2]

Thanks! LGMT. Removing those other unused settings would be nice too.

[marionbarker]

@ps2 said: Removing those other unused settings would be nice too.

I want to be clear which settings should be removed.

Loop.xcconfig has these 3 lines:

LOOP_CODE_SIGN_IDENTITY_DEBUG = Apple Development
LOOP_CODE_SIGN_IDENTITY_RELEASE = Apple Development
LOOP_CODE_SIGN_STYLE = Automatic

I was suggesting that those variables be used in Loop.xcodeproj/project.pbxproj instead of hardcoding them as is done in this PR.

@Camji55 refers to those being in the LoopWorkspace: LoopConfigOverride.xcconfig file.
But they are not included in the DIY LoopWorkspace file at this time.

[Camji55]

@marionbarker & @ps2 I added a doc on how to get Xcode Cloud running with help from Claude. Lmk if y'all think it's sufficient. I think it's important to note this change does not effect local builds/browser builds.

It might be worth another regression test @marionbarker, as it's been a bit since it was tested last.

[Camji55]

I've got a mirroring PR targeting next-dev here: #2476

[ps2]

Thanks for writing this up, @Camji55! I checked the doc against the current project settings, and it's close. A few things to fix before merging:

1. App group name. Step 3 says the app group is group.com.<TEAMID>.loopkit.LoopGroup. The project builds it as group.$(MAIN_APP_BUNDLE_IDENTIFIER)Group, so it's actually group.com.<TEAMID>.loopkitGroup.
2. Clone branch. Step 1 clones --branch=dev. Most people should build main (the release branch); dev/next-dev could be mentioned as an option for testers.
3. PR description. It still describes enabling automatic code signing, but the diff is now docs only. Signing is already automatic with "Apple Development" on both dev (via the LOOP_CODE_SIGN_* variables) and next-dev (hardcoded), so the description should just say it adds the Xcode Cloud guide.
4. Formatting. In Step 4, "TestFlight (Internal Testing Only)" ended up on a broken nested bullet under Actions; it reads better inline ("an Archive action with distribution preparation set to TestFlight (Internal Testing Only)"). There's also a missing blank line before the --- after the "Keeping current" list.

Checked and correct: the bundle ID derives from DEVELOPMENT_TEAM, LoopConfigOverride.xcconfig ends with the commented LOOP_DEVELOPMENT_TEAM line, LoopWorkspace is a shared scheme (and the right one, since Loop builds without the plugins), the listed package dependencies match Package.resolved, and the 25 compute hours / 90-day TestFlight expiry are right.

Not blocking, but worth considering:

• The central claim is that Xcode Cloud supplies the team even though LOOP_DEVELOPMENT_TEAM is empty in the repo, so nothing needs committing. That matches your experience, but it would be good to confirm once from a fresh fork.
• Loop/Documentation/ only holds images today, so this may be hard to find. A link from LoopDocs or the LoopWorkspace README would help people discover it.
• @marionbarker's earlier change request was about hardcoding the signing settings in the project file, which is no longer part of this diff, so it can probably be dismissed once she's had a look.
• This doc is identical to #2476. If next-dev picks up dev changes when they're synced, merging just one would avoid two copies drifting apart.