Hi Apple Developer Forums and Final Cut Pro team, I am developing a Final Cut Pro Workflow Extension focused on speech-to-text / subtitle recognition and generation. The extension runs inside Final Cut Pro, analyzes clips, generates accurate subtitles (often hundreds of individual elements), and allows users to drag the generated subtitles directly back into the FCP timeline as a clean, editable Compound Clip or Storyline. We are implementing this drag-and-drop functionality using the official pasteboard mechanism (com.apple.finalcutpro.xml and versioned types such as com.apple.finalcutpro.xml.v1-10). While the high-level documentation is helpful: Supporting Drag and Drop for Data Sent to Final Cut Pro FCPXML Reference Designing Workflow Extensions There is still no detailed public specification for the exact internal XML structure that Final Cut Pro expects for a drag operation to reliably result in a usable Compound Clip (or direct Storyline insertion), especially when dealing with large numbers of subtitle titles. After extensive systematic testing (multiple rounds over several weeks, with full experiment logs), we have observed the following: Short subtitle sequences work with many different structures (various combinations of , , , inline titles, etc.). Long subtitle lists (800+ individual elements) only succeed reliably when the outer structure uses a specific shell: root= containing + (often combined with a mainflow sequence and inner / layers). In all working cases, the dropped result appears as a “fake” / nested Compound Clip that requires 2–3 Break Apart (unpack) operations before the real editable Storyline with individual titles is revealed. Almost all other structures — pure as root, as root, wrapper layers, direct inline titles without the clip + gap + storyline shell, etc. — are immediately rejected by Final Cut Pro when the subtitle count is high. This undocumented behavior forces third-party Workflow Extension developers to engage in time-consuming blind guesswork and reverse-engineering just to achieve basic, reliable drag-and-drop integration. Our request: We kindly ask Apple to publish a detailed, official specification for the Draggable FCPXML Text Protocol (or expand the existing FCPXML Reference) that clearly defines: The minimal and recommended XML structure for dragging content into the timeline as a Compound Clip or Storyline. Exact roles and requirements for , , , , , and any implicit “mainflow” patterns. Best practices for handling large numbers of nested titles/subtitles. Reasons why certain nesting patterns are rejected or produce multi-level fake compounds. Any version-specific differences across FCPXML DTD versions. This specification is critically necessary for the FCPX Workflow Extension ecosystem. Reliable drag-and-drop from extensions back to the timeline is one of the most valuable integration points for subtitle/caption tools, transcription services, title generators, and other workflow utilities. Without clear guidelines, developers waste significant time on trial-and-error, leading to inconsistent user experiences and slower innovation in the Final Cut Pro community. We are more than happy to share our complete experiment logs, working and failing XML samples, and GitHub repository with the documentation or engineering team if it helps accelerate this. Thank you in advance for any official clarification or guidance. Clear documentation in this area would greatly benefit both developers and Final Cut Pro users.

Hello, I enrolled in the Apple Developer Program approximately 20 days ago. My enrollment has been stuck “In Review” since then with no update, no request for additional documents, and no communication from Apple. I submitted a support request 10+ days ago and have received no response. Submit another request without update.. Here is my situation: • Enrollment status: In Review • Support case submitted: ~10+ days ago, no reply • Country: Canada I have verified that: • Two-factor authentication is enabled on my Apple ID • There are no pending agreements in the developer portal • All enrollment information was submitted correctly I kindly request that someone from the Apple Developer Program enrollment team review my case and provide an update or escalation path. Thank you.

I am trying to find a datasheet containing information such as "Key Exchange / Key Agreement / Key Establishment Protocols Used", "Digital Signature Algorithms Used", "Hash Algorithms Used", etc. Any information would greatly appreciated.

