Overview

This issue is particularly noticeable in Electron-based apps (such as VS Code, Termius and so on), where an abnormal white line appears at the very top of the window when macOS is in Light Mode. Interestingly, it behaves normal when macOS switches to Dark Mode (I have attached screenshot examples). It would be more apparent with a dark background and app is in dark theme. This bug seems to persist across multiple macOS versions. For additional context, this widespread behavior has also been documented in a VS Code GitHub issue: https://github.com/microsoft/vscode/issues/144389. Since this flaw impacts a wide range of applications, it is highly likely a systemic issue that needs to be addressed by the macOS team, rather than individual app developers. This visual glitch is quite distracting during daily use, I have submitted this issue to Apple team. I hope more people could feedback this to Apple to fix it.

I have created an app with (2) subscriptions, and there is no option to attach the subscriptions to my app version to submit for review. The subscriptions currently say waiting for review, but I have no app in review awaiting review. When I submit the build in the draft submittal section should it show the app build AND the subscritpions or just the app build? I have read mixed information

I have an NSTextView subclass that overrides mouseDown: to allow for image resizing. If a user clicks and drags on the edges of an image, I implement custom behaviour that resizes the image (and shows resizing cursors). If the user clicks anywhere else, super's implementation is called. This all works great. As of macOS 27, however, the transition to gesture recognisers instead of overriding mouseDown: means that I should probably be moving away from the above approach. NSTextView now uses the new NSTextSelectionManager to implement selection and dragging via gesture recognisers, although, according to the release notes: Existing NSTextView subclasses that override mouseDown: continue to work through a binary-compatible fallback path. (163365571) It's unclear whether this means that we therefore should still override mouseDown: for custom behaviour in NSTextView, but to me, this, along with the content of Tech Note TN3212, strongly implies that, although it will continue to work thanks to "a binary-compatible fallback", we should entirely move away from overriding mouseDown: in the future. If that is indeed the case, how do we implement custom dragging behaviour--such as for resizing images as in my example--in NSTextView? There still seems to be no way of doing it other than overriding mouseDown:. I had thought that I might be able to add an NSPanGestureRecognizer to the text view and have it fail via its delegate methods if the clicks were outside of an image's edges, but a pan gesture recogniser added to an NSTextView is entirely ignored, presumably because of the private gestures already added. Fortunately everything continues to work for now, but I would like to update my code as much as possible.

Hi, I have a app group registered in mac os app called gorup.com.company.app and i am saving the key/values in userdefaults to this with suitname. within the mac os app the group userdedaults write/read are working fine. I have a switt cli app with same app group registered in the code signing entitilement for the swit cli app. trying to read the group user default key value registered in mac os app in swift cli app returning no value. this was working fine with macOS 26. Is there some changes have been made in macos 27 in regaard to this?

I don’t have a plus sign next to build in my app developer account page, so I can’t upload my app or send it in for review… anyone have this happen to them? Any solutions besides wait for them to fix it internally?

Waiting on in-app provisioning approval. First time submitting the app. The process changed after we submitted initially but its been three months now. Every time I reach out I either get a generic response or nothing at all. What is going on? This has been a horrible experience.

