Overview

Hi I paid my apple developer account fee on October 23rd. However, my account is still not active. I've emailed support several times. What should I do to open my account? I've been waiting for a long time. Is there anyone here to help?

The most recent KDK for MacOS Sequoia that appears in the Downloads is for MacOS 15.5 (24F74), but the current version of MacOS Sequoia is 15.6 (24G84) and 15.7 (24G207) is in RC. Is there an ETA for the KDKs for 15.6 (24G84) and 15.7 (24G207) to be made available to download? Many thanks for any help.

We're developing a Mac App Store application that embeds the V8 JavaScript engine (via Electron). The application has shipped successfully on macOS 15.x with the following entitlements: com.apple.security.app-sandbox = true com.apple.security.cs.allow-jit = true com.apple.security.cs.allow-unsigned-executable-memory = true com.apple.security.cs.disable-library-validation = true On macOS 26 Tahoe, the exact same signed binary crashes deterministically within ~1.5 seconds on Apple Silicon with EXC_BREAKPOINT (SIGTRAP), ESR 0xf2000000. The crash is in V8's background JIT compilation thread when it attempts to manage memory page protections (transitioning pages between Read-Write and Read-Execute states via mprotect). The crash does not occur in these configurations: macOS 26 + App Sandbox + Intel x86_64 — works macOS 26 + Hardened Runtime (no sandbox) + ARM64 — works macOS 15.x + App Sandbox + ARM64 — works This appears to be a regression in how the XNU kernel handles mprotect calls for sandboxed processes on ARM64 under macOS 26, specifically in the context of the allow-jit entitlement. Has the behavior of allow-jit changed in macOS 26 with respect to runtime code generation memory management on ARM64? Is there a new API or entitlement that V8-style JIT engines should use instead of mprotect-based RW↔RX page transitions?

Hi, I'm notarizing my Electron macOS app (DMG) for the first time with our new Developer ID, and most submissions have been stuck in "In Progress" for over 24 hours. Environment: Team ID: BSS9KAH6Z2 Certificate: Developer ID Application (valid until 2031) Tool: xcrun notarytool submit (Xcode CLI) App: Electron 28, signed with hardened runtime File: DMG (~131MB), 104 files inside .app What happened: Total 19 submissions over the past 24 hours Only 4 were Accepted (2 DMGs + 2 zips) The other 15 are still "In Progress" with no log available The 4 Accepted ones took 1~1.5 hours each codesign --verify --deep --strict passes with no issues Accepted submission log shows "issues": null Apple System Status shows "Developer ID Notary Service: Available" What I've tried: Submitting as DMG directly Submitting as ditto zip of .app Submitting via electron-builder's built-in notarize Using both app-specific password and keychain profile auth Verified entitlements (allow-jit, disable-library-validation) Since some submissions did get Accepted, I don't think there's an issue with my signing or configuration. Is this expected for first-time submissions from a new team? Is there anything on Apple's side that needs to be configured for my team? Any help would be appreciated. Thank you.

I have a medium sized schema which has nested maps which if flattened comes to about 20-25 separate fields. I want to know what is the industry approach and standard. Should it be saved flattened or should it be saved nested as binary data + codable. Also one more thing to keep in mind is we are trying to keep it similar across android and iOS

I enrolled my company Yasmina IT and Development LLC (Wyoming LLC) in the Apple Developer Program as an organization. The enrollment was declined and my account page now shows "Your enrollment request for your company has been declined." Company details: Legal Entity: Yasmina IT and Development LLC D-U-N-S: 141729385 Website: yasmina-it.com Valid EIN and passport on file Developer Support (Robert, case 102818588804) advised me to enroll as an individual instead, but provided no specific reason for the organization decline. I replied on March 19th asking for the rejection reason — no response. I opened a second case (30000003327016) on March 25th — also no response. I am not asking to bypass any requirements. I simply need the specific rejection reason so I can take the correct action. Has anyone experienced this and found a resolution?

Enviei meu app (xek) pra revisão desde terça feira. Recebi a solicitação de ajustes na quarta e depois de ajusta-lo na quarta mesmo, ele ficou travado em “Aguardando revisão” desde então. Um app simples que está no processo de liberação desde terça e desde quarta sem nenhum retorno da Apple, isso eh normal? Tenho outro app que nunca demorou tanto nas aprovações. mandei mensagem por outros canais e nada. Vamos ver se por aqui tenho algum retorno.

