Overview

Is there a way to extract the Accessibility Tree directly from the browser? Since Chrome provides an API for it, can we use that to generate a dump of the Accessibility Tree?

So through work, we have ChatGPT Enterprise accounts, that authenticate via SSO. I am trying to link it to my Xcode 26.3, and it starts the SSO process (I can see it navigate to Microsoft), but then it apparently fails, and then Xcode window says, I am logged out. I have tried multiple times, and confirmed the valid account... Anyway to get Xcode 26.3 to tie to my ChatGPT Enterprise Account?

Hello, After upgrading to macOS 26.2, I’ve noticed a significant performance regression when calling evaluateJavaScript in an iOS App running on Mac (WKWebView, Swift project). Observed behavior On macOS 26.2, the callback of evaluateJavaScript takes around 3 seconds to return. This happens not only for: evaluateJavaScript("navigator.userAgent") but also for simple or even empty scripts, for example: evaluateJavaScript("") On previous macOS versions, the same calls typically returned in ~200 ms. Additional testing I created a new, empty Objective-C project with a WKWebView and tested the same evaluateJavaScript calls. In the Objective-C project, the callback still returns in ~200 ms, even on macOS 26.2. Question Is this a known issue or regression related to: iOS Apps on Mac, Swift + WKWebView, or behavioral changes in evaluateJavaScript on macOS 26.2? Any information about known issues, internal changes, or recommended workarounds would be greatly appreciated. Thank you. Test Code Swift class ViewController: UIViewController { private var tmpWebView: WKWebView? override func viewDidLoad() { super.viewDidLoad() // Do any additional setup after loading the view. setupUserAgent() } func setupUserAgent() { let t1 = CACurrentMediaTime() tmpWebView = WKWebView(frame: .zero) tmpWebView?.isInspectable = true tmpWebView?.evaluateJavaScript("navigator.userAgent") { [weak self] result, error in let t2 = CACurrentMediaTime() print("[getUserAgent] \(t2 - t1)s") self?.tmpWebView = nil } } } Test Code Objective-C - (void)scene:(UIScene *)scene willConnectToSession:(UISceneSession *)session options:(UISceneConnectionOptions *)connectionOptions { NSTimeInterval startTime = [[NSDate date] timeIntervalSince1970]; WKWebView *webView = [[WKWebView alloc] init]; dispatch_async(dispatch_get_main_queue(), ^{ [webView evaluateJavaScript:@"navigator.userAgent" completionHandler:^(id result, NSError *error) { NSTimeInterval endTime = [[NSDate date] timeIntervalSince1970]; NSLog(@"[getUserAgent]: %.2f s", (endTime - startTime)); }]; }); }

Hey, everyone! I've been trying to publish a new version of my app but it's been stuck in "Waiting for Review" for over 2 weeks now. Previous review processes were really swift (even during the holiday season). Has anyone experienced this issue? I've seen a couple of similar posts here. Any help or guidance will be much appreciated. Best, Wadi

When creating a new App Store version to update ASO keywords and metadata, I notice that elements like the app icon and other details are missing and I am looking for a way to copy the existing metadata from the previous version. Also, is it possible to submit a new App Store version solely for ASO improvements without uploading a new build and still have the changes applied successfully.

I’m building a Swift Playgrounds app (.swiftpm) in Xcode 26.2 and I consistently see this warning, even on brand-new Swift Playgrounds apps created from the default template: “Skipping duplicate build file in Compile Sources build phase: /Users/.../.swiftpm/Media.xcassets” Everything builds and runs normally and all images/assets appear correctly, so it seems like it’s just an annoying warning. I’ve checked for duplicates and don’t see the asset catalog listed twice, but the warning still appears whenever I add an asset catalog to any playground project in Xcode. Is this warning safe to ignore for submission, and it won’t affect Swift Student Challenge eligibility?

Hello, My new app (App ID: 6757254070) has remained in the “Waiting for Review” status since February 1 (UTC+9). Because the review process seemed to be taking unusually long compared to my previous experiences, I submitted an inquiry (Reference ID: 102812788306), but I have not yet received any response. For additional context, the app was originally submitted on January 23 and remained in the “Waiting for Review” state for eight days. As I was concerned there might have been an issue with the review queue, I canceled the submission and resubmitted the app on February 1. At this point, I am wondering whether the prolonged waiting time is simply due to a heavy backlog in the App Review process. Thank you very much for taking the time to read this. I hope you have a great day.

I'm trying to enable Music Kit for my key however I keep seeing this message "There are no identifiers available that can be associated with the key" even though my identifier has music kit enabled. Can someone help out with this?

I am building my app for iPhone users generally, and realized that maybe I should have had the iPad in mind since I read somewhere that the submissions will be judged on iPad. Should I be testing and tweaking on iPad now or can it be somehow ran on iPhone?

Hi everyone - My first iOS app submission has been in "Waiting for Review" since Jan 27 (we actually submitted Jan 23, saw no movement, and resubmitted with a small update), and Apple Support has not responded to my outreach. Since Jan 27, our team has implemented a handful of app updates from our roadmap and plans to submit the updated version of the app once the first submission is approved. However, we're at a crossroads: Do we wait for the first submission (currently 14 days and counting) and submit the updated version once (hopefully) approved, rolling the dice that an update to an existing app would see a faster 2-3 day turnaround? Cancel our current version and resubmit the updated one, with the risk that we're just moving ourselves to the back of the queue and get stuck in another 15-20 day "Waiting for Review" status? Any devs with insight or experience navigating these choices, any suggestions would be greatly appreciated.

I'm trying to test the update process for an app containing an FSKit module that I'm distributing on the Mac App Store. (I'm also distributing the same app directly with Developer ID, but here I'll focus on App Store because that's the behavior I've been looking at first.) To do that I'm using an internal tester group on TestFlight and then testing an update with TestFlight. Below is the behavior I'm seeing on macOS 15.7.2 (24G325). I've noticed that if an app update is triggered while a disk is mounted using the FSKit extension, the disk is automatically unmounted without warning (FB21287341). That's already undesirable itself in my opinion, but on top of the unmount, there are two other problems: That unmount doesn't seem to be a "clean" unmount and doesn't call functions like synchronize (FB21287688). Now, in my case, my app only provides read-only access, so that doesn't actually matter much in my case. However, I'd imagine if I were to add write access at some point in the future, this would go from "doesn't matter" to "very bad." I've seen a few cases where quitting or crashing the FSModule process while a volume is mounted without actually doing a clean unmount causes a lot of "disk-related actions" (for lack of a better term) to freeze (FB21305906). For example, a use of the mount(8) command or trying to mount a disk at all freezes, and opening Disk Utility stalls on a "Loading disks" spinning indicator. This happens until the Mac is rebooted. I did notice this issue once while testing updates via TestFlight a few times. The same applies if I simply delete the app with Finder instead of updating it. Is there a way to prevent the extension's process from terminating in this case and/or another workaround I could use without waiting for a macOS update to hopefully change this behavior? And does observing this kind of behavior with TestFlight's update behavior suggest the same thing could happen on the App Store with its automatic updates? I'm concerned that pushing an update via the App Store will unexpectedly unmount disks or cause the system-wide issues described in FB21305906 at a random time, which is a pretty big disruption for users.

After upgrading to a new iPhone and restoring from an iCloud backup using the same Apple ID, I noticed an issue with Health app permissions. ■ What is happening On my previous iPhone, an app had permission to read step count data. After restoring to the new iPhone, the app still appears in the Health app under Sources. However, when I tap the app, the usual data type permission toggles (such as Steps) are not displayed at all. As a result, the app is unable to read step count data. ■ Additional details The app itself seems to be recognized as a Health data source. However, the data type permission screen is empty. No ON/OFF switches are shown. The backup was created on iOS 18, and the restore was performed on iOS 26. I have not yet confirmed whether this also happens with other iOS version combinations. ■ Questions Is it expected behavior that Health app permissions (per data type) are not restored via iCloud backup? Has anyone experienced a similar situation where the app appears under Sources but the permission options are missing? If so, how did you resolve it? Any information from users who have experienced the same issue would be greatly appreciated.

This is a copy of a reply to this post. https://developer.apple.com/forums/thread/722222?page=1 I'm posting as new in the hope someone might have more up-to-date information, as I'm pulling out what little hair I have left. I'm using Storekit 2, testing in Xcode with a local Storekit config file. I have created a very minimal system to investigate this issue. I have a SwiftUI-based window using SubscriptionStoreView, and my app set up with the usual listener. I have four types of auto renewing subscription, configured in the local Storekit config file. With my app running, I subscribe to the lowest-level subscription I offer, via the SubscriptionStoreView. Notification of the inital purchase arrives, but subsequent auto-renewals do not trigger any action in my listener for Transaction.updates. They arrive as expected in the Transaction Manager. Radio silence in my listener. If I upgrade one subscription (via my SubscriptionStoreView) I see this reflected in the UI immediately, and also in the Transaction Manager, but the update that arrives in Transaction.updates refers to the old subscription, and has the isUpgraded flag set to false. Also, can anyone remind me what the grey warning triangle next to entries in the Transaction Manager means. I'm assuming it means unfinished, as that's what the sidebar indicates. Can the testing system really be this broken, or am I wildly off the mark? Unless I'm doing something fundamentally wrong this all seems extremely flakey, but happy to be proved wrong. I find this all rather unsettling if I can't test reliably, and am concerned that I my app may end up in this situation if I use storekit 2: https://stackoverflow.com/questions/73530849/storekit-renewal-transactions-missing-in-transaction-all-or-transaction-updates

I have got 26.3 running, signed in with calude max account and open ai plus account, but codex and claude agent "get " button is greyed out. I have apple intelligence turned on.. I can only use sonnet 4.5 inside xcode. anyone has an idea about whhy>?

Hello Using a MacBook Pro Intel with macOS 12.7.6 Monterey, I test in Objective-C an event for the option key but it is not working - (void)keyDown:(NSEvent *)event { printf("%s %p\n", __FUNCTION__, self); BOOL altFlag = [event modifierFlags] & NSEventModifierFlagOption; if (altFlag) { // UpdateClass printf("option pressed\n"); } else { printf("option not pressed\n"); } } The same in Swift works fine override func keyDown(with event: NSEvent) { if event.modifierFlags.contains(.option) { print("option pressed") } else { print("option NOT pressed") } } The Obj-C code works fine on a MacBook Air Tahoe 26.3 Any idea why it does not work on the macOS 12.7.6 Intel? Many Thanks Jean

Hello, We are currently using Apple Notarization (notarytool) for distributing a macOS app, and we are experiencing very long notarization times for large app bundles. [Issue] For apps with large binary sizes, notarization consistently takes around 3.5 to 4.5 hours from submission to completion. This delay is causing practical issues in our release pipeline, especially when: A hotfix or urgent update is required Multiple builds must be notarized in a short time CI/CD-based distribution is expected to complete within a predictable timeframe [Environment] Platform: macOS Notarization method: notarytool Distribution: Outside Mac App Store App size: 100 GB~ (compressed ZIP) Signing: Hardened Runtime enabled, codesigned correctly Submission status: Successfully accepted, but processing time is very long [What we have confirmed] The notarization eventually succeeds (no failures) Re-submitting the same build shows similar processing times Network upload itself completes normally; the delay is in Apple-side processing Smaller apps complete notarization much faster [Questions] Is a 3–4+ hour notarization time expected behavior for large macOS apps? Are there recommended best practices to reduce notarization processing time for large binaries? For example, splitting components, adjusting packaging, or specific signing strategies Is there any official guidance or limitation regarding notarization queueing or processing based on app size? Are there known service-side delays or regional differences that could affect processing time? Any insight or confirmation would be greatly appreciated, as this directly impacts our production release workflow. Thank you.

Hi all, I’m seeing a lifecycle behavior change on iOS 26.0 (and up). While my app is in the foreground and active, pressing the hardware Lock button triggers didBecomeActive callbacks/notifications even though the app is transitioning away from active state. I’m observing this sequence: willResignActive didBecomeActive willResignActive didEnterBackground This happens for: • UISceneDelegate.sceneDidBecomeActive(:) • UIApplicationDelegate.applicationDidBecomeActive(:) • UIApplication.didBecomeActiveNotification On iOS 18 (same app, same code) I do not see didBecomeActive in the middle of locking/backgrounding. Problem is reproduced on totally new project. I would expect a normal transition to background: • willResignActive → didEnterBackground …and no extra didBecomeActive between them. I have “became active” logic (refresh UI/state, resume timers, analytics). On iOS 26.0 this logic runs unexpectedly during locking, causing unnecessary work and incorrect state transitions. Is this callback ordering expected on iOS 26.0 when pressing the Lock button? If expected, what’s the recommended way to detect a “real” activation (and avoid transient didBecomeActive during locking/backgrounding)? If this is a regression, is there a known workaround or best practice?

Hello, I’m writing this here because I’m honestly stuck and unable to reach anyone through official support channels. Order Number: W1466057949 Order Date: 18/02/2026 Case ID: 102824542025 My payment was successfully approved and processed by my bank. The amount has been fully charged. However, my Apple Developer account has still not been activated. I opened a support ticket immediately after noticing the issue. It has now been 6 days, and I have received absolutely no response. There is no active support in Turkey for this issue. When I try calling the Ireland support number, I can only reach an automated system — there is no way to speak to a real person. I currently have no direct contact channel to resolve this. This situation is blocking my development work and causing serious delays. I have completed my payment in good faith, yet I cannot access the service I paid for, and I cannot reach anyone for assistance. If anyone has experienced a similar issue or knows how to escalate this properly, I would greatly appreciate guidance. Thank you.

Hello team, I am trying to find out a way to block urls in the chrome browser if it is found in local blocked list cache. I found URL Filter Network very much suitable for my requirement. But I see at multiple places that this solution is only for Enterprise level or MDM or supervised device. So can I run this for normal user ? as my targeting audience would be bank users. One more thing how can I test this in development environment if we need supervised devices and do we need special entitlement ? When trying to run sample project in the simulator then getting below error

Hello, I would like to formally raise a concern regarding an ongoing lack of communication in the review process. Two of my applications have been in the “Waiting for Review” stage for an unusually extended period. During this time, I have: • Sent multiple support emails • Submitted an expedited review request • Attempted to follow up through official channels Despite these efforts, I have not received a single response or status update. I understand that review timelines can fluctuate depending on workload and complexity. However, prolonged silence without acknowledgment creates uncertainty and directly impacts release planning, user acquisition strategy, and overall operational decisions. This is not a complaint about review duration alone. It is primarily about the absence of communication. Even a brief confirmation or estimated timeline would significantly improve the situation. I respectfully request clarification on the status of these submissions and the reason for the continued “Waiting for Review” state. I sincerely hope this matter can be resolved promptly. Thank you for your time. Best regards, Berkay