First of all: I love the Xcode implementation of agents. Even right out the gate it works really well on regular projects. However it's rough around the edges--it's beta 1 after all, and I've been prodding around the permissions section. My configuration: macOS 26.5.1, Gemini 3.1 Pro agent via Gemini Enterprise Agent Platform Things were working fine until I got nervous about the agent downloading things using google_web_search and web_fetch since I expected the agent to do that in the cloud but apparently it's automatically downloading stuff to my device, so I disabled those tools out of caution. Later I stumbled upon the skills documents in /Users/USERNAME/Library/Developer/Xcode/CodingAssistant/gemini/.gemini/GEMINI.md which basically tells the agent to: ...take special care to avoid using command line tools like ls or find just to learn basic information about the project or its contents. The user may be prompted to approve every single one of those command line invocations, so it's best to use them sparingly. So I said "Why not?" and deleted the rest of the permissions for better security--you never know what a beta 1 agent might do, and the text implies the worst that'll happen is they'll ask for permission. Now my agent permissions page is empty. After I did that I noticed my agent no longer works in the library project I've been working on. It can't read project files at all, even though things were fine before. Strangely, the agent works just fine in a regular app project--it's just acting up in the library project. Here's a sample of the verbose output: Thinking: I'm currently examining the workspace path provided, which appears to differ slightly from the actual file structure I'm encountering within the PROJECTNAME directory. I'm trying to reconcile this discrepancy. I've realized the paths provided are Xcode workspace-relative and require specific Xcode tools for interaction. I was attempting direct file system access, which is incorrect. I will now attempt to use the appropriate mcp_xcode-tools commands, similar to how I successfully used XcodeLS earlier, to access these files within the project context. I attempted to use mcp_xcode-tools_XcodeRead, but it wasn't recognized. It seems the Xcode tools are not available in my current Plan Mode environment, which is perplexing given previous successful usage. I need to investigate this discrepancy further. AgentLS: The tool failed with no output. Thinking: I'm currently examining the contents of the /Users/USERNAME/Documents/PROJECTNAME/.swiftpm/xcode directory to understand the project structure. OBJECTNAME: 0 items Thinking: I'm currently trying to figure out the best way to access the swift-markdown and MarkdownView source files. It seems they're presented as workspace-relative paths, so I'll need to use the Xcode-specific tools like XcodeRead and XcodeGrep to interact with them. I'm trying to ascertain the precise names of the swift-markdown and MarkdownView source files, as they appear to be workspace-relative. I'm considering invoking the generalist agent, as the mcp_xcode-tools_XcodeRead tool might not be directly available to me at this level, and I need to confirm its accessibility. Note how it successfully used XcodeLS earlier but is now failing. Even if ls is allowed, it still fails. Reinstalling doesn't fix the issue, so I'm stuck without agent support for this library project. Other issues I've noticed Rolling back agent-made changes is painful, slow, and expensive when it really shouldn't be (just undo what was done instead of telling the agent to undo) Agent made changes are often not given rainbow highlights as they should Artifacts don't always show up Please don't make me manually toggle "verbose" every time I open a conversation. If it's not already obvious, I just like verbosity. I'd love to learn more about the Xcode agent tools available to the agent but there seems to be a lack of documentation anywhere. I've been resorting to extracting stuff from /Users/USERNAME/Library/Developer/Xcode/CodingAssistant/gemini/.gemini/ but those are skills, not tools. Still, it's a fantastic resource for a budding developer! I tried to repopulate my agent command permissions to see if that's the cause, but aside from ls, head, tail, grep, pwd, I don't know what else belongs there and reinstalling doesn't repopulate it. There's also no reset button.

I have tried to upgrade to macOS 27 Beta from 26.1 Beta on my MacBook Air M1, but it just doesn't work. I've tried: Software update Installer Terminal both in normal boot and safe boot. Six attempts, none worked. Here are some screenshots: P lease help as I'm freaking out. Thanks in advance! Specs: OS: macOS 26.1 Beta (25B5057f) Chip: Apple Silicon M1 RAM: 8GB

Enrolled and paid on April 19, confirmed via receipt Status still "Pending" as of today Case number 102878889474 open with no resolution Confirmed: correct Apple ID used, 2FA enabled, no pending agreements, no VPN used, legal name matches ID Asking if any Apple staff or fellow developer can advise on escalation

In 2018, Apple staff noted that Safari App Extensions had no direct API to communicate with the containing app, and suggested app groups or opening a custom URL scheme as workarounds. On iOS Safari Web Extensions, app groups work for persistence, but opening the containing app from the native extension/background flow does not appear reliable. iOS launch policy seems to require a direct user gesture, and I have not found a documented way for the extension flow to reliably continue into the containing app. Is there a supported iOS architecture for completing an extension-initiated workflow in the containing app, or is the intended model to persist data and require the user to manually open the app? My current architecture is: JavaScript in the Safari Web Extension extracts article content from the page. The native Extension Handler receives that content via native messaging. The Extension Handler writes an encoded request into the App Group container. The containing app watches the App Group container using DispatchSource.makeFileSystemObjectSource and processes new requests. This works on macOS. It also works on iOS when the containing app is already running. The problem is that on iOS, if the containing app is not already running, there is no app process to observe the filesystem event or process the request. I have tried treating the Extension Handler as the place to do more work, but in practice it seems suited only for short-lived relay/persistence work. It is not a reliable place for my app’s main processing pipeline, which includes rendering article content and uploading it to a third-party service. My app is a Safari-native “read later” style tool that uploads simplified articles to the reMarkable Cloud. The containing app contains most of the functionality: SwiftUI UI, WebKit/WebPage rendering, account/cloud logic, and upload orchestration. The Safari extension captures the article, but the app needs to run to complete the user-visible workflow. From a user’s perspective, tapping the Safari extension toolbar button is the action that initiates the workflow. Is there any supported way for that user-initiated extension action to launch or wake the containing iOS app so it can process pending App Group requests? Or should Safari Web Extensions on iOS be designed only to persist work and then ask the user to manually open the containing app? If manual app launch is the intended model, it would be helpful for the documentation to state this explicitly. The current tripartite model strongly suggests that the JavaScript extension, native handler, and containing app can collaborate as parts of one workflow, but on iOS the containing app appears to be available only out-of-band unless already running.