We have received a Pending Termination Notice for our Apple Developer account related to guideline 3.2(f). We submitted a formal appeal over two weeks ago but have not received any response. We want to ensure full compliance and have clearly confirmed in our appeal that: -No hidden features exist -No dynamic content switching occurs after review -All apps are independently configured for specific regions Given the lack of response, could someone advise: whether additional steps are required from our side or how we can ensure our appeal is reviewed Any guidance would be greatly appreciated.

I am having issues getting feedback from Apple review to understand whether the game I created is not unique enough or whether it is something else. My game was inspired by Wordle and uses the idea of marking letters as green/yellow to provide hints, but in my view (and the view of all the testers I've had), creates extremely different and unique experience, which is the core goal of guideline 4.1. Core gameplay: The game is real-time multiplayer (or vs an adaptive difficulty computer that mimics human play), where two players each choose a starting hint word, then based on those hint words (yellow/green letters), in 3 minutes, need to find as many unique words that fit those hints. You see what the player guesses and can't guess the same words. Each word gives 1 point, but the last word and 1 bonus word give +5 points. At 120 seconds, a third hint is provided that limits the number of possible options (making it more likely to reach the very final word with +5 bonus or the bonus word if it wasn't guessed yet). There's a rating system, a customisable reward firework system (which you can show off in multiplayer matches). The game is in Lithuanian only, not targeted globally. When playing with another player, there's a voice chat possibility (initial idea was to create a fun way for friends to have quick voice chats daily who like word games). Screenshots used in store listing attached at the end of the post. App review responses I have had close to 10 back-and forth messages with Apple review, trying to ask which parts are the issue (or whether it's the whole concept of the game), but the responses have always been very abstract and vague, no matter how much I ask for specifics, mentioning metadata and in one message, the screenshots. An example response: Regarding guideline 4.1, the app and its metadata contain content that resembles Wordle without obtaining the necessary authorization. To resolve this issue, it would be beneficial to demonstrate your relationship with any third-party brand owners represented in the app. Additionally, the app’s metadata includes third-party content that resembles a popular app or game already available on the App Store. This content may have been sourced from a developer’s website, distribution source, or a third-party platform. Changes I have made so far/things I checked: No mentions of Wordle anywhere in the metadata The colors in the game are not the same ones that Wordle uses Changed the letter elements to be different from Wordle (circles, not squares). Made the screenshots focus on the fully unique items first (the fireworks system, the multiplayer aspect) Sent video recordings to Apple Review to demonstrate how different the gameplay is compared to Wordle Repeated multiple times there is no association with Wordle. Asked if the name "Žodlė" is the piece of metadata that is causing the issue (I would consider renaming if it is) - but got no reaction to this. I have also submitted a formal appeal through the App Review Board more than a week ago but have not yet received a response. For reference, the same app was recently approved and published on Google Play without any copycat concerns. This has been a hobby project of mine for learning about creating and publishing an iOS app, but has turned into something that quite a few people enjoy, so I would like to make sure that I'm not giving up too early trying to publish it. Would love to hear the opinion of someone with more experience on whether there's a chance to get this published or whether any kind of a game that involves guessing words with yellow/green hints would be considered a copycat of Wordle.

The Android MusicKit documentation documents two functions that are not actually exposed/added to the SDK. https://aninterestingwebsite.com/musickit/android/com/apple/android/music/playback/controller/MediaPlayerController.html#canSetRadioLikeState-- https://aninterestingwebsite.com/musickit/android/com/apple/android/music/playback/controller/MediaPlayerController.html#setRadioLikeState-int- Is the documentation stale or is the SDK out of date?

I just submitted a feedback for this (FB9662125) but in the spirit of “share and enjoy”… The cool new Generate Info.plist File feature in Xcode 13 crashes if you try to put an NSLocationTemporaryUsageDescriptionDictionary in your Info.plist file. Here’s a simple repro scenario: Create a minimal iOS app (no Core Data, no tests) Go to target settings → Info tab → Custom iOS Target Properties Click the (+) button on any row to begin inserting a new row Select Privacy - Location Temporary Usage Description Dictionary Click somewhere else or press Return to commit the selection Xcode crashes immediately More generally, it seems that Xcode crashes any time it tries to regenerate your Info.plist file if it contains an NSLocationTemporaryUsageDescriptionDictionary, even if (for example) you manually pasted that dictionary into the file earlier. In that case, merely tapping the (+) button in step 3 above is enough to crash it.

Hello everyone, My app (ID: 6756186616) was submitted on Mar 15, 2026, and has been stuck in "Waiting for Review" status for over 17 days. I contacted Developer Support (case #20000111565861) and received confirmation that it's proceeding normally, but no update since. On average, Apple reviews 90 percent of apps within 24 hours. However, there might be cases that need more review time, but mine exceeds two week. Any recent experiences with long queues? Thanks!

Hello everyone, Since roughly 12 hours i can no longer submit updated to my Apps, i always get a "Unable to Add for Review" with "To submit new apps or avoid potential payment blocks, add compliance information for Directive on Administrative Cooperation–7th Amendment (DAC7).". I of course already a few weeks ago went to the Business sections and selected "No" as it does not apply to us. I tried a lot but cannot make submissions work. I also contacted the Apple support but got no Feedback yet, does anyone have the same issue? What i tried: Switching DAC7 from No to Yes and then back to No again Private Browsing (Cache reset) Checked all other Agreementes, all is fine and "active" I fail to see any issue and assume it is an Apple central issue as they 1st of April rolled out the new DAC7 compliance check. With many greetings Robert

Hi, I think many of us would love to be able to use our GPUs for Jax on the new Apple Silicon devices, but currently, the Jax-metal plugin is, for all effects and purposes, broken. Is it still under active development? Is there a planned release for a new version? thanks!

Description: We are implementing an in-app purchase (IAP) feature using StoreKit where one user can purchase a non-consumable or one-time product for another user within the same app. We would like to confirm whether our implementation approach aligns with Apple’s guidelines for digital content and in-app purchases, specifically regarding entitlement assignment across user accounts. Implementation Context: The app is built using React Native. We use a StoreKit wrapper library (react-native-iap) to initiate and manage in-app purchases. All transactions are completed using Apple’s In-App Purchase system. Receipts are validated on our backend server before granting any entitlements. Use Case Overview: The app supports a family-style model where multiple users (accounts) can be connected. We have two related scenarios: Scenario 1: Existing Connected User User A (purchaser) and User B (recipient) are already connected within the app. User A selects User B and purchases a one-time digital product using Apple In-App Purchase. The app validates the transaction and sends the receipt and transaction identifier to our backend. The backend verifies the transaction and assigns the entitlement to User B’s account. When User B logs into the app, access is granted based on entitlement status. Scenario 2: New User (Not Yet Registered at Time of Purchase) User A purchases a one-time digital product using Apple In-App Purchase and specifies a recipient email address. The backend records the purchase and associates it with the recipient’s email address along with a secure, single-use claim token. The recipient (User B) receives an email containing a secure link and later installs the app and creates an account or logs into an existing account. After authentication and validation of the claim token, the backend attaches the entitlement to User B’s account. When User B logs into the app, access is granted based on entitlement status without requiring any explicit “redeem,” “claim,” or “accept” action within the app. Important Details: All purchases are completed using Apple’s In-App Purchase system. No external payment methods, codes, or alternative purchasing mechanisms are used. The app does not present any in-app UI for entering codes or manually redeeming purchases. Entitlements are applied automatically by the backend after transaction validation. For new users, entitlement is granted only after secure verification (e.g., a single-use token delivered via email) and not based solely on email address matching. The app only reflects entitlement state after user authentication. Cross-Platform Consideration: User accounts may be accessed across platforms (iOS and Android). Entitlements are associated with the user account and reflected after login. Specific Questions: Is it acceptable to assign an IAP entitlement purchased by one user (User A) to another user account (User B), provided the purchase is completed via Apple IAP and the recipient does not perform any in-app redemption or activation action? In Scenario 2 (new user onboarding), is it acceptable to associate a purchase with a recipient email and, after the user signs up and logs in, attach the entitlement to their account following secure verification (e.g., using a single-use claim token), without presenting any in-app redemption or activation flow? Are there any restrictions or recommended practices for granting access to digital content on iOS devices to a user who did not directly initiate the purchase but is the intended recipient within the app’s account system? For cross-platform usage, is it acceptable for an entitlement originating from an Apple IAP transaction to be associated with a user account and reflected across platforms after login? Are there any StoreKit-specific considerations (such as transaction handling, receipt validation, or appAccountToken usage) when assigning a transaction’s entitlement to a different user account than the purchaser? Expected Outcome: We would like confirmation that the described approaches are compliant with Apple’s guidelines and do not violate policies related to unlocking digital content or bypassing In-App Purchase mechanisms. If any part of these flows is not recommended, we would appreciate guidance on the correct implementation approach. Additional Notes: We have reviewed App Store Review Guidelines section 3.1.1 and want to ensure that our implementation aligns with the intended usage.

Does anyone know if Apple is addressing the issue with buttons. They break the fundamental clarity stressed by Human guidelines by exposing an area around an element that is to be tapped. If that area is then defined as a part of the button it should by default then respond to the tap. But it doesn't. My app when you tap on those elements before Liquid Glass ALWAYS RESPONDS. With Liquid Glass, a glancing tap will get the requisite reaction but doesn't trigger the event it should. Also it's confusing that Liquid Glass but not a show stopper that Liquid Glass elements that are disabled respond by flashing at all instead being visible/inert even though nothing happens. It's unnecessary and confusing eye candy. How did the folly of this get passed Apple's UI team and when is it gonna be rectified. I've tried a number of ways to fix it and it just makes the buttons look like crap and then they become more opaque and stuff. Does anyone have a fix for this or is anyone aware of when a fix for this will be released as a part of an OS update? It could be as simple as a setting that defaults to on that says the area/circumference of the circle button (that you NEVER asked for) fully responds to touch events of the target area and it should default to YES!!

Hi, I have created this UI using custom view and not a real sheet component. But the animations and interaction is not as smooth. Earlier I was using sheet component and it was working very well, but then I had a need to add a search button on top of sheet (not inside, that is very important). And so I created this whole sheet with custom view and not the sheet component. But it resulted in loss of fluid working and animations that sheet have. Including changing between Medium detent and Large detent. Is it possible to achieve this UI with native sheet component? Or using some other native swiftui view which will have good animation that sheet has?

My app Comic Locker - Track & Value (Bundle ID: com.kevinmillerxi.thecomiclocker.app) is a first-time submission with two auto-renewable subscriptions. Version 1.0 is in 'Prepare for Submission' with build 21 attached. Both subscriptions (Pro Monthly and Pro Annual) are configured under the 'Comic Locker Pro' subscription group with full localization, pricing, review screenshots, and availability set to all countries. Paid Apps Agreement is active. ITA Part XX compliance is active. However, the 'In-App Purchases and Subscriptions' section does not appear in the main content area of the version page. The Monetization section (In-App Purchases, Subscriptions) shows in the left sidebar, but there is no way to attach subscriptions to the build on the version page itself. I've tried multiple browsers (Chrome and Safari), uploaded a new build, and updated the version number. I also confirmed via sandbox testing on a physical device that Product.products(for:) returns empty for both product IDs. I've seen similar reports in threads 804327 and 820936. Any help is appreciated.

Hi everyone, I am experiencing an issue with App Store Connect and subscriptions. My app (Couple Organizer, App ID: 6748842796) already has an approved subscription group (Premium Plans) with Monthly and Yearly Premium options. Version 1.0.0 is live in the App Store, subscriptions are working. But - When preparing version 1.1.0 for submission the “In-App Purchases and Subscriptions” section is not visible on the submission page so I am unable to attach them to the new version of the app. I tried removing the build from review and re-adding another one but the section still does not appear. Subscriptions show status approved and ready for sale . My questions: Are subscriptions automatically carried forward to new app versions once approved in the first release? Or is there a step I’m missing to explicitly attach them again in every new version? Is this the expected behavior, or is it a bug in App Store Connect UI? Screenshots available if needed. Any advice would be appreciated!

For some reason they appear in the sidebar but not in the main content area, so I can't add them to my app. This must be some sort of internal glitch. Please help!