When I go to the App Settings menu in Swift Playgrounds and attempt to upload to App Store Connect, I run into the below error screen: I am registered with the Apple Developer Program. Swift Playgrounds is updated to its latest version. This is occurring on both macOS and iPadOS. All the information I put in is valid. Any reason why this would be happening?

Hi, I have recently downloaded the app to start learning how to code in swift and so on. On my first try I have gotten the error stating that ”.swiftpm files cannot be opened”. I have followed some forum posts. I restarted my iPad several times and redown the app several times. I tried to disable the iCloud sync but I think I deleted the iCloud directory entirely that just results in the app closing on any action taken. (such as pressing the “New App” option or choosing the quick actions to make apps). Is there a way to fix this? Any help is appreciate, please ask me to provide any extra needed information.

I followed this guide, and added com.apple.developer.spatial-audio.profile-access as an entitlement to the app (via the + Capability button – Spatial Audio Profile). I have a audio graph that outputs to AVAudioEngine. However, the Xcode Cloud build ended up with this error: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, key 'com.apple.developer.spatial-audio.profile-access' in 'Payload/…' is not supported. This guide says it's available on iOS. Does it mean not on iOS 17? In which case how can I provide fallback for iOS 17?

Some reason the image 'Ren' is not being loaded even though it is in the project how can I resolve this issue in Xcode Playgrounds?

I'm attempting make to make a distribution build of an app. In the Xcode target the supported destinations has only iPhone and build active architectures only is set to NO. I created an archive, then selected Distribute App/ Debugging, but then got this error: Provisioning profile "iOS Team Provisioning Profile: com.abc.def" doesn't include the currently selected device "DT-iPad-XXXX" (identifier YYYY-YYYYYY). I've no idea what this device is, it's nothing to do with me, somebody must have added it to the provisioning profile. But that should be beside the point shouldn't it? Because this device has never ever been connected to my Mac/Xcode and so can't be "the currently selected device". So I tried again. I changed build active architectures to YES and connected an iPhone to the Mac/Xcode and created an archive again. But it was the exact same error. What's going on, why is Xcode saying this iPad is the currently selected device when attempting to make a distribution?

I can sucessfully send pushes to an app (which has been installed/run via Xcode) when the pushes are going through the Apple sandbox server. However I want to test the server is configured correctly to send them through the Apple production server. In the Xcode scheme I tried to change the build configuration to release (and ticked debug executable off) ,however the pushes still only work when sent through the sandbox. Is there a way of installing/running the app using Xcode such that its compatible with the push production environment? Does the APS Environment entitlement come into play here? this only ever says development. (The app is on behalf of a 3rd party company, they've added me to their apple developer account but with limited powers, I can't upload to Testflight nor make an ad-hoc release with with to test with)

I am editing my iOS project in Xcode 16 and want to use the "Swift Compiler - Upcoming Features" section of the build settings to selectively enable the new Swift 6 language features. I have read the instructions for doing this and have dowloaded an Apple sample project and can see that section under the project and target-level Build Settings in the sample project However, when I open my Xcode project in XCode 16 that section does not appear. Is there any way for me to influence how Xcode 16 displays the build settings? In fact, no "Swift Compiler" sections appear at all under my project Build Settings (All | Combined). There is a "User-Defined" section that has the Swift Version, Compilation Mode and Optimization level. The project itself is several years old and was on a very old project version. I have upgraded my project document format to "Xcode 16" but it made no difference. I have compared my project and the sample project in a text editor and both seem to have similar structure. I tried removing unused and outdated settings from my project but that also had no effect. Is there an alternative to deleting my project file and adding the source files to it? I have a large project with multiple targets so that would be something I'd rather not do.

I'm exploring using a handful of frameworks to share code between macOS apps. However, one of these frameworks needs privilege to function. The main app has a helper tool utilizing SMAppService. However, I can't work out if there's a feasible way to use that helper tool to support the framework dependency. Should I be creating a second helper tool for the framework instead? Or am I barking up the wrong tree? Thanks!

