Overview

Hello, I’m investigating subscription product discovery in my iOS app, BiteTempo. StoreKit 2 completes the product request successfully but returns an empty array for both auto-renewable subscriptions. The issue occurs on a physical iPhone running through Xcode and also in TestFlight. App and products Bundle ID: shehan.NouriJournal App version: 1.0 (4) Monthly: shehan.NouriJournal.plus.monthly Annual: shehan.NouriJournal.plus.annual Reported storefront: USA Device system version reported in diagnostics: 26.6.1 (23G83) Reproduction Run the app on a physical iPhone through Xcode with StoreKit Configuration set to None. Open the subscription paywall. Request both products using Product.products(for:). Inspect the returned array immediately after the awaited call, before filtering. At that breakpoint, returnedProducts contains 0 values. The empty result is not created by application filtering or by converting a caught error into an empty array. Errors are reported separately. Diagnostic output from the Xcode device run Date: 2026-09-26T10:06:24Z App: shehan.NouriJournal 1.0 (4) Storefront: USA Requested: shehan.NouriJournal.plus.monthly, shehan.NouriJournal.plus.annual Returned: 0 Products: Lookup: completed I also see unavailable plans in TestFlight, although the diagnostic output above is specifically from the Xcode device run. Configuration checked Product IDs match App Store Connect exactly. Both subscriptions have pricing and all-country availability. Both products and their subscription group have English (U.S.) localization. Paid Apps Agreement is Active. Other apps under my developer account have working live subscriptions. Debug and Release use the same bundle identifier and signing team. No local StoreKit configuration file is selected. A Sandbox Apple Account is signed in on the test device. These are the first subscriptions for this app and have not yet been submitted for review. I have retried after completing the missing localization, but the result remains empty. The failure occurs during product discovery, before any purchase or server-side transaction verification. What additional checks or diagnostics would help distinguish an app/signing configuration issue from a sandbox product-catalog availability issue? Is there any additional product state or configuration required for these subscriptions to appear in sandbox? I have also submitted a support request to Apple and can provide a minimal reproduction project through the appropriate support channel. Thank you.

Hi , I'm new here, do anyone know how long it takes for Apple to approve my enrollment?

I have done the payment around 12 hours ago, and i got no mail or anything, it asks to do payment again. The process is done via Apple developer app from Iphone. And when i contacted apple team, they are telling we have no payment from your side, check with your bank. From my Bank and UPI side, the payment was successfully sent to apple. Any Indian dev in this situation who got it sorted out ?

I see a lot of posts about things that need fixing and it looks to me like you all need the help if there’s anything I can do please let me know I know what I can do for you so what could you do for me I’m looking to join your team and help you fix some issues your having maybe an internship or even a developer position either way you could get your money with depending on how well you pay

My dating app has now been rejected by Apple under Guideline 4.3(b) for the fourth time. The reason given is that the App Store already contains enough apps in this category. I understand that Apple does not want duplicate or copycat apps. However, my app is not simply another dating app with a different name and design. The app has several core features specifically built around real-life dating: Real Date Score: Users receive a score based on completed real-life dates. This score is displayed on their profile and helps other users understand whether someone actually goes on dates and follows through. Real Date Planner: Users can plan real-life dates through the app. Group Dates: Users can organize dates with groups of up to 10 people. Group Chat: Up to 10 people can participate in a group conversation. Ghosting Protection: Users who repeatedly ghost after matching can be permanently banned. Mandatory Selfie Verification: Users must complete verification to use the platform. Singles & Couples: The app supports both individual and couple profiles. I have searched the App Store for an app that provides the same concept, particularly a dating profile that publicly displays a score based on completed real-life dates. I have not found one. If Apple considers this app substantially equivalent to existing apps under Guideline 4.3(b), I would like to know: Which existing App Store app provides these same core functionalities, particularly the Real Date Score and the system that permanently bans users for repeated ghosting? I am not claiming that no other dating app has any individual feature that overlaps with mine. Of course there are common dating-app features. The question is whether the overall product concept and core functionality are sufficiently different from existing apps to justify its presence on the App Store. This is not only unfair but also an anti-competitive approach. It is certainly not something befitting a giant like Apple. This is now the fourth 4.3(b) rejection, so I would appreciate clarification from developers who have encountered the same situation or from anyone familiar with how Apple evaluates this type of differentiation.

Hello everyone, I am seeking advice, or hopefully the attention of an Apple Community Moderator, regarding a structural loop I am stuck in with my Apple Developer Program enrollment. My independent corporate enrollment is currently being declined due to an automated historical account association, and standard support channels have not been able to resolve it. The Context • Back in 2015: I was added as an Admin or Team Member to a past client’s Apple Developer account to help them set up their environment. That client never ended up publishing any applications, and that account has been completely dormant for years. • In 2024: I officially incorporated my own separate, independent legal entity in the United States. I successfully obtained our IRS EIN, established a clean Dun & Bradstreet (D-U-N-S) profile, and applied for a fresh Apple Developer Organization Account using my company's official credentials. The Issue Our application was completely declined. Through correspondence, it became clear that Apple’s automated enrollment scanners are flagging my personal identity or Apple Account because of that legacy 2015 admin association. The system is treating my new, legitimate corporation as a duplicate or "associated entity" violation. The Roadblock I am the authorized legal signee for my new US company. This is a completely separate legal and financial entity. I have all official corporate documentation ready for verification, including IRS CP-575 EIN assignments, state Articles of Organization, and active D-U-N-S data matching our exact corporate address. Unfortunately, Tier 1 developer support templates are not addressing this backend identity-link issue. I simply need an Account Specialist or Risk Management team member to manually review the file, sever my identity link from that dead 2015 client team ID, and allow our US corporation to proceed with enrollment. Our business operations and product launch timelines are completely stalled. Has anyone successfully broken out of this legacy association loop? If any Apple Dev Forums moderators are reading this, could you please help escalate this ticket internally? Case ID for reference: 102966456983 Thank you for any insight or assistance. Regards Tanveer

My app has been stuck in “Waiting for Review” for more than five days, without any progress or communication from App Review. Unfortunately, this is not the first time. Some submissions move forward within a few days, while others remain waiting for a week or longer with no explanation or meaningful status update. For developers running an actual business, this is extremely frustrating. App submissions are not simply experiments or hobby projects. Releases, customers, marketing plans, bug fixes, and business commitments can all depend on the review process. I fully understand that Apple needs sufficient time to properly review applications, but leaving a submission sitting at **“Waiting for Review” for an extended period without even beginning the review is difficult to justify—especially without any indication of the expected timeframe. Apple provides developers with strict guidelines, deadlines, and requirements, and developers are expected to comply with them. It is reasonable to expect a similar level of predictability and communication from the review process. Has anyone else recently experienced apps remaining in “Waiting for Review” for 5–7+ days? If so, how long did it eventually take before the review actually started? I would also appreciate clarification from Apple regarding whether these extended waiting times are currently considered normal or whether developers should contact App Review after a certain number of days.

HI, I'm the ceo of Yachtara.com. A boat and cruising navigation app for sailors and cruisers around the world. Yachtara launches publicly tomorrow, Saturday 26 September 2026, at 14:00 CET, on the web and Google Play. We have now been trying since 9 september after spending 3 months in dev/test environments to get our app accepted in Production. We have our global live tomorrow in 15 hours from now. We asked for a response, an expidited review and also have a support ticket open. Can anyone reply and review please ? We would love to not dissapoint all of our apple based users. The review was submitted on wednesday. The App ID is 6763736626 Thanks for your kindness CEO Yachtara.com

Hi, I’m experiencing a TestFlight issue affecting multiple apps in my account. Issue summary: • Several TestFlight builds across all of my apps expired at the same time. • After uploading new replacement builds, neither I nor my testers are able to install them. • Installation fails with the message: “Could not install {App Name}. The requested app is not available or doesn’t exist.” • The build shows as processed and available in App Store Connect. • Testers are already invited and active. • No redeem code is required. I am seeing the same issue on my own device as well. What I’ve tried: • Uploading new builds (incremented version + build number). • Confirmed builds are visible and available in App Store Connect. • Removing and re-adding testers. • Logging out of the app. • Deleting the app from the device. • Restarting the device. • Reinstalling directly from TestFlight. • Restarting TestFlight. Despite this, installation consistently fails with the “requested app is not available or doesn’t exist” error. Expected behavior: • New TestFlight builds should be installable once processed and available. • Testers (and the developer) should be able to install directly from TestFlight. • Expired builds should not block installation of newly uploaded builds. Additional context: • This started immediately after multiple TestFlight builds expired across my apps. • All affected apps were previously installing and testing without issue. • Apple Developer Support has been contacted, but I wanted to check whether others are seeing the same behavior or if there is a known workaround. Has anyone else encountered TestFlight builds becoming unavailable across multiple apps at once, or an install failure after replacing expired builds

Hi, I’m trying to test an independent watchOS app on an Apple Watch Series 6 Cellular that is set up for a child using Apple Watch For Your Kids (Family Setup). My current environment: Apple Watch Series 6 Cellular watchOS 26.6 The Watch is set up for a child using Apple Watch For Your Kids / Family Setup Xcode 26.6 Parent iPhone running iOS 27.0 Developer Mode is enabled on the parent iPhone The Family Setup Watch does not appear as a development device in Xcode/CoreDevice There is no Developer Mode option visible on the Family Setup Watch For comparison, I also have another Apple Watch used for normal development, and that Watch can be detected by the development environment. The issue appears specific to the child’s Family Setup Watch. I would like to understand the Apple-supported development and testing workflow for this configuration. Specifically: Is an Apple Watch set up using Apple Watch For Your Kids / Family Setup expected to be available as a direct Xcode development device? If direct Xcode deployment is not supported, can an independent watchOS app be installed and tested on a Family Setup Watch through TestFlight? If TestFlight is supported, what is the correct workflow for installing the beta on the child’s Family Setup Watch / child Apple Account? Is there another Apple-supported testing or distribution method developers should use for this scenario? I’m specifically asking about an independent watchOS app that can operate without the parent iPhone nearby, rather than a Watch app that depends on an iPhone companion app. I’d also appreciate clarification on the distinction between direct Xcode development deployment and TestFlight/App Store distribution for Apple Watch For Your Kids. Thank you.

I have an iOS app that supports multiple scenes on the iPad, and which has an "Open in Another Window" feature which creates a new window scene. I would like to bring this feature to the iPhone Duo. On the iPhone Duo, of course, creating new windows is only supported when the device is open; when it is closed, creating new windows does not work. (If you try, an error is thrown.) Until now, the way I have checked whether my "Open in Another Window" feature should be available is to check to see if UIApplication.shared.supportsMultipleScenes is true. This has always returned false for previous iPhones and true for iPads. Unfortunately, however, this does not work as expected on the iPhone Duo. On the Duo, I would expect supportsMultipleScenes to return true when the device is open, but false when it is closed. This is not the case: it returns true for all poses. (Filed as #FB24948411 as this doesn't seem right to me.) So it does not help me decide whether the feature should be available. UIWindowScene.ActivationAction does work as expected when used in a menu, with the action auto-hiding when the Duo is in the closed pose. In my app, though, I need more than just an auto-hiding menu item; I need to check whether creating a new window is currently possible for certain UI availability decisions. What, then, is the correct way of checking this, if it's not with supportsMultipleScenes? Given that UIWindowScene.ActivationAction is able to hide itself, I assume there is some better way of checking that I have missed.

Hello, I am playing around with MailKit in Xcode... just created a new App with MailExtension target. When I run it, it's asking if I want to test it with Mail, however, I cannot see the extension in the Mail Settings for enabling it... I a totally newbie here.... what am I missing?

Hello, Our first submission was previously reviewed and we received feedback under Guideline 2.1 because the reviewer was unable to access the app due to a forced update issue. We fixed the issue completely, uploaded a new build, and resubmitted on Friday. The submission has now been in Waiting for Review for approximately 4–5 days with no further messages or requests. Could someone please confirm that the submission is correctly queued and that nothing else is required from our side? App: KIBAKI: Persian Community Submission ID: d1f921a3-9001-4ef2-a392-657860c437cd Current status: Waiting for Review Thank you.

Hi Quinn — following up from DTS case 22070584. I'm working on a Windows compatibility runtime (Wine plus a CPU translator) that runs natively on Apple Silicon. 64-bit x86 Windows programs work fine. 32-bit ones don't, because they need address space in the low 4 GB: guest pointers are 32-bit, and some Windows structures sit at fixed addresses like 0x7ffe0000 that programs read directly. On arm64 I can't get anything down there: task_info(TASK_VM_INFO) -> min_address 0x100ea0000 mmap(0x7ffe0000, MAP_FIXED) -> ENOMEM mach_vm_allocate(0x7ffe0000, VM_FLAGS_FIXED) -> KERN_INVALID_ADDRESS There's also nothing below 4 GB to remove: mach_vm_region finds no entry there at all, and mach_vm_deallocate(0, 4 GB) returns KERN_SUCCESS without changing anything. Building with a smaller __PAGEZERO doesn't help either — every size I tried (0x1000, 0x4000, 0x10000, 0x100000, 0x1000000, 0x10000000, 0x80000000) gets SIGKILLed before main, with no crash report. Ad-hoc signing, the hardened runtime and -no_pie made no difference. I did notice /usr/libexec/rosetta/runtime is arm64 with no __PAGEZERO segment at all and __TEXT at vmaddr 0, so the kernel can clearly do this, at least for platform binaries. Is there a supported way for a third-party arm64 process to map below 4 GB — an entitlement, a spawn attribute, something I've missed? If the answer is no, that's fine, I'd just like to know so I can stop looking and plan around it. I have two small test programs that print all of the above if they'd be useful.

We have a group of Macs that mount SMB shares over 10 GbE with jumbo frames (MTU 9000). Since late June, they have been kernel panicking several times a day with the same assertion: panic(cpu N caller ...): assertion failed: m->m_flags & M_PKTHDR, file: .../xnu/bsd/kern/uipc_mbuf.c, line: 4839 @uipc_socket.c:8260 Panicked thread: dlil_input_en0 Last started kext: com.apple.filesystems.smbfs 6.0.1 Environment Clients: Mac Studio (M1 Max and M1 Ultra) and Mac Pro (2019, Intel with T2), using the built-in 10GBASE-T at MTU 9000 macOS 26.5.1 (25F80), 26.6.2 (25G83) and 26.7 (25G229); it panics on all three Servers: Samba-based NAS, SMB 3.1.1, signing on, encryption off Filed as FB24912731 What we've found It still panics with our third-party EDR fully uninstalled. The Mac that panics needs an active SMB session. A Mac left on the network without a share mounted stayed up through several events that took down the others. Panics are often simultaneous across machines: two to six Macs, with different hardware and different macOS builds, within the same minute. It doesn't need sustained heavy throughput. Some panics came within minutes of reconnecting, during light editing. Setting kern.skywalk.flowswitch.rx_agg_tcp_host=0 did not help. The switch and server links stay up, and spanning tree doesn't change during these events. Only the Macs' ports drop. In one server-side capture, the client stopped sending within about 0.2 ms of receiving a READ response made of 8948-byte frames. That fits the panicked thread being dlil_input. Two existing threads look related Kernel panic using Vagrant synced folders via NFS beginning with macOS 15.4 (FB17853906). A DTS reply there said the issue is in kernel mbuf management and that SMB "is very likely to experience a similar panic." Incorrect packet handling in SMBClient MacOS 26, which describes a race in SMBClient under heavy load above about 10 Gbps. Questions Is this the same underlying issue as FB17853906, and is a fix planned for macOS 26? Our 2019 Mac Pros can't move to a later major release. Is there a known workaround, such as a sysctl, an nsmb.conf option, or a change to MTU or offload settings? Is there logging or a diagnostic we can leave enabled to capture more state at panic time? We can't reproduce this on demand, but between several machines we see it multiple times a day. We can provide full panic reports, sysdiagnoses, and packet captures from both client and server sides.

I have been trying to enroll in the Apple Developer Program for seven weeks, and this has become an unacceptable support experience. During this period, I have exchanged multiple emails with Apple Developer Support and have been contacted by at least six different support representatives. Most replies have repeated the same generic instructions, particularly telling me to use the same device, without providing any specific diagnosis or meaningful resolution. I have followed the instructions, used the same iPhone, submitted the requested identity documentation, enabled two-factor authentication, and kept my Apple Account information up to date. Apple Support also withdrew my previous enrollment and instructed me to enroll again. Nevertheless, the process still ends with the same message: “Your enrollment could not be completed.” After seven weeks and at least six support representatives, I still have not been told: the actual reason the enrollment is being rejected; whether there is an account, device, identity-verification, or regional restriction; whether the previous enrollment was fully cleared from Apple’s backend; which team is responsible for manually reviewing or resetting the enrollment; or when I can expect a real resolution. Repeated template responses are not a reasonable substitute for investigating the problem. If Apple’s system is blocking the enrollment, Apple should be able to identify the restriction and explain how it can be resolved. Is it normal for an enrollment issue to remain unresolved for seven weeks after repeated contact with so many support representatives? Has anyone experienced the same problem and successfully had it escalated to an Enrollment Specialist or Senior Advisor? I would particularly appreciate a response from Apple explaining the correct escalation path for a manual backend review, rather than another repetition of the standard enrollment instructions.

While attempting to read a user’s daily step history spanning backward to the last 7 days, a small but consistent subset of users encounter Error Code 3 with the underlying error description: Error Code 3 "Unable to invalidate interval: no data source available." When this error occurs, we are entirely unable to read their step history. We have received ~10 direct user reports of this within the last couple of weeks.

When I tap on one of the buttons in the ShieldAction extension I want to close the shield and open the parent app instead of the shielded app. Is there any way of doing this using the Screen Time API? class ShieldActionExtension: ShieldActionDelegate {      override func handle(action: ShieldAction, for application: ApplicationToken, completionHandler: @escaping (ShieldActionResponse) -> Void) {     // Handle the action as needed.           let store = ManagedSettingsStore()               switch action {     case .primaryButtonPressed:       //TODO - open parent app       completionHandler(.defer)     case .secondaryButtonPressed:       //remove shield       store.shield.applications?.remove(application)       completionHandler(.defer)         @unknown default:       fatalError()     }   }   }

Hi, I’m testing the new NowPlaying framework on iOS 27 using Xcode 27 and an iPhone 17 Simulator, and I’m seeing some behavior that I’m trying to determine is a Simulator issue or something incorrect in my implementation. I have a local AVPlayer playing an MP3 and a MediaSession conforming to MediaSessionRepresentable. The session publishes MusicContent with static artwork, AnimatedArtwork using the .tall aspect ratio, a MediaPlaybackSnapshot, and commands for play, pause, previous, next, and seek. The strange behavior is: I start playback and call requestToBecomeApplicationPrimary(). It succeeds and isApplicationPrimary becomes true, but isSystemPrimary remains false. I lock the Simulator for the first time. There is no Now Playing UI or metadata. I unlock it and return to the app. After recreating/re-registering the MediaSession and calling requestToBecomeApplicationPrimary() again, isSystemPrimary sometimes becomes true. When I lock the Simulator a second time, the Now Playing UI finally appears and the animated 3:4 artwork works correctly. However, the Lock Screen card still does not show the expected play/pause/previous/next buttons. It only shows the title, artist, progress bar, and volume control, despite those commands being included in commands. When the second session succeeds, the framework also starts requesting the artwork as expected: applicationPrimary: true systemPrimary: true Animated preview requested: (1206, 1608) ratio: tall Static artwork requested Animated video requested: (1206, 1608) ratio: tall Calling requestToBecomeSystemPrimary() directly has also consistently returned: internalFailure Playback itself continues correctly throughout all of this. So I’m trying to understand whether anyone else is seeing similar behavior with the iOS 27 Simulator: MediaSession becoming application-primary but not system-primary on the initial playback Now Playing metadata only appearing after a lock/unlock/re-registration cycle media commands being supplied but playback buttons missing from the Lock Screen requestToBecomeSystemPrimary() returning internalFailure I have not yet tested the same build on a physical iOS 27 device, so I’m particularly interested in whether this is currently a known Simulator limitation/bug or whether there is another step required when publishing a local playback MediaSession. Thanks!