Overview

In WKWebView, there is the WKUIDelegate method: func webView(_ webView: WKWebView, createWebViewWith configuration: WKWebViewConfiguration, for navigationAction: WKNavigationAction, windowFeatures: WKWindowFeatures) -> WKWebView? {} This delegate method provides a callback when a new window (for example, target="_blank") is requested in the web view. However, in native SwiftUI (iOS 26), WebView / WebPage APIs do not provide an equivalent delegate method to handle new window requests. As a workaround, I am using the following method: public func decidePolicy(for action: WebPage.NavigationAction, preferences: inout WebPage.NavigationPreferences) async -> WKNavigationActionPolicy {} In this method, when action.target == nil, I treat it as a new window request. My question: Is relying on action.target == nil in decidePolicy a reliable and future-safe way to detect new window requests in SwiftUI’s WebView, or is there a better or more recommended approach for handling target="_blank" / new window navigation in the SwiftUI WebView APIs? Code: public func decidePolicy(for action: WebPage.NavigationAction, preferences: inout WebPage.NavigationPreferences) async -> WKNavigationActionPolicy { guard let webPage = webPage else { return .cancel } // Handle case where target frame is nil (e.g., target="_blank" or window.open) // This indicates a new window request if action.target == nil { print("Target frame is nil - new window requested") // WORKAROUND: Until iOS 26 WebPage UI protocol is available, we handle new windows here // Try to create a new WebPage through UI plugins if handleCreateWebPage(for: webPage, navigationAction: action) != nil { // Note: The new WebPage has been created and published to the view return .allow } } return .allow }

Since last year, our company has been signing in new users to Apple Store Connect using our private email domain. However, since last week, when we try to sign in with this same domain, we receive the following error: "Your primary email address cannot end in @mydomain.com.br. Choose a different email address."

When Live Caller ID first came out I experimented with it and got it working using the Example PIR database. All my links from that time are now out of date and no longer work, however I seem to have found where the PIR database example and documentation has moved to (https://swiftpackageindex.com/apple/pir-service-example/main/documentation/pirservice/testinginstructionslivecalleridlookup) But what I can't find is an exact definition of the the logo size/max size/dimensions/format should be. My memory from that time is that it was very pernickety, and if things weren't exactly right, the logo wasn't displayed. I can remember the format had to be HEIC to get it to work. Looking through the documentation however, I can't see exact requirements specified. My question is - for the Live Caller ID logo what are the exact image requirements, and where are they documented?

Been trying to get into Developer Prgram since December 2025. And like many others, it seems the biggest tech company on the planet cannot streamline an enrollment program. Unless, it’s by design, to test your nerve? Anyways, I have now ended up paying twice, and still not even a squeak from support. There is no Developer Support phone number in South Africa, and mails go unanswered. How is this possible? $200 out of pocket, and nothing to show. Cannot even find a method for refunds. If there are steps to still follow or docs to submit, why take my money, then ask for more info?? But this black hole of SILENCE…. Now that skype is no longer, what other platform will allow me to call the US Support number from South Africa?

Hi, Once I try to reset security question, it says: "Your request could not be completed. This action could not be completed due to an error. Please try again later." So I am unable to access account. Please help! Best Regards,

Hi, We're seeing a recurring issue in Sandbox only with in-app subscriptions (StoreKit 2). Hoping someone has run into this and has a workaround or explanation. What happens A subscription purchase (e.g. Yearly) is made in Sandbox. For whatever reason, the transaction stays pending in the queue. On the next app launch (or when a different user logs into the app on the same device), the store returns this same pending transaction via getAvailablePurchases() / the purchase queue. Our app sends that transaction to our backend for validation and updates the currently logged-in user in our database. So the same transaction can end up being applied to another user if they log in on the same device after the original purchaser. We call finishTransaction after successful validation, but the pending transaction still reappears in subsequent sessions or for another user on the same device. So in short: one Sandbox purchase stays "pending" and is replayed every time we start the app or switch accounts, and we can't rely on it being tied to a single user. Environment Sandbox only (we haven't shipped to production yet). StoreKit 2 / modern App Store Server API (transaction ID validation). We run getAvailablePurchases() on connect and process pending purchases once per session; we then call finishTransaction only after our server has validated and updated the user. Same device, multiple app accounts (different app users, same Sandbox Apple ID or same device). What we're trying to understand Is it expected in Sandbox that one transaction can be delivered again and again (on each launch or for each user on the device) until something clears it? Is there a recommended way to clear or ignore a specific pending transaction in Sandbox when we've already validated it for a given user (e.g. idempotency key, or a way to "consume" it so it doesn't replay)? Has anyone else hit this "same pending transaction replaying for different users / on every launch" in Sandbox and found a reliable approach (e.g. server-side idempotency, or a StoreKit/Sandbox step we're missing)? We've added server-side protection (one transaction → one user) so the same purchase isn't credited to multiple accounts, but we'd like to understand if there's a proper way to handle or clear this pending state in Sandbox. Thanks in advance.

Hi, It is the second time I am trying to create a Developer account and having the same issue. First time, my account was "pending" for weeks until the payment were refunded to my account. I called to Apple Store, which told me the issue could be with the bank processing. I called the bank, which said the issue could be with Apple processing. Now again, trying it, and Pending... Anyone had this issue and could give me some help please ?

Hello everyone, this is the situation with the iPhone 15 pro, forgot the password code needs to be reset to factory settings, tell me if it is possible to get the media content later that was on the device and there was no backup

Use iTMSTransporter to upload the ipa file on Windows. ERROR: Client configuration failed [2026-02-05 16:35:17 CST] INFO: iTMSTransporter Correlation Key: a97add20-898c-4d66-81c8-a1e313f2807e-0001 [2026-02-05 16:35:17 CST] DEBUG: DataCenter: contentdelivery01.itunes.apple.com [2026-02-05 16:35:18 CST] DBG-X: Apple's web service operation return value: [2026-02-05 16:35:18 CST] DBG-X: parameter DSToken = hidden value [2026-02-05 16:35:18 CST] DBG-X: parameter DSTokenCookieName = myacinfo [2026-02-05 16:35:18 CST] ERROR: Client configuration failed Here is the error message. Package Summary: 1 package(s) were not uploaded because they had problems: C:\Users\Administrator\Desktop\bag\gsl222.ipa - Error Messages: Client configuration failed [2026-02-05 16:35:18 CST] DBG-X: Returning 1

I have a framework, which depends on a library (GPGME) to do its actual encryption. As a consequence of using this external library, there are header files which have GPGME types in them... @interface E3Gpgme : NSObject ... /*****************************************************************************\ |* Call GPGME to sign \*****************************************************************************/ - (int) signWithMode:(gpgme_sig_mode_t)mode userId:(NSString *)signingKeyOrEmail srcStream:(E3Stream *)src dstStream:(E3Stream *)dst error:(NSError **)error; ... @end . This means the E3Gpgme class header file has to #import <gpgme.h> to get those type definitions. That is then proving problematic because the framework modularisation fails, with <e3gpgme.h> obviously not being a part of the framework, so the project refuses to build. I can see a few ways around this: Just don't run the modularisation check. That doesn't sound like a fantastic option import the GPGME headers (there's only 2) into the project and bundle them as if they were project ones. Again, not a great option, I don't expect GPGME to change its API but it runs the risk of there being a mismatch in future if the library code itself remains external. So what's the best-practice for requiring a dependency on a library, not a framework ? Is there a way to copy the library binary into a folder inside the framework folder and make sure you link with that ? Assuming that's the shared library it ought to still be ok for the LGPL licensing... Is there a better way ? I'm sure I'm not the first person to run into this :)

Environment: Device: MacBook Pro (Mac16,7) Chip: M4 Pro (SoC ID 6040, Revision 11) OS: macOS 15.2 (24C101) Kernel: Darwin Kernel Version 24.2.0; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041 Summary: I am developing a Windows emulator on the MacBook Pro M4 Pro platform. During testing with certain applications, the system frequently triggers an instantaneous reboot. This issue appears to be highly specific to the M4 Pro hardware and current OS version. Observation & Diagnostic Challenges: Upon reboot, the system generates a bug_type 210 (SoC Watchdog Reset) report. The panic string indicates: "Unexpected SoC (system) watchdog reset occurred after panic diagnostics were completed". The primary difficulty in debugging is that the hardware reset happens so rapidly that the kernel fails to capture a stackshot or any detailed panic trace. We have practically no actionable information from the standard diagnostic reports. However, we did find the following recurring entries in the system log prior to the resets: Ignored NI0 NI0 niGeneral 1 NO_ACCESS error (0x00000010) cmd/st:0x14(ncrdincr)... srcchildid/srcparentid:0x8ea/0x1d Comparison & Testing: We have performed extensive cross-version and cross-device testing to isolate the cause: M1/M2 Series: Identical tests on M1 and M2 devices running macOS 15 do not trigger this issue. The applications run stably. OS Versions: Interestingly, this issue seems significantly harder to reproduce on newer system builds (e.g., version 26 series), suggesting it might be a regression or a specific incompatibility in the current macOS 15.2 environment for M4 Pro. Request for Assistance: Since we cannot collect stack traces through conventional means, we are seeking your expertise: Known Issues: Has Apple received similar reports from other developers working on low-level emulation or virtualization on M4 Pro? Is this a known issue in macOS 15.2 / build 24C101? Debugging Guidance: Given that the system reboots without leaving a stackshot, what are the recommended methods to capture more granular data? Are there specific boot-args or instrumentation tools that can help log the state of the SoC fabric (NI0) before the watchdog kicks in? Architectural Insights: Based on the NI0 NO_ACCESS error and srcchildid: 0x8ea, could you suggest which subsystem or memory operation we should investigate further?

Hi everyone, I subscribed to the Apple Developer Program on Tuesday evening, Jan 30th, 2025. The payment has already been successfully charged to my bank account, but my account is still showing “Pending” with the message “Subscribe your membership.” It has been several days now, and I haven’t received any confirmation email or any request for additional verification. I’ve already contacted Apple Developer Support via email, but I wanted to check here as well. Has anyone else faced this issue recently? How long did it take for your membership to become active? Any insights or experiences would be greatly appreciated. Thanks in advance!

Hello, I am an individual developer working on a macOS application using SwiftUI and RealityKit. I would like to understand the feasibility of face-related tracking on macOS when using an external USB camera, compared to iOS/iPadOS. Specifically: • Does macOS provide an ARKit Face Tracking–equivalent API (e.g., real-time facial expressions, gaze direction, depth)? • If not, is it common to rely on Vision / AVFoundation as alternatives for: • Facial expression coefficients • Gaze estimation • Depth approximation • In an environment without dedicated sensors such as TrueDepth, is it correct to assume that accurate depth data and high-fidelity blend shape extraction are realistically difficult? Any clarification on official limitations, recommended alternatives, or relevant documentation would be greatly appreciated. Thank you.

Hey guys! I downloaded Apple’s Icon Composer to build my iOS 26 app icon. I exported my SVG from Illustrator (and verified it through Canva and the W3C validator). However, when I import it into Icon Composer, it looks really weird . There are these bubble-like artifacts appearing in the center. Here's my orignal svg icon file trace-logo.txt Any help will be appreciated! Best, Justin

Missing recommended icon. The bundle does not contain an alternate app icon for iPhone / iPod Touch of exactly '120x120' pixels, in .png format for iOS versions >= 10.0. To support older versions of iOS, the icon may be required in the bundle outside of an asset catalog. Make sure the Info.plist file includes appropriate entries referencing the file. See https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleicons (90890) Missing Icon. The Info.plist key CFBundleIcons.CFBundleAlternateIcons contains an entry “newIcon” that references asset “newIcon.” No such asset is present in the asset catalog. (90895) I configured multiple icon settings in Xcode 26 version. I added new Icons in the asset file. However, after packaging and uploading the app to the AppStore, it kept giving me an error message saying that some content was missing. Looking at the documentation, it doesn't seem to say that starting from Xcode 13, we can configure through the asset file?

On iPhone 16 Pro Max (not tested other devices) there's a noticeable jump in the framing of the preview video when you record in the iOS AVCam Sample App. The same jump in camera framing can be observed by switching to the front facing camera and then back to the rear one. It looks roughly consistent with switching between the 0.5x and 1x camera (but not quite a match for the same viewable area in the Camera app) - and it's only when it's initially loaded, once recording is started it retains the 'closer' image no matter how many times it's stopped/started thereafter. I'm relatively new to Swift and haven't done anything with the camera before, so odd 'buggy' behaviour in the sample code isn't helping me understand it! :-) Is there any way to fix this?

I’m having an issue verifying a domain for a Merchant ID. I’m implementing Apple Pay on the web for a demo, and I’ve configured the Azure server to match Apple’s requirements for domain verification, such as the TLS configuration, not requiring client certificates, and ensuring there are no redirects. I’ve run tests with OpenSSL and PowerShell and all responses return HTTP/1.1 200 OK. I also tested the URL Apple says it uses to validate the file under .well-known, and it does show the expected result. I already have the Apple Pay Payment Processing Certificate and the Apple Pay Merchant Identity Certificate approved; the only thing missing is the domain verification. I’m not sure what else to test—if you could help me with a possible solution, I’d really appreciate it. (The project is built in .NET 8 and hosted on Azure App Service.)

Problem Description Location-based notifications added with UNLocationNotificationTrigger and CLCircularRegion do not fire consistently when the user enters the monitored region. Sometimes they work, sometimes they do not. In tests where the user physically enters the region and waits several days, the notification often never triggers. What we’ve confirmed Notification permission is granted Location permission is set to “Always” The notification request is successfully added (no error from UNUserNotificationCenter.add) Pending notification requests are present when checked with getPendingNotificationRequests CLLocationManager didEnterRegion / didExitRegion work when we monitor the same region via startMonitoring(for:) UNLocationNotificationTrigger behavior is inconsistent and unreliable in our tests Reproduction Steps Launch the app and grant notification permission and “Always” location permission Add a region notification (either by current GPS location or by selecting a point from MKLocalSearch) Leave the monitored region Later, physically return into the region Expected: a notification is delivered when entering the region Actual: the notification often does not appear, even after waiting days Our Hypothesis: Coordinate System Mismatch in China We suspect the issue may be related to coordinate systems in mainland China. In China, Apple MapKit and MKLocalSearch use GCJ-02 (the “Mars” coordinate system required by local regulations). Device GPS and CLCircularRegion / Core Location use WGS-84. If an app supplies GCJ-02 coordinates to CLCircularRegion (e.g. from MapKit or search), the region center may be offset by hundreds of meters from the actual WGS-84 position. That could make the system’s “inside region” check fail, even when the user is physically inside the intended area. Questions for Apple Does CLCircularRegion (and therefore UNLocationNotificationTrigger) expect coordinates in WGS-84? If so, should apps in China convert GCJ-02 to WGS-84 before passing coordinates to CLCircularRegion? Is there any official guidance or documentation for handling coordinate systems when using location-based notifications in mainland China? Are there known limitations or special requirements for UNLocationNotificationTrigger in China (e.g. coordinate system, accuracy, or system behavior) that could explain intermittent or missing triggers?

Hello, We are implementing Apple Wallet extensions (PKIssuerProvisioningExtensionHandler). While our UI extension works as expected, our Non-UI extension is unable to detect payment passes provisioned by our app. Specifically, PKPassLibrary().passes(of: .secureElement) returns an empty array when called from the Non-UI extension, even though the same call correctly returns the passes when executed from the Main iOS App. Our Payment Network Operator has confirmed that our extension bundle identifiers are correctly registered in the metadata on their side. They suggested that the Wallet Extensions entitlement (com.apple.developer.payment-pass-provisioning) may require additional backend enablement for these specific Extension App IDs. Is there a known reason why PKPassLibrary would behave differently in the Non-UI extension vs the Main App? Beyond the standard entitlement request, is there a specific process to "activate" these IDs for extension visibility? Does anyone have guidance on reaching the appropriate team for backend entitlement activation issues? Any insights would be greatly appreciated.

You can't transfer this app because of the following reasons: App Transfers Disabled for This Account Due to irregular activity associated with your account, you cannot transfer or receive apps at this time. If you think this is an error, contact Developer Support.