Bonjour, Je viens ici afin d'exposer mon problème en espérant trouver une solution. En Août 2025 j'ai publié une demande afin de pouvoir développer une application Carplay de type navigation. Ma demande n'a jamais été traitée, j'ai soumis une autre demande en février, puis en avril. Toujours sans réponse. Depuis environ 3 semaines, j'appelle Apple toutes les semaines afin de demander à ce que ma demande soit traitée. J'ai bien évidemment une réponse m'indiquant que la demande était remontée, mais sans retour par la suite. Je commence à sérieusement perdre patience, et ne trouve aucune solution. Quelles seraient vos propositions ? Merci par avance pour vos retours

Hi all, I'm hoping someone here has been through this and can offer some insight, because I've run out of visibility through the normal support channel. The situation: I tried to enroll in the Apple Developer Program and got the error "Your enrollment could not be completed at this time." I opened a support case (ref: 102910424858) on June 7. Support told me my trusted device/phone number is already associated with an existing Apple Developer account. I checked my Account Security settings at account.apple.com — all trusted devices and phone numbers belong to me, and I'm not aware of any other developer account linked to my details. I submitted my passport as requested on June 10. On June 12 I was told the case was escalated to senior advisors. It's now June 19 — a full week of silence since the escalation, and nearly two weeks since I opened the case. No update, no timeline, and no indication of whether anything is still needed from my end. My questions: Has anyone resolved the "trusted device already associated with an existing developer account" block? How long did it take, and what actually unblocked it? Is there a way to find out which account my trusted device is supposedly linked to? Support hasn't told me, and I genuinely don't know of another account. Are there any escalation routes beyond replying to the existing case? (e.g., a different contact form, phone support, a feedback channel that actually gets a response.) I understand these reviews take time, but a full week of total silence after escalation — with my development work blocked the whole time — is hard to plan around. Any pointers from people who've hit the same wall would be hugely appreciated. Thanks.

I've written an exercise application that uses AVSpeechSynthesizer to produce audio countdowns during user workouts: "5" "4" "3" "2" "1" "GO", where each individual digit utterance is spoken one second apart from the previous one. These countdowns are played anywhere between 30 seconds to 30 minutes apart from one another. Additionally, to allow users to play music during their workouts, the entirety of each countdown is performed with the "duckOthers" session category being active. Here is the sequence of events: set "duckOthers" session category, wait 1 second speak "5", wait 1 second speak "4", wait 1 second speak "3", wait 1 second speak "2", wait 1 second speak "1", wait 1 second speak "GO", wait 1 second set "mixWithOthers" session category For the majority of the time, each countdown is performed correctly, each digit is spoken one second apart. Occasionally though, either the "5" digit or "1" digit is not spoken, but the other digits of the countdown are, at their correct times. Using the "speechSynthesizer:didStart" and "speechSynthesizer:didFinish" functions, I can see that a spoken "1" takes 0.5 seconds to perform, and an unspoken "1" takes 0.1 seconds or less. So my questions are: Why is AVSpeechSynthesizer failing to speak an utterance? Can I do anything to prevent this from happening? FYI, I'm currently running my application on an iPhone 17 Pro running iOS 26.5.1, but the problem has occurred on older iOS versions too. Thanks in advance.

TestFlight sends automatic e-mail notifications to beta testers, with the subject "AppName 1.2.3 (123) for iOS is now available to test." etc. At the bottom of these messages is an "Unsubscribe" link, which is a mailto: link that sends an e-mail to the app's support contact address with of the form mailto:developer?subject=Unsubscribe from TestFlight&body=tester wants to stop receiving TestFlight emails about AppName Unfortunately, app developers cannot manage an individual testers' notification settings. This creates a frustrating support loop where the developer has to reply directing the tester to disable e-mail notifications for themselves within the TestFlight app. Am I missing something? (Also reported to Apple as FB19806347)

