Hi. On my iOS app, both the app store and the device are making changes to my app icon to make it look more Liquid-Glass. See attached image showing my original icon, and then how it appears on the app store and on devices. There is an added bevel/3d effect. I'd like to not have this happen. Did anybody figure out how to turn this off? So that the icon appears as submitted. I've played around with Icon Composer a bit but haven't managed to turn this off there. And would prefer to just submit the png's. Thank you!

Hello, I made my app icon with Icon Composer and added the .icon file directly to my Xcode project. I noticed that the icon preview in Icon Composer looks one way, while the icon shown on the App Store looks different. Details: I am using the .icon file directly in the project I am not using an exported PNG for the app icon I did not add a separate background image The background was set with fill in Icon Composer The preview in Icon Composer looks as expected The App Store version has a different appearance I would like to ask whether this difference may come from: App Store processing caching or a recommended Icon Composer setup for background fill If anyone has seen something similar, I would appreciate any guidance. I can also share screenshots of the Icon Composer preview and the App Store result.

Hey everyone, We’re testing a React Native iOS app in the Simulator. There is a quirk with our email and phone links. The inline links render correctly and visually register taps, but they are unresponsive. The same behavior occurs with an "Email Us" button. These links work on a physical device. To confirm, we used Terminal to see what was happening: xcrun simctl openurl booted mailto:info@example.com xcrun simctl openurl booted tel:+15555555555 Both of these commands throw an error: NSOSStatusErrorDomain code=-10814 So does the Simulator lack a registered handler (like the native Mail or Phone apps) for mailto: and tel: schemes, or is there a touch-handling bug in our UI? Our Environment & Setup React Native: 0.80.2 Simulator Device: iPhone 17 Simulator Runtime: iOS 26.0 Implementation: React Native's Linking.canOpenURL() and Linking.openURL(). Config: For 3rd-party fallbacks, we added googlegmail and ms-outlook to our LSApplicationQueriesSchemes in our Info.plist. My Questions Is this -10814 error the expected behavior for mailto: and tel: schemes across iOS Simulators? Are there workarounds or testing strategies for these links, or do I always need to validate on physical hardware? Thanks in advance for any insights!

Hi all! I am struggling to make any app because reality composer pro freezes when I click on create new project, as well as it does not appear in Xcode at all. I have tried deleting and redownloading all versions of both Reality Composer Pro & Xcode, as well as restarting my computer. Kindly advise what else I can try. Thank you!

Can someone please tell me if it possible to create and publish an ios app onto the app store from a windows device? If it possible then how do i do it?

Hello, Running unit tests fires up the simulator, which is so slow. Is it feasible, for an iOS project, to move all logic into an external package (no UI imports)? That feels like a sledgehammer just to make tests run a bit quicker. And all the extra potential mistakes of running one app across two projects. Are there other/better approaches to test logic only in an Xcode iOS project? Buy a bigger laptop? :) Thanks

Hoping someone from Apple or anyone who has hit this can help. While setting up my first app I made a mistake: the App Store Connect app record was created with the wrong identifier a Services ID I use for Sign in with Apple (com.mycompany.myapp.signin) instead of my real app bundle ID (com.mycompany.myapp). A second app record was bound to the correct bundle ID. It had no builds, no in-app purchases, and was never published, so I deleted it, expecting the bundle ID to be released. Current state: The correct bundle ID does not appear in the Bundle ID dropdown, either in my existing app's App Information page or when creating a new app. Deleting the App ID in the developer portal fails with: "The App ID appears to be in use by the App Store, so it can not be removed at this time." It has been like this for several days; all my builds are signed with the correct bundle ID, and my subscriptions live on the surviving app record, so I cannot upload builds or run sandbox purchases until the record is on the right identifier. I raised a support case with Apple Developer Support 3 days ago (Case ID: [20000129712022]) and haven't had a response yet. Questions: Is there any self-service way to release a bundle ID held by a deleted, never-published app record? Alternatively, can support change the bundle ID on my existing (never-published) app record? Typical turnaround for this kind of case?

The RSS feed at https://developer.apple.com/news/rss/news.rss appears to be inaccessible as of a couple of weeks ago. Has it gone for good and is there an alternative way to subscribe to updates?

Hello, I use Mermaid diagrams for conception and documentation. I would like to do this in close coupling with Xcode, e.g. diagram previews "directly" in Xcode. Does anyone have a tip for me?