I'm trying to enroll in the Apple Developer Program as an individual, but I keep hitting a dead end. Every time I attempt to enroll, I get a generic error saying my enrollment could not be completed at this time, with no detail on why. I've reached out to Apple Developer Program Support by email about this but haven't received any response, which is why I'm turning to the community here. On my end, I've ruled out all the common issues. Two-factor authentication is on, I have a valid major credit card on file, I'm enrolling through the web rather than the Developer app, no VPN is active, and my Apple ID is email-based. If anyone from Apple can take a look at my account, or if someone in the community has run into this same error and found a fix, I'd really appreciate the help. Thanks in advance.

Hola, compre el 25 de marzo la membresía de desarrollador, pero aun mi cuenta sale pendiente, no subo datos de empresa ya que soy freelance. Cuanto podría tardar la aprobación de la cuenta. Ya mande dos ticket a soporte pero nada responden

Hi everyone, I am an iOS developer from Ecuador and I am writing to ask if there's any way to fix my issue. After some initial struggling with my phone number not being able to receive Apple verification messages, I was able to register an Apple ID and use that Apple ID to enroll into the Apple Developer Program. Currently, I am stuck at the step of paying the subscription fee. When I try to pay for the 99$ enrollment fee, I receive an "Order Acknowledgement" e-mail from Apple but the payment is never processed. I have tried with multiple debit cards: 2 times with my main crypto debit card emitted from a Hong Kong bank 1 time with a debit card emitted from a local Ecuadorian bank 1 time with a debit card emitted from a US bank In all these cases the result is the same: the same order acknowledgement e-mail but nothing more happens. I even tried asking the support via e-mail (the only method that is supported in my country), but no one replies. Does anyone have any tip on how to overcome this situation?

After updating to Xcode 26.4 and also the update on the simulator the copy paste feature in the simulators doesn't work anymore and i can't build my app without it because the user has to copy and paste api keys in it. Is there an solution for it I have tried to install an other simulator ios version but then the simulator doesn't work on the the new xcode. Have someone already found an solution?

Hello, I am facing a critical technical blocker regarding the Family Controls (Screen Time API) entitlement for my app extensions. Current Situation: My parent app (com.hayashikento.FocusPact) is already approved for the Family Controls (Distribution) entitlement. However, the associated DeviceActivityMonitorExtension (com.hayashikento.FocusPact.FocusPActMonitor) and ReportExtension (com.hayashikento.FocusPact.ReportExtension) are still pending entitlement approval. Technical Issue: Because the extensions lack the Distribution entitlement, ManagedSettings and DeviceActivity triggers (like intervalWillEndWarning) are ignored by the system when testing via TestFlight or in a non-development environment. As a result, I am unable to verify the core "automatic re-blocking" logic and "usage reporting" features in a real-world scenario. This has completely halted the final QA and TestFlight phase of my project. Requests: Could an Apple engineer verify if these extension IDs can be linked to my existing approved parent app entitlement? Is there a specific process to expedite the "linking" of extensions when the main app is already authorized? App Details: Parent App Bundle ID: com.hayashikento.FocusPact Extension IDs: com.hayashikento.FocusPact.FocusPActMonitor, com.hayashikento.FocusPact.ReportExtension Apple ID (App)6759132649 I have already submitted the web request forms, but the lack of synchronization between the parent app and extensions is preventing my MVP launch. Any assistance would be greatly appreciated. Thank you.

Hello. Our application performs encoding and decoding of large json files which sometimes may take up to 1,5GB of RAM memory. We understand that this may be a problem for devices with low RAM memory (3GB). But before iOS 26.4 we didn't have much occurrences (3 for the last 90 days). Starting from iOS 26.4 it started to crash a lot. Can the reason be that iOS 26.4 occupies more RAM memory so there is less memory left for our app? Or maybe starting from iOS 26.4 there is less RAM memory allocated per app? The crash message is Fatal error: failed to allocate 392 bytes of memory with alignment 8

When opening a project or workspace in Xcode 26.4 the most recently active scheme is not restored. Instead, the scheme reverts to the first scheme in the list. I've tried opening and closing Xcode a few times, and removing the user data for a workspace. No luck. Any suggestions or workarounds?