Issue with "Mine" Branch Not Displaying After Switching GitHub Accounts in XcodeCloud I have been using XcodeCloud for a while. Recently, in one of my projects, I switched from using my personal GitHub account to a separate GitHub account for work purposes. Since then, when I manually start a workflow, nothing is displayed under the "Mine" section on the branch selection screen. I suspect that Xcode is attempting to list branches from the previously used account, causing branches from my new account not to appear. Where are these old account settings stored, and how can I reset them? For reference: In Xcode's Accounts settings, only the new GitHub account is present—the old account is no longer listed. The git user in the local repository has also been updated to the new one. Any assistance on how to resolve this issue would be greatly appreciated!

When I try to cancel it I get "Your request is temporarily unable to be processed. Please try again". I have since created a new test user from "Users and access", set the renewal for subscriptions to be at 5min. Added the new test user on my iPad where I am developing locally as a sandbox account, and then purchased the same subscription. And same problem happened - I can't cancel it from Apple ID -> Subscriptions. Getting the very same error. Also the subscription there seems to renew on a daily base and not on every 5 minute as I have set it. If I try "Clear purchase history" from the "Users and Access" from AppStore connect - nothing happens, I still see the subscription and I can't purchase it again. Please advise how to proceed in this situation. This happens on iOS 15.5 if it does matter and I am using StoreKit2. Regards, Al

The ESP-Homekit-SDK tool provides the payload. How do we convert it into the actual QR image with the artwork? We have already checked the handbooks but couldn’t find any tool to generate the QR code with actual artwork. I can only see the "Setup Code Sizing and Placement" guidelines for it.