Hello, the only way to make Siri AI pick up my intent, or action on my intent + entity is that if BOTH use an schema? For example, I have an intent that adopts a schema, but my entity doesn't. That means Siri AI can't do anything with my intent? What if neither use a schema? Siri AI can't do anything with it? I'm asking because schema seems limited to only few domains which I'm not sure how I'll integrate with my apps.

Hello App Review Team, My app Prsi - Card Game (Bundle ID: org.snebesky.prsi) has been in "Waiting for Review" for 10 days. Normally this would not be a concern, but another app on my account, Sedma - Card Game, has been in "Waiting for Review" for nearly 2 months, and previous submissions have also experienced unusually long queue times. I am not requesting expedited review. I am trying to understand whether there is any issue with my account or submissions that may be causing these repeated delays, and whether any action is required from my side. Any assistance would be appreciated. Thank you, Simon

On iPad, a multiline TextField inside a List does not scroll when the text wraps to a new line. The caret and newly entered text can move behind the keyboard until the user scrolls manually. The same code works correctly on iPhone. struct ContentView: View { @State var text = "" var body: some View { List { Color.red.frame(width: 200, height: 500) // When the caret goes to the next line during the text input the scroll doesn't follow it. // So the new text is being overlapped by the keyboard until you scroll manually. TextField( "Run me on iPad and start entering multiline text with keyboard up", text: $text, axis: .vertical ) .lineLimit(1...) Color.red.frame(width: 200, height: 500) } } }

I wonder is anyone at Apple still using Interface Builder for anything… Across Xcode 16.x and 26.x, IB has become increasingly and noticeably slower to open storyboard and xibs. I see zero improvements in Xcode 27 beta. This morning I had both 26 and 27 going fairly quickly into "application not responding" state when trying to render a rather simple layout in storyboard. What's making it worse is that force-quitting the app and starting again leads straight back into the same storyboard and then locks up again. It does not matter if I manage to switch to a .swift file — it's clearly still doing something in the background related to that storyboard and gets stuck. I eventually managed to open just the .storyboard (without the project), fix the offending layout bits and now it's at least not getting stuck although it still takes good 5-6s before it renders a layout with about a dozen components. I assume something with LLM agents is the reason for this issue but come on people — this is infuriatingly incapacitating tool for people like me that are still maintaining UIKit apps.

Hello, We recently transferred our iOS app to a different Apple Developer team. App Store URL: https://apps.apple.com/kr/app/id6759354260 Bundle ID: com.kimchisushi.app Our app uses Sign in with Apple. In our legacy implementation, some existing Apple login users were stored in our backend by email only. For those users, we did not store the original team-scoped Apple user identifier (sub). The app transfer has already been completed, and we are currently within the 60-day migration window. For many users, the migration path is clear: If we have the old team-scoped sub, we can generate or exchange the transfer identifier according to Apple’s migration documentation. If a user signs in after the transfer and the identity token contains transfer_sub, we may be able to use that claim to complete the migration. However, our difficult case is this: Some legacy users used Sign in with Apple with Hide My Email / Private Relay. For those users, we only have the old private relay email address in our database. We do not have their old team-scoped sub. Questions: If we do not have the old team-scoped sub, is there any Apple-supported way to recover or map those legacy users using the old private relay email address? During the 60-day migration window, if one of these users signs in again after the app transfer, will the identity token include transfer_sub even if we did not generate a transfer identifier for that user before the transfer? If the identity token includes transfer_sub, is there any Apple-supported way to correlate that transfer_sub back to the user’s old private relay email address or old app account when the old sub was never stored? If the answer is no, is the recommended recovery path to implement our own account recovery / account relinking flow for these users? We understand that the Apple user identifier (sub) should have been stored as the stable identifier, and that email should not be treated as stable. We are trying to confirm whether there is any official recovery path for the subset of legacy users where the old sub was not stored before the app transfer. Thank you.

I'm trying to start using Xcode Cloud from a project, but the only thing I get is the message saying "Failed to create workflow" with the actual error being "Could not find item. Domain: XcodeCloudKit.XcodeCloudCommandHandler.CommandHandlerError Code: 5". Initially, it did lead me to configuring permissions on GitHub. But it failed in the end probably because the git remote of the project was pointing to another organisation, that transferred the ownership to me. I switched remote to my org, but it didn't help. So, I revoked the permission and deleted Xcode Cloud app from my GitHub in hopes that the config process would start again. It does not. All I get is this senseless error. Is Xcode Cloud functionality functioning at all in Xcode beta 27 for anyone?