Hello, I am facing a critical technical blocker regarding the Family Controls (Screen Time API) entitlement for my app extensions. Current Situation: My parent app (com.hayashikento.FocusPact) is already approved for the Family Controls (Distribution) entitlement. However, the associated DeviceActivityMonitorExtension (com.hayashikento.FocusPact.FocusPActMonitor) and ReportExtension (com.hayashikento.FocusPact.ReportExtension) are still pending entitlement approval. Technical Issue: Because the extensions lack the Distribution entitlement, ManagedSettings and DeviceActivity triggers (like intervalWillEndWarning) are ignored by the system when testing via TestFlight or in a non-development environment. As a result, I am unable to verify the core "automatic re-blocking" logic and "usage reporting" features in a real-world scenario. This has completely halted the final QA and TestFlight phase of my project. Requests: Could an Apple engineer verify if these extension IDs can be linked to my existing approved parent app entitlement? Is there a specific process to expedite the "linking" of extensions when the main app is already authorized? App Details: Parent App Bundle ID: com.hayashikento.FocusPact Extension IDs: com.hayashikento.FocusPact.FocusPActMonitor, com.hayashikento.FocusPact.ReportExtension Apple ID (App)6759132649 I have already submitted the web request forms, but the lack of synchronization between the parent app and extensions is preventing my MVP launch. Any assistance would be greatly appreciated. Thank you.

I purchased the Apple Developer Program on March 26, 2026. Payment went through immediately. I have the invoice (UA31019584), the order confirmation (W1318171870), and €99 charged to my card. Apple had no problem taking my money within seconds. Five days later: Account status: Pending Portal still says "Purchase your membership" and asks me to pay again App Store Connect: inaccessible TestFlight: inaccessible I contacted Apple Developer Support on day one — both by email and callback request. I now have three open cases and have received exactly zero responses: Case ID: 102856462218 — Program Purchase and Renewal Case ID: 102853916886 — Program Purchase and Renewal Case ID: 102853919455 — Program Enrolment Not a single acknowledgment. Not even an automated "we're looking into it." Nothing. My app is built and ready. I have testers waiting. I cannot distribute anything — not even through TestFlight — because Apple took my payment and then stopped responding. I see dozens of threads on this forum from developers with the exact same problem going back months. Paid memberships stuck on Pending, no activation, support completely unresponsive. This is not an isolated case — this is a systemic failure in the enrollment system that Apple has apparently chosen to ignore. I am based in the EU and I am fully prepared to pursue this through consumer protection channels if this is not resolved. You cannot charge someone for a service and then refuse to provide it or even respond to inquiries. For the world's biggest tech company that is built on software, this is practically a joke. I don't remember the last time seeing an issue like this from any other company in my whole life living on this planet. New developers practically cannot join and publish apps on Apple anymore. But if you are happy to pay, they will let you. And after payment, they will put a notice at the top reminding you to 'complete your purchase' and pay again. Is this really Apple or has this company been hijacked by some retard?

I added a workflow and it seemed to work fine so lets add them all ! I added a second workflow and it seems to see the repository but not the branches in the repository. I have googled and even asked AI. Checked and it's installed with all repo access on Github Removing the repo .. adding it back Deleting the workflow and adding it back Adding the workflow from the browser Adding the workflow from XCode Nothing seems to work, but the first one I created works. Is there paid support for Xcode Cloud ? I s there a version control that works better with Xcode Cloud? Any suggestions are appreciated.

We are encountering an issue in an iOS application where functionality works correctly in Debug builds but fails in Release builds distributed via TestFlight. Details Debug (No Optimization -Onone): Works correctly Release (Optimize for Speed -O): Fails Release with -Onone: Works, but app size nearly doubles Context The issue is related to integration with the Microsoft ONNX runtime library. It appears that the Swift/Clang compiler is aggressively optimizing certain parts of the code in Release builds, possibly removing or altering required logic. Observations The issue started appearing with recent iOS/Xcode updates. No code changes affecting this logic were made recently. Behavior strongly suggests optimization-related side effects. Questions Are there known issues with aggressive optimization (-O) affecting third-party libraries? Are there recommended flags to selectively disable optimization for specific modules or functions? Any tools or diagnostics to identify what is being optimized out? Temporary Workaround Using -Onone resolves the issue but is not viable for production due to significant increase in app size. Any guidance would be greatly appreciated.

