Overview

When trying to use the MIDI Maestro app by Singular Sound, BLE peripherals experience unwanted connection-parameter renegotiation and disconnections on iOS 26, beta iOS 26.2 does not fix this issue. iOS 26 BLE communications are being sent too fast to be read correctly by the hardware device, and iOS 26.2 refuses communication altogether.

I've been working on UI Tests for a month or two and things have been great. But I believe there was a recent update to Xcode [running Version 26.2 (17C52)] and since then about 80% of the time when I try to view the test results so I can see the screenshots and video, Xcode crashes hard and I have to open it again. I've tried cleaning the Build folder and Derived Data and all sorts of stuff like that. Restarted Xcode, restarted my computer, etc. Any idea of how I can avoid these crashes?

Hello, We're developing endpoint security software using the Endpoint Security framework, and we've encountered challenges with the behavior change in macOS 15 regarding provisioning UDIDs in cloned VMs. The Change Prior to macOS 15, cloning a VM preserved its UDID (format: 0000FE00-9C4ED9F68BBDC72D). Starting with macOS 15, cloned VMs receive a new UDID generated from the host's Secure Enclave (format: b043d27202c7ac37ca3c6b82673302225485cae9), making each clone effectively a new device. Our Workflow We maintain a clean base VM image and clone it for each test run. We add the base VM's UDID to our provisioning profile once, then create clones which (previously) retained that same UDID, allowing us to start new testing cycles without re-registering devices. This is essential because our product involves low-level system integration through the Endpoint Security framework, and if something goes wrong during development, it has the potential to affect system stability. To prevent any cascading issues between test runs or different product versions, we need each test to start from a known clean state rather than reusing the same VM. The Challenge With each VM clone generating a new UDID, we're hitting Apple's device registration limits quickly. This particularly impacts: New team members who spin up VMs for the first time and can't run signed builds Our CI/CD pipeline where multiple test environments need provisioning profiles Developers testing different branches who need separate clean environments Current Workaround We've found that VMs created on macOS 14 and upgraded to macOS 15+ retain their original UDID format. However, we're concerned this workaround may stop working in future macOS versions, which would leave us without a viable path forward. If the workaround stops working, our fallback would be signing each CI build with a Developer ID signature to allow running on any device. However, we'd prefer to avoid this as it would significantly increase load on Apple's signing infrastructure for what are essentially internal test builds. We completely understand the security reasoning behind tying UDIDs to the host's Secure Enclave for Apple Account support. However, for development workflows that don't require Apple Account features in VMs but do require clean, isolated test environments, the previous behavior was quite valuable. Question Is there a recommended approach for teams in our situation? We're happy to explore alternative workflows if there's a pattern we're missing, or we'd be glad to provide more context if this is a use case Apple is considering for future updates. Thanks for any guidance you can provide! Feedback case: FB21389730

I am developing an app which included subscriptions and in app purchases. Created a Test Flight archive a day ago. Got Apple email with their approval, shortly after. I know there is a problem and the Test Flight release is not available in Connect app, or App Store Connect on Mac. I am useing Xcode 26, iOS 26 and an iPhone 17 Pro.

One of the biggest ongoing frustrations with Apple’s App Review process is inconsistency across builds of the same app version. We regularly encounter the following situation: A build of a new version is reviewed and approved. Shortly after, we submit another build of the same version, often containing only a minor bug fix. This second build is suddenly rejected for an issue that was never mentioned in the previously approved build. After explaining the situation and resubmitting, the build is usually approved. While this may seem manageable on paper, in practice it causes unnecessary delays, especially for time-critical patches and hotfixes that need to reach users quickly. The core issue is predictability: If a guideline violation exists, it should be identified consistently across all builds of that version. If functionality is effectively unchanged, review outcomes should not vary based on reviewer interpretation. Developers should not have to lose hours—or days—explaining why a nearly identical build suddenly fails review. Apple’s review process is essential for platform quality, but lack of continuity between reviews creates avoidable friction for teams shipping live products. Consistent enforcement of guidelines across builds would significantly improve trust, efficiency, and developer experience—without lowering App Store standards. This is not about bypassing rules. It’s about clarity, consistency, and respecting the urgency of real-world software development.

Hi, I'm trying to set the displayScale environment value for a RealityView, so it renders at 2x instead of 3x on the iPhone, but it seems to have no effect. .environment(\.displayScale, 2.0) Is this expected behavior, or a bug? The reason I want it to render at 2x and not at the default 3x is for game optimization and performance.

I was looking through: https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/ScriptableCocoaApplications/SApps_handle_AEs/SAppsHandleAEs.html And wondered how these are handled for SwiftUI apps. What would I add or override?

Hey, I am looking to participate in the upcoming SSC 2026. I am confused whether I am allowed to submit an idea which is for watchOS. I know the fact that submission would be xcode project and playground correct me if I am wrong but as far as I know, we can develop prototypes for watch on playground. If anyone of you knows about this, please let me know!

I’m trying to test IAP in Sandbox, but I can't find any product IDs. It seems my Paid Apps Agreement is still "Pending User Info" even though Bank, Tax, and Compliance forms are all marked as "Active." It’s been over 10 hours. Does anyone know what "Pending User Info" might refer to if everything looks complete? I noticed I left the "Nickname" field blank in the Tax Form—could that be the reason? If so, how can I edit it since the forms are already submitted?

Our apps, such as iCMTGIS PRO, provides the ability for users to open a job file received as an email attachment. Our apps use application:openurl:option to get the URL for the job file (*.pmp). We use [URL path] to convert it to NSString format. Then we use fopen to read the .pmp job file in "read only" mode. On iPad Air (5th generation) running iOS Version 18.6.2, our apps are able to read the .pmp job file. However, on iPhone 11 running iOS: 26.2, using fopen to read the .pmp file, we get a NULL value and are not able to correctly read the .pmp file.

I have a Apple Developer accounts for development purposes only and that is also used for testing builds via TestFlight. Is the Age Ratings Responses updates due by the end of January 2026 still required even to send builds to TestFlight?

I'm in the process of supporting Apple Pay through a 2nd payment gateway for some users, so I need to support two separate Apple Pay relationships. Both require their own apple-developer-merchantid-domain-association. I don't see how I can have both files for the one domain. Is this possible? Is there a workaround other than just replacing the old file with the new one and hoping that doesn't disrupt anything. That seems to be the approach taken by others (https://developer.apple.com/forums/thread/695538) but it is too high risk for me without any confirmation from Apple that this is ok. I'd also like to avoid having to setup a 2nd domain for these customers, since the current domain is already quite embedded in their operations.

Hello, I purchased the Apple Developer Program a week ago and yet I haven't received any information on it. No activation of the account whatsoever. I've sent 3 emails to apple support, but still no replied. Is this normal? How long does it take? Will someone finally assist me Apple?

Here we are facing issue, which is mentioned in detail below: Safari on iOS consistently crashes when loading https://johnsoncontrols.com/. The error shown is: “A Problem repeatedly occurred on https://johnsoncontrols.com/” This happens with multiple iPhone models and iOS versions, suggesting a WebKit rendering or JavaScript execution issue. This occurs occasionally similar behavior on Android, iPhone (Chrome) Environment • Devices: Any iPhone model, we are tested on available models like iPhone 12 mini, iPhone 14, iPhone 15 • iOS Versions: Latest stable releases, occasional occurrence on iOS 13 • Browser: Safari (WebKit) • Network: Both Wi-Fi and cellular tested • Additional Occurrences: Rarely reproduced on Chrome (iPhone, Narzo Android) • Occurs only on physical devices (not observed in Simulator) Steps to Reproduce Open Safari on any affected iOS device. Navigate to https://johnsoncontrols.com/. Sroll page up and down for some time Observe page automatically get reloads, crashed and show error message (A problem repeatedly occurred on “https://johnsoncontrols.com/"). Expected Result Page should be rendered normally without crashing. Actual Result Safari reloads page / blank / crashed and displays errors. Troubleshooting Done • Cleared cache and cookies • Disabled content blockers • Tested in Private mode • Reset Experimental Features • Issue persists across different networks Technical Notes • Suspect JavaScript memory leak or DOM manipulation causing WebKit crash. • Intelligent Tracking Prevention (ITP) or site scripts may conflict. Questions for Community • Can Apple confirm whether this aligns with any known WebKit bugs? • Are there recommended diagnostic steps (e.g., Web Inspector, crash logs, sysdiagnose specifics) for reproducing Safari scroll-related site crashes? • Should the site’s development team adjust JavaScript, rendering approach, or resource handling to improve stability on WebKit?

Here we are facing issue, which is mentioned below: On https://johnsoncontrols.com/, tapping the blue “Scroll to Top” button (up arrow icon) causes the entire page to reload instead of smoothly scrolling back to the top. This issue occurs only on physical iOS devices and is reproducible across multiple models and iOS versions. Similar behavior is rarely/occasionally seen in Chrome on iPhone and some Android devices. Environment • Devices: Any iPhone model, we are tested on available models like iPhone 12 mini, iPhone 14, iPhone 15 • iOS Versions: Latest stable releases • Browser: Safari (WebKit) • Network: Both Wi-Fi and cellular tested • Additional Occurrences: Rarely reproduced on Chrome (iPhone, Narzo Android) • Occurs only on physical devices (not observed in Simulator) Steps to Reproduce Open Safari on a physical iPhone. Navigate to https://johnsoncontrols.com/. Scroll down until the blue “Scroll to Top” button appears on the right side. Then tap on ‘Scroll to top’ button. The page reloads instead of scrolling to the top. Expected Result Tapping the Scroll to Top button should smoothly move the user to the top of the page without reloading. Actual Result Safari reloads the entire page when the button is tapped. Troubleshooting Done • Replaced # with javascript:void(0) in the button’s anchor tag • Tested with e.stopPropagation() • Switched button position from fixed to sticky • Tried overflow-y: scroll; and -webkit-overflow-scrolling: touch; on body • Updated scrollTop logic to match iOS‑compatible standards. Questions for Community • Is this a known WebKit issue on physical iOS devices? • Any recommended debugging or profiling steps to better understand the cause? • Are there best practices or example implementations to improve Safari compatibility for scroll to top interactions?

Why is the application not completed? Your enrollment in the Apple Developer Program could not be completed at this time.

hello everybody, I have a new idea for the future a new product the new iPod with integrated mobile router and with more functions also other products in this category more functions you can thinking for gaming and more one function is special for handheld controller. One is Nintendo Switch or other consoles. She have problem with the Wi-Fi. When you most login we are website. This problem is with this problem. Not more a problem. This is the idea one from thousand ideas the best is the software you can use this for working and for the children for the first smartphone you cannot calling all person you can only call the 911 or the family interest you making with FaceTime this is the number one for communication on this iPod. This is a new category and you can music streaming.

Hi everyone, I’m seeing recurring internal AVFoundation camera logs on iOS 26.2 and I’m trying to understand whether this is expected behavior or a regression in the capture pipeline. These logs appear shortly after starting an AVCaptureSession, while video frames are being delivered, and also when the camera is stopped or the capture session is torn down. <<<< FigXPCUtilities >>>> signalled err=-17281 at <>:302 <<<< FigCaptureSourceRemote >>>> Fig assert: "err == 0 " at bail (FigCaptureSourceRemote.m:569) - (err=-17281) Even in this clean, minimal setup, the same logs appear on iOS 26.2 The exact same logic did not produce these logs on iOS 18.x. To rule out issues caused by my own code, GPT created a minimal SwiftUI example from scratch. My primary interest is to perform real-time processing on the video frames delivered by the camera (via AVCaptureVideoDataOutput), for tasks such as analysis, computer vision, or custom frame handling, while simultaneously displaying the live preview. Thanks in advance for any insight. Example Code

Hi everyone, I’ve completely removed my App Clip: Deleted all Advanced App Clip Experiences Removed the App Clip target from my build Removed App Clip references from my apple-app-site-association file Deleted the meta tag from my website: However: When scanning the QR code, the App Clip card still appears with: "This App Clip is not currently available in your country or region." This link still works for my App Clip, which is not what I expected: https://appclip.apple.com/id?p=com.example.appclip Does anyone know why the App Clip card is still showing and how to fully remove it? Thanks!

Hi everyone, I’ve removed my App Clip completely: Deleted all Advanced App Clip Experiences Removed the App Clip target from my build Removed App Clip references from my apple-app-site-association file Deleted the meta tag from my website: But when I scan the QR code, the App Clip card still appears with: "This App Clip is not currently available in your country or region." Does anyone know why this is still showing and how to fully remove it? we need to show our website when this QRCode is scanned. Thanks!