xcode github

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 “”. 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?

My app uses Foundation Models and Apple Pencil. The app runs great through Xcode; however, due to Apple Pencil support, it has to be run on a physical device. However, Swift Playgrounds on iPad doesn't support iOS 26. I was just wondering if this is something that can be mentioned in submission notes. eg. The app needs to be compiled in Xcode but run on a physical device.” Or should we expect iPadOS 26 support for Swift Playgrounds by the time of submission? Thank you!

Hi all, I’m enrolling in the Apple Developer Program as an Individual and working with a freelance iOS developer. The developer is telling me that on an Individual account, they cannot create or manage signing certificates or provisioning profiles unless I either share my Apple ID credentials or export and share a P12 certificate. My understanding is that with App Store Connect Admin access and Xcode managed signing, a third party developer can build, sign, upload builds, manage TestFlight, and submit apps using their own Apple ID without credential or private key sharing. Can anyone confirm the current recommended Apple workflow for this scenario? Is there any functional requirement to enroll as an Organization in order to avoid sharing Apple ID credentials or P12 certificates? Thanks in advance.

Running the sample Juice app, which demos the Sign In With Apple flow, doesn't seem to work with Xcode 12 beta and iOS 14 beta on the simulator (worked fine on the non-beta versions and on a real device with iOS 14 beta). Once the password for the device's Apple ID is entered, the wheel in the password field just keeps spinning. No error messages and nothing handed back over to the app from the ASAuthorizationController. Anyone else seeing this problem ? Are there any workarounds ?

Hello, I created a code in Xcode on my Mac. Once it was debugged I tried to run it on a simulator. Every time I run it on a simulator I get the white screen with the spinning red box. I'm very new at this and I am creating this app for my own child. As a teacher I couldn't stand the other math fact apps. You'll have to talk to me like an infant.

I've signed an app, zipped it, and uploaded it to github. When I download it on another Mac, I get it can't be opened because it could not be verified for malware. But on that computer, I can verify it with codesign, and it appears to be correct (as far as I can tell). I can copy/paste the app from my other Mac, and that copy will run without problem. sys_policy, however, gives: Notary Ticket Missing File: ReView.app Severity: Fatal Full Error: A Notarization ticket is not stapled to this application. Type: Distribution Error This is the same for the copy that runs, and the copy that doesn't. The difference between them appears to be a quarantine xattr. I can delete this, and the app launches without incident. Is this expected? Why should a signed app be quarantined just because it's been downloaded? The whole point of paying the fee is to avoid the security obstacles...! ;-)

I used to develop iPhone apps about a decade ago and am now back at it with an iPhone and companion Apple Watch app. Why does it suck so bad? I a must be doing something wrong, but what I am doing is out of the box. The majority of the time when I go to build on the watch I get: Previous preparation error: A connection to this device could not be established.; Timed out while attempting to establish tunnel using negotiated network parameters. Which I then first try to force quit the app on the watch and if that does not work, reboot the watch (which is pretty ridiculous). I tried Gemini and it gave me the following explanation: This is arguably the single most frustrating error in the entire watchOS development ecosystem. As an expert, I can tell you that you are not doing anything wrong; you are fighting a fragile architecture. Here is the technical breakdown of why this happens and a workflow to mitigate it without constant reboots. The Technical Why This error message reveals that the issue lies in the Cor