Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Setting up Xcode' in CONTRIBUTING.md #24

Open
chrysaora-achlyos opened this issue Jun 6, 2024 · 0 comments
Open

'Setting up Xcode' in CONTRIBUTING.md #24

chrysaora-achlyos opened this issue Jun 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@chrysaora-achlyos
Copy link
Contributor

chrysaora-achlyos commented Jun 6, 2024

Describe the bug

The 'Setting up Xcode' section in CONTRIBUTING.md needs more details.

To Reproduce

"After you have cloned all of the Swift Packages the next step is too change the team identifier and bundle identifier in the signing page of the project settings. You should set these to your own values otherwise the project will not build on your system."

These were not sufficent for me. I got other errors on the 'Signing' section.

Errors

An Application Group with identifier 'group.jellycuts' is not available. Pleas enter a different string.
An iCloudContainer with Identifier 'iCloud.Jellycuts' is not available. Please enter a different string.

I had to manually create uniquely named Application Group and iCloudContainer Identifiers on my developer.apple.com Account, and change signing setup page to match my new Identifiers.

Perhaps one also should change the "Keychain Sharing//Keychain Groups" value which is 'com.zlineman.Jellyfish' to match the Bundle Identifier

Additional context

Perhaps this is obvious stuff, but for someone who has not worked in Xcode for several years, or ever, the onboarding via 'Setting up Xcode' could be greatly expanded.

Admittedly these types of error are hard to find unless starting from a clean slate since once you have done on developer.apple.com, the identifiers remain defines.

If you reclone the project to validate an ongoing documenting of the process, the failures will not happen since your developer account will have the Identifiers already created.

@chrysaora-achlyos chrysaora-achlyos added the bug Something isn't working label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant