Overview

I got this error when using iPhone Duo Simulator on Xcode 27.1 iPhone Duo’s iOS Simulator platform doesn’t match App.app’s supported platforms. You can change App.app’s Base SDK or Supported Platforms to support iPhone Duo. My Supported Platforms is already iOS. How to fix this one properly?

Hello, The initial release of my first app under my new developer account has remained In Review for more than 11 days, with no messages or requests for further information in App Store Connect. ID: 6786302718 Submitted: September 22nd 2026 In Review since: September 25th 2026 Developer Support case: 102983715714 This is the app’s third review cycle. The first two submissions were reviewed relatively quickly and returned with specific issues, which I addressed before resubmitting. The current corrected submission has now remained continuously In Review for significantly longer than either of the previous reviews. I submitted an App Review Status enquiry on October 2nd but have not yet received a response. I have worked on and submitted iOS apps since 2013. I understand that some submissions require additional verification and that review times can vary, but I have never experienced an app remaining In Review for this long without any communication. This is well outside any review experience I have had previously, and the lack of information is extremely frustrating. The delay is preventing me from launching the app and submitting the next update to support the iPhone Duo. I do not know whether my submission is actively progressing, waiting for an internal review, or requires information that is not visible to me. I am increasingly concerned that the submission may be stuck, and having no way to confirm its status is causing me considerable worry and stress. I would simply appreciate confirmation that the submission is progressing normally and that no action is required from me. If possible, could an Apple representative please check or escalate the existing Developer Support case? Thank you.

QLPreviewController renders plain text as hyperlink in document downloaded from my ios app. xcode version 27.0, ipadOS - 26.5, ipad Air 11inch(M4). Expected behaviour - plain text should be shown as plain text only. Current Behaviour - When i download a document(excel file) with multiple tables(tabs), it shows some plain text as hyperlink, clicking on those links doesnt work. This works fine in case of single table(tab) document. When it happens The problem shows up only when all three are true: The user downloads the whole report as Excel ("Table Data"), which gives one file with many sheets. 2.The file is opened in the built-in iOS Quick Look / Files viewer. 3.At least one sheet has a real link in its header, footer or cells. It does not happen: 1.In the single table export (one sheet). Tapping the Google link shows the "Leave Files and open this link?" popup and opens the link. 2.In Microsoft Excel (Windows, Mac, iOS, web), even with the same multi-sheet file.

A newly released iOS app has been available for approximately three weeks, but I still cannot find it by searching its exact name in the U.S. App Store. Several U.S.-based people whom I asked to independently test the same search were also unable to find it using their own devices and accounts. The same issue occurs on Apple’s public U.S. App Store website. The app’s direct link works normally, and searching for the developer name returns the app, but searching for the exact app name only returns unrelated apps. I submitted Developer Support case 20000142933730 approximately one week after the app became available, so the issue was already well beyond the normal 24-hour post-approval period. Apple Support reproduced and documented the issue before the case was escalated. After multiple phone calls and emails, the case has been assigned to three different Advisors. The current Senior Advisor says the app appears in her search environment and asked me to provide a screen recording. I sent the requested screen recording and screenshot, but was subsequently asked to provide the same evidence again. My questions have not been answered. Her response also referenced an unrelated case number. I do not intend to criticize any individual Advisor. However, I am increasingly concerned that the complete case history and submitted evidence have not been reviewed, and that the case may be stuck in a Support loop rather than reaching the team that can investigate App Store search behavior. This issue is significantly delaying the app’s launch and preventing users from discovering it through normal App Store search. Could an Apple staff member please help confirm whether case 20000142933730—including Apple’s previous reproduction and the screen recording and screenshot I submitted—has been forwarded to the Engineering team responsible for App Store search? If any other developers have experienced inconsistent exact-name search results across different App Store user environments, I would also appreciate hearing how the issue was resolved.

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

When using a background color for a UINavigation controller it seems the header does not extend to the top of the device for iPhone Duo when its closed in portrait mode. See screenshot. It should fill the entire 'status' bar up to top of device, Landscape correctly works, its just Portrait. Any thoughts on if this is 'expected' behavior? Seems odd to not just extend the navbar alll the way to the top.

Hello everyone, I am hoping to get some advice or guidance from the community regarding the Apple Developer Program organization enrollment process. Currently, our enrollment status is showing as "Your enrollment is being processed." We are a bit concerned because our previous enrollment application remained in this state until it unfortunately expired, which meant we had to start the process over with a new one (Enrollment ID: 6XP6S5L3Q2). We want to make sure we are doing everything correctly on our end so this one can go through smoothly. Here is where we are at so far: Successfully verified our D-U-N-S number and legal entity details. Opened a support case via the Developer Support portal to follow up. Our team has finished building our app and we are incredibly excited to share it on the App Store! We are just eagerly waiting on this final enrollment step to move forward. Has anyone else experienced a similar delay or had an application expire while in processing? If so, could you share any tips on the best way to gently follow up with support or reach a review specialist to ensure all our documents are in order? Any help, insights, or advice you could share would be greatly appreciated. Thank you so much for your time and help! Warm regards, JOY CLOUD SERVICES LLP

Our team (Team ID WQS88HK2V3) began notarizing with a new Developer ID Application certificate on October 2nd. Since then, no submission has completed. Every one sits at "In Progress"; two production app uploads from October 2nd are still there after three days. To rule out our app, I submitted a minimal signed hello-world binary (a main that returns 0, signed with hardened runtime and a timestamp, zipped with ditto). Today's one, 151fa89a-f115-4b8b-9713-d3c733f7b3ad, submitted 2026-10-05 15:32 UTC, was still "In Progress" after 20 minutes with --wait. Earlier hello-world tests took many hours to reach "Accepted"; one from October 3rd (1274bb4c-a0a5-4af6-a991-ac8fc3194656) is still "In Progress". What we've verified: notarytool history authenticates and lists every submission under the team, so credentials and upload are fine. codesign -dv shows TeamIdentifier=WQS88HK2V3 and the Developer ID chain. The Apple Developer Program License Agreement was accepted on 2026-10-02; nothing is pending on the Membership page. System Status shows the Developer ID Notary Service as available. No App Store Connect app record exists, which I understand is expected for Developer ID distribution. Stuck production submissions: 258583f0-2322-4048-a97c-f290c63d849c — 2026-10-02 17:45 UTC a7d7b1b1-286f-47ae-ab51-f20b0634f27e — 2026-10-02 19:41 UTC We have a Developer Support case (102984780721); so far the guidance has been to upload to App Store Connect, which doesn't apply to Developer ID notarization. Is there a known hold on first submissions from a newly provisioned team, and is there anything on our side that would clear it? This is blocking a release to our customers.

In Xcode 27.1 RC 1 there is a regression bug displaying incorrect accent color across the app. It worked correctly in Xcode 27.1 Beta 1. It affects borderPromintent top bar buttons and tab bars: https://x.com/kulik_wojciech/status/2107252543709692166?s=20 I already reported it as a bug: FB25074768

Submitted my third brand new on 15 Sep. Three weeks later it's still sitting in "Waiting for Review". Sent an expedite request on the 27th, heard nothing. By now the build in review is already pretty outdated, and I might have to wait another two weeks after sending the newer version. But I don't want to pull it and end up at the back of the queue. Anyone else seeing waits this long right now? And if it gets approved, does an update usually go through faster, or should I swap the build while I'm waiting?

Hi everyone, I am facing what appears to be a severe backend system loop, and I desperately need an Apple Engineer or App Store Connect Specialist to investigate my account. My app finally changed status, but it has now been actively stuck on "In Review" for 9 consecutive days. There have been no updates, no rejections, and no communication. This current freeze follows a horrific chain of consecutive system glitches: 17 Days: Wasted waiting for my enrollment to clear due to an initial glitch. 12 Days: Frozen on "Waiting for Review" despite an officially approved expedited request. 9 Days (Current): Permanently stuck "In Review". In total, I am on Day 38 of this nightmare. Since a normal "In Review" phase typically takes 24-48 hours, a 9-day freeze heavily indicates my binary is technically locked or stuck in a backend loop. Standard support (Cases 102974693297 and 102976576467) only provides automated "it is proceeding" templates. Has anyone else experienced a 9+ day "In Review" freeze? How can I get a human technical specialist to manually unfreeze this submission? Team ID: 8A9595UHD7

Hi, Over the past few months, I developed an iPhone app and submitted it through App Store Connect. My app has now been approved. I chose the private distribution model (not public). Now I need help making the app available for specific users to download and install. In App Store Connect, under Pricing and Availability > Pricing and distribution methods, I entered my Apple ID and my organization name. From my research, I understand that I need to be registered at business.apple.com. I expected to see my app under Apps and Books in the side menu. However, my account has no side menu, and I can't find the Apps and Books section. Could you please: Give me step-by-step instructions on how to make my approved private app available for installation on specific iPhones? Explain why the side menu, and therefore Apps and Books, is missing in my Apple Business Manager account? Thank you.

Hi everyone, I am posting this out of sheer desperation. I am currently on Day 38 of an unusually long Apple Developer journey, and my app is now completely stuck. My app finally moved to "In Review," but it has been sitting in that exact state for 9 consecutive days with absolutely no updates, rejections, or communication. Here is the full timeline of my 38-day wait: 17 Days: Waiting for my initial account enrollment to clear. 12 Days: My app was stuck on "Waiting for Review" even after an officially approved Expedited Review failed to trigger. 9 Days (Current): The app is now stuck on "In Review". Since a normal "In Review" process typically takes 24 to 48 hours, a 9-day wait in this specific status makes me deeply concerned that my submission might be stuck in the queue or facing an unseen hold. Standard email support (Cases 102974693297 and 102976576467) only sends automated templates asking for patience. Could an Apple Engineer, App Store Connect Specialist, or Moderator please look into my account to see if my submission is stuck? I would deeply appreciate any human intervention to help move this forward. Team ID: 8A9595UHD7 Thank you to anyone who can help. Select a Topic: Chagua App Store Distribution & Marketing Select a Subtopic: Chagua App Review

Hi, I’m currently waiting for my app to be reviewed on the Apple App Store. Could you please tell me the usual review waiting time, and whether there is any way to check the current status or estimated review time for my submission? Thank you.

When I login to an account on a subdomain of a main domain, I want to be able to store a separate password for the same login id on the main domain account. This doesn't seem possible in the current Safari implementation.eg: domain.com is the main domain and is the general information site.my.domain.com is the subdomain that hosts the customer support.I want different passwords on each for the same login ID... Can't I do this?--marcel

After upgrading my M1 MacBook Pro from macOS 26 to macOS 27, my NuPhy Kick75 Bluetooth keyboard started randomly disconnecting during normal use. This issue did not occur on macOS 26 with exactly the same Mac, keyboard, physical location, and usage environment. The problem started immediately after upgrading to macOS 27. The keyboard disconnects approximately 2–3 times per hour. When the interruption occurs, the Bluetooth connection indicator on the keyboard also shows that the Bluetooth link has been lost. This is therefore an actual Bluetooth disconnection rather than only input lag or delayed keyboard events. The keyboard automatically reconnects shortly afterward. macOS bluetoothd logs captured at the exact time of an occurrence confirm that the Bluetooth LE HID link is being disconnected. Hardware Mac: MacBook Pro with Apple M1 Keyboard: NuPhy Kick75 Bluetooth device name: Kick75 IO-2 Connection type: Bluetooth LE HID Regression macOS 26: No Bluetooth disconnections observed during long-term normal use. macOS 27: Random Bluetooth disconnect/reconnect events occur approximately 2–3 times per hour. No keyboard, firmware, physical location, or other hardware/environmental changes were made when the issue started. The behavioral change occurred immediately after upgrading the Mac from macOS 26 to macOS 27. Steps to Reproduce Connect a NuPhy Kick75 keyboard to an M1 MacBook Pro using Bluetooth. Use the keyboard normally for typing. Continue normal use for approximately one hour. At seemingly random intervals, keyboard input suddenly stops. At the same time, the keyboard's Bluetooth connection indicator shows that the Bluetooth link has been lost. macOS automatically reconnects to the keyboard shortly afterward. The same event can be observed in bluetoothd logs as an LE HID link disconnection. Frequency Intermittent but frequent. Approximately 2–3 occurrences per hour after upgrading to macOS 27. Expected Result The Bluetooth LE HID connection should remain stable during normal use, as it did on macOS 26. Actual Result The Bluetooth LE HID connection is unexpectedly terminated. macOS subsequently reconnects to the keyboard automatically. Relevant bluetoothd Log The following was captured during an actual disconnection at: 2026-09-15 17:47:44 Disconnect OI_HCI_LM_HANDLE: 0x55 (85) wakeUp: No RSSI: -37 -37 -37 -37 ... _GATT_LE_DisconnectedCB ... reason STATUS 708 LE Link disconnected ... reason 708 LE ConnManager disconnection complete reason 708 localRole=Central encrypted:1 linkReady:1 disconnectDevice:0 localRole:0 reason:708 result:307 Device disconnected - { devicename: Kick75 IO-2, result: 307 } App disconnected - { bundle: com.apple.BTLEServer, reconnecting: Y } macLeDeviceDisconnected: LE Connection disconnected. Device is a LE HID. BLE Disconnected Unspecified reason 708 Setting LeDevice to Compatible HID from Compatible HID The RSSI values immediately before the disconnection remained consistently around -37 dBm, indicating a very strong Bluetooth signal at the time the link was lost. The following fields appear consistently relevant to this event: reason:708 result:307 disconnectDevice:0 reconnecting:Y macOS also classified the keyboard as a Compatible HID. Related Community Reports This may not be isolated to the Kick75. There is an independent community report involving a NuPhy Air75 V3 on macOS 27 that describes very similar Bluetooth LE HID disconnections. That report has several notable similarities: The Air75 V3 disconnects repeatedly on macOS 27. The same keyboard reportedly operates normally on Windows and iOS 27. Other Bluetooth devices connected to the affected Mac reportedly remain stable. The reporter's macOS Bluetooth logs contain: Incompatible LE HID HID latency issue detected LE Link disconnected (reason 708) Another user reported the same problem with a NuPhy Air65 V3. NuPhy Support responded that they had adjusted Bluetooth parameters and optimized the Bluetooth connection interval, and offered a test firmware for further investigation. The original reporter later tested the same Air75 V3 over Bluetooth on a Mac running macOS 26 at an Apple Store and reported that it did not disconnect. The reporter also observed that having certain Apple Bluetooth HID devices connected at the same time could affect the frequency of the NuPhy disconnections. The community report is titled: “Air75 V3 randomly disconnects on macOS 27 Developer Beta (works perfectly on Windows & iOS 27)” I am including the link to that report with this feedback as supporting information. Importantly, that report involves different NuPhy hardware and a different Mac, but its LE Link disconnected (reason 708) log message closely matches the reason 708 observed independently on my Kick75. This suggests the issue may affect more than one NuPhy Bluetooth LE HID keyboard model under macOS 27. Summary My own reproducible observations are: Same M1 MacBook Pro Same NuPhy Kick75 Same physical environment Stable Bluetooth operation on macOS 26 Frequent disconnections immediately after upgrading to macOS 27 Approximately 2–3 disconnections per hour Keyboard Bluetooth indicator confirms actual link loss bluetoothd confirms an LE HID disconnection RSSI was approximately -37 dBm immediately before the disconnection macOS records reason 708, result 307, and subsequently attempts to reconnect An independent NuPhy Air75 V3 report on macOS 27 also contains LE Link disconnected (reason 708) Taken together, these observations suggest a possible Bluetooth LE HID compatibility regression introduced in macOS 27. I can provide additional Bluetooth diagnostics, a sysdiagnose, and reproduce the issue with Apple's Bluetooth debug logging profile enabled if required.

There's an easily reproducible SwiftUI bug on macOS where an app's UI state no longer updates/re-renders for "Designed for iPad" apps (i.e. ProcessInfo.processInfo.isiOSAppOnMac == true). The bug occurs in Xcode and also if the app is running independent of Xcode. The bug occurs when: the user Hides the app (i.e. it goes into the background) the user puts the Mac to sleep (e.g. Apple menu > Sleep) a total of ~60 seconds transpires (i.e. macOS puts the app into the "suspended state") when the app is brought back into the foreground the UI no longer updates properly The only way I have found to fix this is to manually open a new actual full app window via File > New, in which case the app works fine again in the new window. The following extremely simple code in a default Xcode project illustrates the issue: import SwiftUI @main struct staleApp: App { @State private var isBright = true var body: some Scene { WindowGroup() { ZStack { (isBright ? Color.white : Color.black).ignoresSafeArea() Button("TOGGLE") { isBright.toggle(); print("TAPPED") } } .onAppear { print("\(isBright ? "light" : "dark") view appeared") } } } } For the code above, after Hiding the app and putting the computer to sleep for 60 seconds or more, the button no longer swaps views, although the print statements still appear in the console upon tapping the button. Also, while in this buggy state, i can get the view to update to the current state (i.e. the view triggered by the last tap) by manually dragging the corner of the app window to resize the window. But after resizing, the view again does not update upon button tapping until I resize the window again. so it appears the diff engine is mucked or that the Scene or WindowGroup are no longer correctly running on the main thread I have tried rebuilding the entire view hierarchy by updating .id() on views but this approach does NOT work. I have tried many other options/hacks but have not been able to reset the 'view engine' other than opening a new window manually or by using: @Environment(.openWindow) private var openWindow openWindow could be a viable solution except there's no way to programmatically close the old window for isiOSAppOnMac (@Environment(.dismissWindow) private var dismissWindow doesn't work for iOS)

Heya devs 👋 I am hoping that you might help me with an issue I am having with a Shortcut I have created that's behaving unexpectedly. If you'd like, you can download the Copy Obsidian Link Shortcut to test yourself. Here's a screenshot of the Shortcut: The Shortcut should create an Obsidian Markdown external link when used as a Quick Action from the Finder, e.g., right-clicking on the file Caption - Creative.png in the subfolder PNGs/ and selecting Quick Actions → Create Obsidian Link should send [Caption - Creative.png](file:///Users/user/Documents/Writing-Workspace/PNGs/Caption%20-%20Creative.png) to the paste buffer Instead, [Caption - Creative](file:///Users/user/Library/Group%20Containers/group.com.apple.shortcuts/Temporary/com.apple.WorkflowKit.BackgroundShortcutRunner/Caption%20-%20Creative.txt) is copied. Please help me debug this issue! If you can think of a better place for me to ask this question, I'd be grateful for that even. I've asked on the Obsidian forum and Discord channel already, but haven't got any response.

Hello, I am trying to submit my In-App Purchase subscriptions for review, but App Store Connect is preventing the submission. I have already created: A subscription group ("Piscineiros Pro") Two auto-renewable subscriptions All required metadata and review screenshots When I open the draft submission, I receive the following message: "Unable to Submit for Review. To submit your items for review, add an app version for the selected platform." However, my app version (iOS 4.8.3) already exists in App Store Connect and was previously submitted for review. I would like to understand: Do I need to create a new app version and upload a new binary before I can submit these subscriptions for review? Is it possible to associate the existing subscriptions with the currently rejected app version? What specific steps are required to submit these In-App Purchase products together with my app review? Thank you for your assistance. Best regards, Luiz Maueski

We ship a signed, notarized product archive (.pkg) built with pkgbuild + productbuild and a custom InstallerPlugins pane (ChoosePlugin.bundle). The payload must always install to the system volume (/). There is no supported alternate directory. customize="never" is set because there is a single component package; the user must not pick packages either. What we already do In Distribution.xml: Introduction ChoosePlugin.bundle Target Install PackageSelection is omitted. customize="never" is set. Observed behavior (current macOS) Destination Select (Target) If Target is kept in SectionOrder, the pane still appears in the wizard (often with a read-only / single-volume UI). That step is unused product-wise: the user cannot choose another location. If Target is removed from SectionOrder, Installer.app hangs on the Installation pane at “Preparing for installation…” (pagecontroller / no selected volume). So Target cannot be dropped if we still use the GUI Installer. Installation Type (PackageSelection) The pane does not run (correct). The sidebar still lists “Installation Type” (and often “Summary”) as grayed items. There is no documented way to hide those labels. There is no public InstallerPlugins API to auto-advance the native Destination Select pane (gotoNextPane only applies to our custom section). Question Is there a supported way (Distribution XML, InstallerSections.plist, productbuild, or otherwise) to: Not show Destination Select at all in Installer.app, while still installing to / and not hanging on Installation; and Not list Installation Type (and unused Summary) in the left-hand wizard list, when customize="never" and PackageSelection is omitted? If this is not supported, please confirm that: Destination Select must remain in SectionOrder for GUI installs even with rootVolumeOnly + domains limited to localSystem; and sidebar entries for unused built-in sections cannot be removed. Environment Product archive via productbuild --distribution --plugins macOS 13+ (tested on current macOS / Apple silicon) Custom plugin is universal (arm64 + x86_64) Silent / MDM path (installer -pkg … -target /) is acceptable for automation; this request is GUI Installer.app only.