Im working on my laptop with Mac OS 15.7.5 and Im using Xcode 26.0.1 and Im trying to simulate the code I've written. It only allows me to simulate on iPhone 16e but it never finishes loading, I also tried using my personal iPhone as a simulator but that doesn't work either. Could it possibly be my storage on why the simulators don't work?

I am developing a productivity app called "FocusPact" using the Screen Time API (Family Controls). Current Status: The parent app bundle ID (com.hayashikento.FocusPact) has already been approved for the Family Controls (Distribution) entitlement. I have recently submitted a new request for the DeviceActivityMonitorExtension bundle ID: com.hayashikento.FocusPact.FocusPActMonitor. The Issue: Currently, the extension only works while debugging with Xcode (Development entitlement). When the device is disconnected, the intervalWillEndWarning and intervalDidEnd triggers are ignored by the system because the Extension ID lacks the Distribution entitlement. This is a critical blocker for my MVP testing phase on TestFlight, as I cannot verify the core "automatic re-blocking" logic in a real-world environment. Request: Could any Apple staff or engineers help expedite the linking of this extension ID to my existing approved entitlement? Parent App ID: com.hayashikento.FocusPact Extension ID: com.hayashikento.FocusPact.FocusPActMonitor I would greatly appreciate any guidance or assistance to resolve this so I can proceed with user testing. Thank you.

I am unable to install due to the following error: "can't install the software because it is not currently available from the software update server" Mac OS: Tahoe 26.1 CLI: Iterm2 Command : xcode-select --install Output: Command transitions to a GUI installer and attempts to download but fails with the attached error. As a result I am unable to proceed with installing Homebrew from CLI or downloaded pkg

I'm pretty sure a lot of people had this issue already, I just can't find a concise reply with what I should do. I'm trying to enroll to the developer program, I live in an EU country. It requires me to enter my Driver's License, I also tried my official document as per online recommendation, but it didn't work. I'm legal here, but not a citizen or EU passport holder. I don't know what to do as this is my only official address.

Hi, I am attempting to setup Xcode Cloud for my project. The repository for the project is in Azure Devops. When I look on the internet, I get the answer: Go to AppstoreConnect, your app, Xcode Cloud and configure the repo. However, in my version of Xcode I am immediately sent back to Xcode to configure it. When looking in this forum, I see some old Posts from 2022 and 2024 without any answer. I assume I need to pick 'Github Enterprise' as the GIT provider. If I do, It attempts to connect to devops.azure.com, which sounds about right. But then I get a permission error. I would like to configure Xcode Cloud to access Azure Devops using one of the PATs that I have configured. Has anybody been able to Mae this work? Or should I make a Mirror Repo in Github (ir BitBucket or Gitlab) and let Apple connect to that? Kind regards Wouter

I’m currently working on a macOS application to control a USB camera’s optical zoom via a direct USB connection. My situation: I am using a USB camera that supports optical zoom. I downloaded an open-source project, CameraController. The prebuilt binary provided on GitHub works perfectly, and I can successfully control the camera’s optical zoom. However, when I build and run the same project from source in Xcode, the zoom control UI appears disabled (grayed out). The project compiles without errors. Additionally, I attempted to implement zoom control myself using the UVC protocol in Swift . However, it seems that the zoom control commands are not successfully sent or recognized by the camera. Questions: Why would the prebuilt app work, but the same source code built locally results in disabled zoom controls? Are there known limitations on sending zoom control requests via USB on macOS? Is there a recommended modern approach for controlling optical zoom programmatically via Swift? Any insights, debugging suggestions, or references would be greatly appreciated. Thanks in advance!