I sent it for testing from the Choicely app. I have entered the downloaded key, opened it in Notepad, and pasted the long key; my team and distributor are right. But it seems like Apple always mentions build 1.0.2 (7) when I am actually sending (8). It'll say failed, then suddenly say ready to submit for review. So I will, and I'm waiting for review... then I get a red failed sometime later saying either certificates are not included ( I don't get all that... I'm using Windows, so I can't make them like they say I need to, and sometimes it says invalid binary...although if I look at app info and details... it says binary validated. It will make it to just before TestFlight sometimes, and sometimes it passes TestFlight... also it will say app synced successfully but failed to collect metadata. So many oddities... I don't know what to do!!

I am developing a large iOS application with an extensive UI test suite (hundreds of UI test scenarios). After upgrading our CI runners to macOS Tahoe 26, we started observing an intermittent issue where an iOS Simulator may operate normally for many successful application launches before unexpectedly entering a persistent degraded state. Once this occurs, every subsequent application launch crashes inside dyld before reaching our application’s main(). The degraded state persists until the simulator device is reset This causes UI tests to hang and eventually timeout. Business impact CI/CD jobs frequently timeout (90+ minutes per failed run) Significant loss of CI capacity Difficult to maintain reliable quality gates At our scale, this has become a serious issue affecting release confidence and overall engineering productivity. Technical details Crash report MyProject-2026-07-13-125307.ips — a crash report from a CI Demo project dyld_crash_demo — a minimal reproducible project demonstrating the relevant dyld execution path. The project intentionally returns errors from system functions along the shared cache initialization path to demonstrate that dyld continues execution until DyldSharedCache::getUUID(), where it subsequently crashes. Simply open the project and run it in iOS Simulator 26.2. Environment Component Version macOS Tahoe 26.x Xcode 26.2, 26.5 iOS Simulator 26.2, 26.5, 26.6 Architecture Apple Silicon dyld 1378 dyld_sim 1335 What we have ruled out multiple Xcode versions multiple macOS 26.x releases multiple iOS Simulator runtimes multiple simulator devices UI tests with parallel execution disabled deleting the simulator dyld shared cache recreating simulator devices application-specific issues (the crash happens before main()) The issue is still reproducible. Investigation The earliest observable failure sequence is consistently: shared_region_check_np() → "Cannot allocate memory" (ENOMEM) Shared cache mmap(0x180000000, ...) → EACCES The shared cache region remains unmapped DyldSharedCache::getUUID() reads 0x180000058 EXC_BAD_ACCESS (Translation fault) The crash occurs before any application code executes. The first faulting instruction belongs to DyldSharedCache::getUUID(), while the shared-cache region is still unmapped. Published dyld source analysis Relevant execution path: loadDyldCache() ↓ mapSplitCachePrivate() ↓ preflightCacheFile() Based on the published sources of dyld-1378, this appears to be the execution path leading to the observed failure. After the loadDyldCache() function failed to load the cache, dyld continued execution anyway and moved on to calling the DyldSharedCache::getUUID() function, where it subsequently failed. Additional observations Once the simulator enters the degraded state: simctl spawn succeeds. simctl launch crashes inside dyld before reaching main(). During our experiments, both processes were created by the same launchd_sim instance Before dyld::_dyld_start, both processes expose the same virtual address layout, including an unmapped shared-cache region (0x180000000–0x300000000). Current workaround As a temporary mitigation, we launch the application with DYLD_SHARED_REGION=avoid In our environment, this completely avoids the launch failures. However, this mode appears to be undocumented and intended primarily for debugging. We are concerned that it may change or stop working in future macOS or Xcode releases, so we are reluctant to depend on it in our production CI infrastructure. Questions 1. dyld Is it expected for dyld to continue dereferencing the shared-cache header after both the shared-region initialization and the shared-cache mapping have already failed? Execution appears to continue into: loadInfo.loadAddress->getUUID(cacheUuid) which results in an access to an unmapped address. The attached demo project reproduces this behavior by simulating failures from the shared-cache initialization path. Is there an expected fallback behavior for this situation or is continuing into DyldSharedCache::getUUID() the intended behavior ? 2. Simulator state Why does a simulator that initially launches applications successfully eventually enter a state where every subsequent launch fails while the shared cache can no longer be mapper? The earliest related system log we have found is: vm_shared_region_start_address() returned 0x1 Is this a known CoreSimulator or macOS Tahoe issue? If so, is there a supported workaround or recommended long-term solution besides DYLD_SHARED_REGION=avoid? Any guidance would be greatly appreciated.

I have tested my app on many iOS versions e.g. 26.5.0 27.0 beta and many more for all iPhone and iOS devices on simulator. I wanted to ask, it's difficult to have so many real devices. So what should we do for that?

We're hitting a submission deadlock with a Capacitor-based iOS app that I suspect will affect any app using Capacitor/Cordova (or similar frameworks distributed as prebuilt binaries) once Xcode 27 ships. Setup: App built with the current Xcode, targeting the current SDK. Embeds Capacitor.framework and Cordova.framework (via ionic-team/capacitor-swift-pm). The loop: Using Ionic's latest official release: these prebuilt frameworks are still built against an older Xcode/iOS SDK. App Store Connect rejects the upload with ITMS-90111 (stale SDK), even though the app's own target and every other embedded framework are current. To fix that, we rebuilt Capacitor.framework/Cordova.framework from Capacitor's open-source iOS source (MIT-licensed, same version as the official release) using the current Xcode — confirmed via archive that every framework now reports the current SDK. That upload is then rejected with ITMS-91065 (missing signature) — the rebuilt frameworks lack an Apple SDK signature that (as far as we can tell) only Ionic's own build pipeline can produce. So: official release → current-SDK check fails. Self-rebuilt release → signature check fails. We verified this isn't a fluke with an isolated throwaway-archive test swapping only the framework source. Questions for anyone who's solved this: Is ITMS-91065's "Apple SDK signature" requirement satisfiable by re-signing a self-built .framework with our own Distribution certificate during export, or does it specifically require Apple's own build-time signature that third parties can't reproduce? Has anyone shipped a Capacitor/Cordova app successfully against a new major Xcode/SDK before Ionic cut a matching signed release? If so, how? Also filed with Ionic: ionic-team/capacitor#8537 (https://github.com/ionic-team/capacitor/issues/8537) — no response yet as of 2026-07-23.

I distribute my AppleScript applet in a read only DMG file. I want to add a simple background image which encourages users to copy the applet to their Applications folder. I use the Finder function "Show View Options" which has the option to add a picture. That seems to work in macOS Tahoe. However, the background image is not visible on earlier versions of macOS. I've also found that a background image set on a Mac running Monterey is not visible on a Mac running Tahoe. Is there a way to add a background image which works across multiple macOS versions ?

Hi folks, This webpage: https://developer.apple.com/download/os/#ios-restore-images-ipad-new lists the iPhone 7 Plus as being among the devices that are compatible with iOS 16.7.16. Currently the maximum iOS for the 7 Plus is 15.8.8 according to Settings. The page also indicates that iOS 15.8.8 should be installable on the iPhone 6. Are these typos? The utility idevicerestore refuses to install 16.7.16 on an iPhone 7 Plus so I assume so, but it would help to get confirmation.

It is gone from where I used to find it on Apple’s web site. Is it deprecated or no longer available?

I know that using a mouse to control an iPhone simulator on macOS allows me to swipe down from the top right corner to open the Control Center, but why can't I swipe down from the top left corner to open the Notification Center? Am I doing something wrong, or does iOS disable mouse access to the Notification Center on macOS? Also, it seems that you can't use a mouse or gestures to open the Notification Center or Control Center in iPhone Mirroring at all. I saw that Accessibility has a feature to open the Notification Center or Control Center with the keyboard, but it doesn't work in my tests on macOS. I have an application feature that needs to check the effect of the media playback cards in the Notification Center, but I can't check it at all. Every time I compile to a real device and test manually. Is there any way to reliably trigger the Notification Center and Control Center on macOS? Otherwise, testing on a real device every time is too cumbersome, and I can't automate the testing at all!

Hello, I would like to suggest adding dedicated keyboard shortcuts or menu commands for opening Notification Center and Control Center in both iOS Simulator and iPhone Mirroring. At the moment, these interfaces generally need to be opened by dragging downward from a specific area at the top of the simulated or mirrored iPhone screen. While this works for normal manual interaction, it is less reliable when using a mouse, especially when the window is resized or when the pointer needs to begin very close to the screen edge. This also creates difficulties for automated UI testing and computer-use agents, such as Codex-based testing workflows. These systems interact with the screen through mouse and keyboard input, so accurately reproducing an edge swipe can be unreliable. A small difference in the starting position may open Spotlight, scroll the current application, move the window, or fail to trigger the system interface entirely. It would be helpful if Apple could provide commands such as: Open Notification Center Open Control Center Dismiss Notification Center or Control Center These commands could be exposed through: Keyboard shortcuts The Simulator “Device” or “Features” menu The iPhone Mirroring toolbar or menu bar Accessibility or UI automation interfaces For example, Simulator already provides menu commands and shortcuts for actions such as pressing the Home button, locking the device, rotating the screen, and triggering other hardware-related interactions. Notification Center and Control Center could be handled in a similar way. This would improve: Manual testing with a mouse and keyboard Automated testing of applications that interact with notifications, media controls, Bluetooth, Focus modes, screen recording, and other system features Accessibility for users who have difficulty performing precise drag gestures Reliability for computer-use and vision-based testing agents Ideally, the commands should behave like genuine system gestures rather than directly changing internal state, so developers can test the complete user-visible interaction. Thank you for considering this feature.

Good morning. I have been developing an app for my company using flutter for a couple of months. A few months ago I deployed it through TestFlight, as it's supposed to be used by our staff exclusively. It has been working flawlessly since may, but today it has stopped working suddenly without me doing any kind of update or change to the code. The issue is that it's unable to send any kind of http request to our server, which it could do until literally yesterday. The error messages are both Connection Timed Out and Bad File Descriptor. As I have not updated the app in several days and it has suddenly stopped working without me changing anything, I suppose it could be a problem with a change of permissions or conditions that I have not agreed to. What could have happened? I use flutter 3.44.1 on windows and deploy using codemagic. Thank you for your cooperation.

Hello! Double checking I'm not missing something before I submit a feature request -- possible for self-intersecting paths to render as layered instead of merged? For example, a spiral path with the tail overlapping the tip will currently "flatten" into a circle instead of rendering a translucent overlap.