I have an iOS application view that contains an AVCaptureSession, AVCaptureVideoPreviewLayer (created with the AVCaptureSession), and a UIImageView (in the backend the app takes the output of the AVCaptureSession, runs it through a Semantic Segmentation model, and displays the output in the UIImageView). When I pause the app and run the “Debug View Hierarchy”, it shows the UIImageView, the relevant buttons and labels. However, it does not seem to show AVCaptureVideoPreviewLayer that I have set up in my application. Is there some special set up that needs to be done to be able to view Camera Related features? The following is part of the view code, a component that is used to render the AVCaptureVideoPreviewLayer (not sure if this is enough, please let me know if its not): class CameraViewController: UIViewController { var session: AVCaptureSession? var frameRect: CGRect = CGRect() var rootLayer: CALayer! = nil private var previewLayer: AVCaptureVideoPreviewLayer! = nil init(session: AVCaptureSession) { self.session = session super.init(nibName: nil, bundle: nil) } required init?(coder: NSCoder) { super.init(coder: coder) } override func viewDidLoad() { super.viewDidLoad() setUp(session: session!) } private func setUp(session: AVCaptureSession) { previewLayer = AVCaptureVideoPreviewLayer(session: session) previewLayer.videoGravity = AVLayerVideoGravity.resizeAspectFill previewLayer.frame = self.frameRect DispatchQueue.main.async { [weak self] in self!.view.layer.addSublayer(self!.previewLayer) //self!.view.layer.addSublayer(self!.detectionLayer) } } } struct HostedCameraViewController: UIViewControllerRepresentable{ var session: AVCaptureSession! var frameRect: CGRect func makeUIViewController(context: Context) -> CameraViewController { let viewController = CameraViewController(session: session) viewController.frameRect = frameRect return viewController } func updateUIViewController(_ uiView: CameraViewController, context: Context) { } }

A new app I have submitted to Apple App Review for iOS/tvOS/macOS has been rejected for tvOS because it is apparently crashing on launch. The same build has been approved by App Review for iOS and macOS. So far, App Review have not provided me with a crash report, and despite a lot of trying, I cannot get the crash to occur either on a real device or on any version of the Apple TV in the simulator. Apart from constantly asking App Review for the crash report, I don't know how to resolve this, and that means I either have to give up on tvOS for this app, delay the launch, or perhaps start another submission and get lucky with a different reviewer that doesn't experience the crash (but then what if lots of users do?). I've tried running a release build on my devices and the simulator; but I'm not sure how I'm supposed to debug this without a crash to work with. The TestFlight build for the same upload that is crashing for App Review works just fine. Any suggestions would be welcome.

I'm receiving this error when attempting to log into my game and authenticating via Firebase and Game Center. I am using Unity to develop my game and have been able to successfully authenticate with Google Play and Apple Sign In but Game Center is giving some trouble. The error seems easy enough except I have triple checked that I am signed in to Game Center with the profile that is set up in Sandbox Testing. Other things I have verified: I have a provisioning profile and game center is on it. In xCode I have Game Center on my signing capabilities, entitlements, and have the GameKit.framework in my Link Binary with Libraries. Any ideas as to what may be causing this error to throw? Maybe another step I missed somewhere?

I am absolutely shocked and frustrated by the way the Apple Developer Program operates. My team and I recently attempted to launch two completely unique applications through the platform: Goal Hero and Redsport App. Both apps were thoroughly reviewed by our team lead during a code review to ensure they met all the required standards. However, despite all our efforts, Apple repeatedly rejected our submissions without providing clear, actionable feedback. After multiple attempts to communicate and understand the issues, Apple has now banned our developer account entirely and hasn’t responded to any of my inquiries for over a month. We are a legitimate game development studio working under the name Betonred. We’ve always adhered to ethical practices and were excited to expand our business on the App Store after years of success on Google Play. This experience has left us questioning Apple’s commitment to supporting developers, especially smaller teams trying to grow. Honestly, at this point, I am considering restructuring our entire business model to return to focusing solely on Google Play. Apple’s lack of transparency, poor communication, and seemingly arbitrary decisions have made it nearly impossible to work effectively within this ecosystem. Has anyone else faced similar issues? What’s the best course of action here? Apple’s system feels completely broken.

Production build on eas failing for a couple of days. Submitted a request for information day before yesterday, but I was wondering if anyone else has been having this problem. I will post any update from Apple if/when I get it.

The AVCam sample code by Apple fails to build in Swift 6 language settings due to failed concurrency checks ((the only modification to make in that code is to append @preconcurrency to import AVFoundation). Here is a minimally reproducible sample code for one of the errors: import Foundation final class Recorder { var writer = Writer() var isRecording = false func startRecording() { Task { [writer] in await writer.startRecording() print("started recording") } } func stopRecording() { Task { [writer] in await writer.stopRecording() print("stopped recording") } } func observeValues() { Task { for await value in await writer.$isRecording.values { isRecording = value } } } } actor Writer { @Published private(set) public var isRecording = false func startRecording() { isRecording = true } func stopRecording() { isRecording = false } } The function observeValues gives an error: Non-sendable type 'Published<Bool>.Publisher' in implicitly asynchronous access to actor-isolated property '$isRecording' cannot cross actor boundary I tried everything to fix it but all in vain. Can someone please point out if the architecture of AVCam sample code is flawed or there is an easy fix?

I'm testing a video stream (HLS) with AVPlayer. On XCode 14.3 and simulators running iOS 16.4, there is no video image, only black screen. The audio is playing normally, also progress/duration of the video is showing as expected. The problem does not occur on same XCode version with earlier versions of the simulator. Is this a simulator bug? I've also tested it on real device with iOS 16.4 - no problem there.

Hi everyone, I'm getting this error when I try to test my app on my iPhone. If any other developers who have gotten the same error could help, that would be great. Thanks, Oliver

Recently my Mac OS is updated to 15.2 and Xcode and it's tools are updated.I'm working on my react native project to create build using Xcode but I'm getting this error. Anyone please help