Overview

Post

Replies

Boosts

Views

Activity

My IP address has been blocked by the forums?
I've hit a dead end with normal Apple support channels. I wrote up a radar for it (FB23333685). I used curl -v https://developer.apple.com/forums/ on my Mac via my phone's hotspot (working) and via Spectrum (not working) (some irrelevant stuff elided to shrink post): Working: % curl -v https://developer.apple.com/forums/ * Host developer.apple.com:443 was resolved. * IPv6: 2620:149:a06:f000::134, 2620:149:a06:f000::139 * IPv4: 17.253.31.140, 17.253.31.139 * Trying [2620:149:a06:f000::134]:443... * Connected to developer.apple.com (2620:149:a06:f000::134) port 443 <elided> > GET /forums/ HTTP/1.1 > Host: developer.apple.com > User-Agent: curl/8.7.1 > Accept: */* > * Request completely sent off < HTTP/1.1 200 OK < Server: Apple < Date: Mon, 22 Jun 2026 23:22:30 GMT < Content-Type: text/html;charset=utf-8 < Vary: Accept-Encoding < Set-Cookie: oid-dev-forums=; Path=/; Domain=.apple.com; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Max-Age=0; Secure; HttpOnly < Expires: Mon, 22 Jun 2026 23:22:29 GMT < X-Frame-Options: DENY < Strict-Transport-Security: max-age=31536000; includeSubDomains < Service-Worker-Allowed: / < User-Type: anonymous < Cache-Control: private,no-cache,no-store, must-revalidate, max-age=0 < Last-Modified: Mon, 22 Jun 2026 23:22:29 GMT < X-Content-Type-Options: nosniff < Content-Security-Policy: <elided> < Vary: Accept-Encoding < X-XSS-Protection: 1; mode=block < Vary: Origin < Vary: Access-Control-Request-Method < Vary: Access-Control-Request-Headers < Content-Language: en-US < X-Request-ID: 41b2b91a2a2c5e8be35787ec7b349db8 < Edge-Control: !no-store,max-age=3600 < X-Request-ID: 41b2b91a2a2c5e8be35787ec7b349db8 < Set-Cookie: myacinfo=; Path=/; Domain=.apple.com; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Max-Age=0; Secure; HttpOnly < Set-Cookie: asc_user=; Path=/; Domain=.apple.com; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Max-Age=0; Secure < Set-Cookie: XID=<redacted>; Path=/; Domain=.apple.com; Expires=Wed, 22 Jul 2026 23:22:29 GMT; Max-Age=2592000; Secure; HttpOnly < Set-Cookie: df_shld_btm_prd=<redacted>; Expires=Tue, 23 Jun 2026 11:22:30 GMT; Max-Age=43200; Domain=apple.com; Path=/; SameSite=Lax; Secure < Age: 2 < Via: https/1.1 ussea4-edge-mx-005.ts.apple.com (acdn/302.16436), https/1.1 ussea4-edge-fx-007.ts.apple.com (acdn/302.16436) < X-Cache: miss, miss < CDNUUID: 42f00814-9cfb-4675-a0fa-4f3aa5ba89da-2134634100 < Transfer-Encoding: chunked < Connection: keep-alive < <!DOCTYPE html> … Failing: % curl -v https://developer.apple.com/forums/ * Host developer.apple.com:443 was resolved. * IPv6: (none) * IPv4: 17.253.83.137, 17.253.83.132 * Trying 17.253.83.137:443... * Connected to developer.apple.com (17.253.83.137) port 443 <redacted> * SSL certificate verify ok. * using HTTP/1.x > GET /forums/ HTTP/1.1 > Host: developer.apple.com > User-Agent: curl/8.7.1 > Accept: */* > * Request completely sent off < HTTP/1.1 403 Forbidden < Server: Apple < Date: Mon, 22 Jun 2026 23:16:25 GMT < Content-Type: text/html < Content-Length: 146 < Cache-Control: private, no-cache, no-store, max-age=0 < Age: 0 < Via: https/1.1 uslax1-edge-mx-005.ts.apple.com (acdn/302.16436), https/1.1 uslax1-edge-fx-015.ts.apple.com (acdn/302.16436) < X-Cache: miss, miss < CDNUUID: 4da2a4a9-3bd4-4135-b895-6b58b6d7f53b-1614544808 < Connection: keep-alive < <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> <hr><center>Apple</center> </body> </html> * Connection #0 to host developer.apple.com left intact The Spectrum response never reached the forums app at all — it was rejected at the edge node itself (uslax1-edge-mx-005 / uslax1-edge-fx-015, both LA-area). The working request happened to land on a Seattle-area edge (ussea4) via anycast routing. So this isn't an app-level or account-level block — it's a deny rule sitting on (or upstream of) the LA edge PoP for my specific IP. Thing is, I don’t know how to get help on this issue.
Topic: Developer Tools & Services SubTopic: Developer Forums
5
0
293
3d
Xcode 27 incorrectly links a Catalyst binary, _UIFontTextStyleCallout Expected in AppKit
I have a personal iOS project that I also compile for macOS with Catalyst. When built with Xcode 26.x, everything is linked correctly. When built with Xcode 27 betas, the following runtime error occurs: Termination Reason: Namespace DYLD, Code 4, Symbol missing Symbol not found: _UIFontTextStyleCallout Referenced from: <046ED276-F81A-31B4-82FF-6DC82E9041BC> /Applications/Photo Library.app/Contents/MacOS/Photo Library Expected in: <298B64F6-9BC0-3BFB-BE72-EBDC2BE0FF19> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit Any assistance? Thanks
Topic: Developer Tools & Services SubTopic: Xcode Tags:
2
0
96
3d
Betas not available to all developers?
It's been over 2 weeks and I still don't have the option to download the Mac or iOS 27 betas. All I see is the option for the current public betas for Tahoe and iOS 26. I am a registered developer and thought I would get access to the betas. I've submitted 2 tickets through the feedback assistant and both were closed with the comment "investigation complete - working as designed". I don't know where else to go. Is it true that not every developer gets access to beta software or that developer betas are released in phases? I've never read that anywhere nor heard that once released that beta software isn't available to all developers in the Apple dev program (not the public beta program). Can anyone shed light on this? is this true? Are betas released in phases to developers? At this rate as a developer I will have to wait until the public beta. Help!
Topic: Developer Tools & Services SubTopic: Apple Developer Program Tags:
6
0
165
3d
SB 2420 - I have no idea what to do.
I recognize that Apple has put out documentation on how to do things with the new Age APIs, but I have no idea what my apps are supposed to do to be in compliance with this law. Most of the law sounds like it applies to App Store developers like Apple, more than it pertains to individual app devs. If the age rating of an app changes, wouldn't we just put it in App Store Connect and have Apple disable those apps on the devices of the underage kids?
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
2
0
133
3d
How to get Ask Siri context menu button
In my UIKit apps, collection view cells that have a context menu gain an Ask Siri item in iOS 27 without me doing anything. In my SwiftUI app I have a LazyVGrid containing a ForEach of CellView which is a Button that has a contextMenu, yet there’s no Ask Siri button in the context menu. What determines whether or not it will be added? What do I need to do to allow the system to add it?
Topic: UI Frameworks SubTopic: SwiftUI Tags:
2
0
100
3d
How to clean Xcode build files？
When I tried to use Xcode to compile an app for my iPhone, it also compiled a macOS version, but they don't work. I tried to delete them from the Applications folder, but they're not there. According to the Xcode logs, I found that they're located in /private/var/folders/ and there are some deprecated projects. How should I delete them?
Topic: Community SubTopic: Apple Developers Tags:
3
0
158
3d
Xcode won't sign into ChatGPT Codex account anymore
As of May 8th, 2026, after I upgraded to "codex-cli 0.129.0" via Xcode, I can no longer sign into my ChatGPT account in Xcode Intelligence Settings. The Log In window is always successful, but the settings never update to show the login being successful. It's a constant loop. Perhaps a hand-shake fail. Versions: Tahoe 26.3.1, Xcode 26.4.1, codex-cli 0.129.0.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
8
2
1.2k
3d
Age assurance in Texas
Hello Apple Developer Support Team, We understand from the Declared Age Range documentation that, in some regulated regions, the system automatically provides the person’s age range and they can’t decline sharing it with the app. We have implemented the API as prescribed in the documentation. For certain users in Texas, the API returns: isEligibleForAgeFeatures == true declaredAgeRangeRequired == true However, in our testing we observe that these Texas users can still decline sharing their age range, either via the system prompt or later via Settings, which results in no age range being provided to the app. This behavior appears inconsistent with the documentation’s statement that, in regulated regions, the person “can’t decline” sharing their age range, and it also raises questions for us about how this aligns with the applicable legal requirements in Texas. Could you please clarify: Whether this behavior (Texas users being able to decline sharing their age range even when declaredAgeRangeRequired is true) is expected, and Under what exact conditions the “they can’t decline sharing” behavior is enforced for Texas accounts (for example, only for new Apple Accounts created in Texas after a certain date, or only for particular age categories)? Any guidance on how we should interpret isEligibleForAgeFeatures and declaredAgeRangeRequired in this scenario would be greatly appreciated. Thank you.
Topic: App & System Services SubTopic: General Tags:
0
0
89
3d
Clarification on the planned removal of UIDesignRequiresCompatibility
Dear Apple Developer Support, I am developing and maintaining an iOS application. In iOS 26, we understand that setting UIDesignRequiresCompatibility to true in the Info.plist file allows an app to opt out of the Liquid Glass design. However, we also understand that during WWDC25 Platforms State of the Union, Apple stated: "We intend this option to be removed in the next major release." We would appreciate clarification on the following points. Questions Should the phrase "next major release" be interpreted as iOS 27? Is it currently Apple's plan to make UIDesignRequiresCompatibility unavailable or remove it in iOS 27? Or is the statement above only an intended direction, with the actual removal schedule still subject to change? If there is any publicly shareable information regarding the future availability or deprecation timeline of UIDesignRequiresCompatibility, could you please provide it? Background We develop and maintain a business application that contains a large number of custom screens and UI components. Adapting the entire application to the Liquid Glass design system will require significant design review, implementation effort, and testing. As a result, the future availability of UIDesignRequiresCompatibility is a critical factor in our development planning and resource allocation. For this reason, we would greatly appreciate any guidance you can provide regarding Apple's current plans for this compatibility option. Thank you for your time and assistance. Best regards, Toshiyuki
Topic: UI Frameworks SubTopic: General Tags:
9
0
446
3d
Camera features
Hello Everyone, I am a student from India who is passionate about technology, coding, and design. I would like to propose a precise hardware and software design enhancement regarding the "LED Flash for Alerts" feature on the iPhone. Current Limitation: The existing feature utilizes the main camera flash/torch. While functional, it is incredibly bright and harsh, causing visual discomfort in dark rooms, study spaces, or classrooms. My Specific Idea: Instead of using the blinding main flash, Apple could integrate a subtle, soft white LED indicator directly inside or underneath the small black circle element located on the camera module (the sensor/microphone area). When a notification or call arrives, this exact black circle should softly pulse or glow with a clean, ambient white light. Benefits: Precision & Aesthetics: It utilizes an existing design element to create a beautiful, minimalist, and non-disruptive visual alert. User Experience: It provides a soft indicator that doesn't blind the user or disturb others in low-light environments. Power Efficiency: Illuminating a tiny dedicated ring/circle consumes significantly less battery than firing the main camera torch. As a student, I believe this subtle refinement would make the iPhone experience feel even more premium and thought-out. I would love to hear what Apple engineers and the developer community think about this!
Topic: Design SubTopic: General
1
0
97
3d
ApplePay create-session API timing out
We are an Apple Pay consumer and observed elevated response times and intermittent timeouts affecting the create‑session API (apple-pay-gateway.apple.com/paymentservices/paymentSession) between approximately 8:01 PM and 8:35 PM PST today. We are reaching out to understand whether there were any service disruptions during this timeframe, as we do not see corresponding updates on the system status pages. We would like to confirm whether this behavior was related to a broader Apple Pay issue or specific to our integration.
Topic: App & System Services SubTopic: Apple Pay
1
0
390
3d
Is UISceneAppIntent supported in Designed for iPad apps on macOS?
I'm seeing what appears to be different UISceneAppIntent behavior between iOS and Designed for iPad on macOS, and I'd like to confirm whether this is expected. I'm working on an iOS app that defines an AppIntent conforming to UISceneAppIntent from the AppIntents framework. The intent is handled by a scene delegate conforming to both UIWindowSceneDelegate and AppIntentSceneDelegate. On iOS, everything works as expected: If the app is launched for the first time from Shortcuts, the intent is available via connectionOptions.appIntent in scene(_:willConnectTo:options:). If the app is already running, scene(_:willPerformAppIntent:) is called. However, when running the same iOS app on macOS in Designed for iPad mode, the behavior is different: If the app is launched from Shortcuts, connectionOptions.appIntent is always nil in scene(_:willConnectTo:options:). If the app is already running, scene(_:willPerformAppIntent:) is never called, even though the application is successfully activated. Is this expected behavior? I noticed that the AppIntents framework explicitly marks both AppIntentSceneDelegate and UISceneAppIntent as unavailable on macOS: @available(iOS 26.0, tvOS 26.0, *) @available(macOS, unavailable) @available(watchOS, unavailable) public protocol AppIntentSceneDelegate : UISceneDelegate Since the app is running on macOS in Designed for iPad mode and still uses the iOS binary, I wasn't sure whether these scene-based APIs are expected to work in this environment or whether they are intentionally unsupported. Has anyone from Apple or the community been able to confirm whether this behavior is by design, or whether it should be considered a bug? I'd appreciate any clarification.
Topic: Machine Learning & AI SubTopic: App Intents Tags:
1
0
103
3d
NSFileProviderReplicatedExtension: uploading after completion handler
Hello, I'm implementing an NSFileProviderReplicatedExtension (iOS 26 and macOS 26) and would like to validate my approach. What I do To make my uploads efficient I batch them: instead of uploading file-by-file inside each createItem / modifyItem, I ingest all local changes into my extension's local state quickly and upload the content blobs in the background in batches. Concretely, for both createItem and modifyItem: I persist the item to my local store, write its content blob to a local cache, and schedule the upload in my internal queue. I call the completionHandler right away before uploading the item, returning the NSFileProviderItem with isUploaded = false. Once the upload succeeds, I flip the item to isUploaded = true and call signalEnumerator(for: .workingSet) so the change is delivered through the working-set enumerateChanges. This works in my testing, but I'm unsure it is the intended approach, and I have the following questions. Question 1 — Honoring the Progress object I call the completion handler early (step 2) and run the upload afterwards. The convenient part for my batched uploads is that I don't seem to need to honor the returned Progress at all — I never report into it and I just drop it, yet in my testing the upload still completes. I'd like to confirm two things: (a) Can I ignore the Progress? I'd like to never report into the returned Progress and simply drop it: I coalesce uploads into batches drained from a persisted queue, so I can't map one Progress to one upload, and retaining thousands of them is itself a cost. Is that allowed? What makes me unsure is that the docs read a little asymmetrically — for createItem the progress is "presented in the user interface until the completion handler is called", whereas for modifyItem it is "expected to include the upload progress … even if the provider chose to call the completion handler before the upload finishes". (b) If I ignore it, am I still granted execution time to finish the upload? This is what worries me, because the "Execution time" clause couples the two: the system "will grant enough time … to upload the file" but "will interrupt the call if it stops making progress." If I report no progress, does the system stop granting runtime? Question 2 — Upload pipeline depth When calling the completion handler before finishing the upload, both createItem and modifyItem are no longer gated by the NSExtensionFileProviderUploadPipelineDepth limit, and I can have thousands of items pending upload. This is crucial for my approach. Is this behaviour correct and intended?
Topic: App & System Services SubTopic: Core OS Tags:
1
0
103
3d
Effect of iBeacon broadcast interval adjusting from 100ms to 50ms on iOS activation effect and system compatibility
Our current business goal is to improve the success rate of iBeacon wake-up on iOS. Apple's official iBeacon specification recommends a standard broadcast interval of 100ms; Now we are planning to shorten the broadcast frequency to 50ms, and we would like to consult the full dimensional impact of this change, and whether it can really improve the success rate of beacon identification and pull trigger on iOS devices.
Topic: App & System Services SubTopic: Maps & Location
1
0
88
3d
IAP products not loading in sandbox after activating Paid Apps Agreement
I activated the Paid Apps Agreement today along with banking and tax information. My app uses react-native-purchases (RevenueCat) with StoreKit 2. When tapping purchase buttons in TestFlight I still get "Product not available - Could not load this product." Products show "Waiting for Review" in App Store Connect. Sandbox tester is configured. Is there a delay after activating the Paid Apps Agreement before sandbox purchases work? How long should I expect to wait?
Topic: App & System Services SubTopic: StoreKit
0
0
59
3d
ESP32 USB-C to iPhone 16 USB-C communication
Hi everyone, I am seeking clarification regarding the communication capabilities between an ESP32 microcontroller and Apple's latest devices, specifically the iPhone 16 Pro Max and iPad Pro, both equipped with USB-C ports. Background: MFi Certification: Historically, establishing communication between external devices and iOS devices required MFi (Made for iPhone/iPad) certification. But I remember this being necessary in the Lightning Cable to USB era. With the introduction of USB-C ports in recent iPhone and iPad models, there is an indication that MFi certification may no longer be necessary for certain peripherals. Perhaps I'm not confident on the terminology here: https://mfi.apple.com/en/who-should-join Project Requirements: I am working on a sensor research project that necessitates the collection of low-latency time-series data from an ESP32 microcontroller, which features a USB-C port. The data needs to be transmitted to an iPhone 16 Pro Max or iPad Pro. Bluetooth communication has proven insufficient due to its limited data transfer rates (~1.2 Mbps with L2CAP). While NEHotspot could be an alternative, it restricts the iPad's internet connectivity. Therefore, establishing a direct USB-C connection between the ESP32 and the iOS device appears to be the most viable solution. Questions: MFi Certification Necessity: Is MFi certification still required for an ESP32 microcontroller to communicate with iPhone 16 Pro Max or iPad Pro via USB-C? USB-C Communication Support: Do the iPhone 16 Pro Max and iPad Pro natively support serial communication over USB-C with microcontrollers like the ESP32? If not, are there recommended protocols or interfaces to facilitate this communication? App Development Considerations: Would developing a custom iOS application be necessary to handle data transmission from the ESP32 over USB-C? If so, are there specific APIs or frameworks provided by Apple to support this functionality? Data Transfer Rates: Considering the need for high-speed data transfer, are there any limitations or considerations regarding the data transfer rates achievable through a USB-C connection between the ESP32 and iOS devices? Thank you!
Topic: App & System Services SubTopic: Hardware Tags:
6
1
2.3k
3d
Unable to receive 2FA SMS - TestFlight blocked, 250+ users waiting
Case ID: 102924093872 Case ID: 102924089648 Hi Apple Support Team, I’m reaching out regarding a critical issue that is blocking my app testing and affecting hundreds of users. I cannot receive the two-factor authentication code for my Apple Developer account. My mobile operator has confirmed that SMS messages from Apple are not reaching their network at all. I also receive no calls. Since my account is not logged in on any device, SMS is the only way I can verify my identity - and it’s not working. I have already submitted two support cases but have not received any response yet. Here is the impact this is having right now: • 250+ people are waiting to get access to test my app • 400 users are already using the app • I cannot sign the new agreement that appeared in App Store Connect • Because of this, TestFlight is completely blocked - both the 10,000 user limit and the 100 user internal testing • Even when I add someone to my team and grant them access, it still doesn’t work for them either I have been building this app for almost 7 months. We are in the final testing stage before I plan to release it for sale. Every day without access is a day my users are waiting and I cannot move forward. I am asking you to please help me resolve this as quickly as possible. I really need your support right now. Thank you so much for your time. Best regards, Tata
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
1
0
58
3d
Message Filter Extension: undocumented per-sender ILMessageFilterAction categorization state on iOS 26.5 — by design or bug?
Environment: iOS 26.5, Message Filter app extension (IdentityLookup framework), offline filtering. Setup My Message Filter Extension performs offline string matching on the message body and returns one of: ILMessageFilterAction.allow / .junk / .transaction / .promotion In the Messages app the filtering UI shows these folders: Messages (the main/default folder), Transactions, Promotions, Junk. .allow is expected to surface a message in the main Messages folder. The documented behavior (API docs + WWDC22 "Explore SMS message filters") only describes a static mapping from action → folder. On iOS 26.5 I'm seeing what looks like a stateful, per-sender behavior that I cannot find documented anywhere, and I can't tell whether it is intended or a bug. Test methodology All messages in every sequence are sent from the same single phone number. Before each Case, I fully clear the receive history for that number, so every sequence starts from a clean slate with no prior state for that sender. The notation shows how many conversations/entries appear in each folder after each step. Case A — first message = allow allow → Messages: 1 promotion → Messages: 2 (allow + promotion), Promotions: 1 junk → everything collapses into Junk; Messages & Promotions become empty every subsequent message lands in Junk regardless of the action I return Case B — first message = allow, then transaction allow → Messages: 1 transaction → Messages: 2 (allow + transaction), Transactions: 1 junk → everything collapses into Junk; Messages & Transactions empty every subsequent message lands in Junk regardless of returned action Case C — first message = transaction transaction → Messages: 1, Transactions: 1 ← also appears in Messages allow → Messages: 2, Transactions: 1 promotion → Messages: 3, Transactions: 1, Promotions: 1 junk → Messages: 4, Transactions: 1, Promotions: 1, Junk: 1 (NOTE: here junk does NOT collapse the thread, and there is no "sticky junk") Case D — first message = promotion promotion → Promotions: 1 only (does NOT appear in Messages) allow → Messages: 2 (the earlier promotion now also appears in Messages), Promotions: 1 junk → everything collapses into Junk (sticky, same as Case A/B) every subsequent message lands in Junk regardless of returned action My core question: are the following two behaviors by design, or are they bugs? (1) "Sticky junk" after allow-first / promotion-first. In Cases A, B and D, once .junk is returned the whole sender thread collapses into Junk, and from then on every message is forced into Junk regardless of the action my extension returns. Is this expected/by-design, or a bug? If by design: is it permanent, and what resets it — does the extension have any control, or is it purely user-driven (e.g. the user moving the thread out of Junk)? What concerns me is that the system appears to ignore my returned action entirely once this state is entered. (2) .transaction-first behaving differently from .allow-first. A sender whose first message is .transaction (Case C) behaves differently: the message also appears in the main Messages folder, and a later .junk does not collapse the thread (no sticky junk). Is this .transaction-first behavior expected/by-design, or a bug? If by design, what is the underlying rule that makes .transaction-first confer this state while .allow-first does not? Since the history is cleared before each test, this is determined purely by the first action returned. Additional clarifying questions Is any of this per-sender state behavior documented beyond the static action → folder mapping in the API docs / WWDC22 "Explore SMS message filters"? If so, where? More generally, what determines whether a categorized (.transaction / .promotion) message is also mirrored into the main Messages folder? Thanks — I'd like my extension's return values to produce predictable categorization for users, and right now this first-message-dependent behavior makes that hard to reason about.
Topic: App & System Services SubTopic: General Tags:
0
0
68
3d
My IP address has been blocked by the forums?
I've hit a dead end with normal Apple support channels. I wrote up a radar for it (FB23333685). I used curl -v https://developer.apple.com/forums/ on my Mac via my phone's hotspot (working) and via Spectrum (not working) (some irrelevant stuff elided to shrink post): Working: % curl -v https://developer.apple.com/forums/ * Host developer.apple.com:443 was resolved. * IPv6: 2620:149:a06:f000::134, 2620:149:a06:f000::139 * IPv4: 17.253.31.140, 17.253.31.139 * Trying [2620:149:a06:f000::134]:443... * Connected to developer.apple.com (2620:149:a06:f000::134) port 443 <elided> > GET /forums/ HTTP/1.1 > Host: developer.apple.com > User-Agent: curl/8.7.1 > Accept: */* > * Request completely sent off < HTTP/1.1 200 OK < Server: Apple < Date: Mon, 22 Jun 2026 23:22:30 GMT < Content-Type: text/html;charset=utf-8 < Vary: Accept-Encoding < Set-Cookie: oid-dev-forums=; Path=/; Domain=.apple.com; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Max-Age=0; Secure; HttpOnly < Expires: Mon, 22 Jun 2026 23:22:29 GMT < X-Frame-Options: DENY < Strict-Transport-Security: max-age=31536000; includeSubDomains < Service-Worker-Allowed: / < User-Type: anonymous < Cache-Control: private,no-cache,no-store, must-revalidate, max-age=0 < Last-Modified: Mon, 22 Jun 2026 23:22:29 GMT < X-Content-Type-Options: nosniff < Content-Security-Policy: <elided> < Vary: Accept-Encoding < X-XSS-Protection: 1; mode=block < Vary: Origin < Vary: Access-Control-Request-Method < Vary: Access-Control-Request-Headers < Content-Language: en-US < X-Request-ID: 41b2b91a2a2c5e8be35787ec7b349db8 < Edge-Control: !no-store,max-age=3600 < X-Request-ID: 41b2b91a2a2c5e8be35787ec7b349db8 < Set-Cookie: myacinfo=; Path=/; Domain=.apple.com; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Max-Age=0; Secure; HttpOnly < Set-Cookie: asc_user=; Path=/; Domain=.apple.com; Expires=Thu, 01 Jan 1970 00:00:00 GMT; Max-Age=0; Secure < Set-Cookie: XID=<redacted>; Path=/; Domain=.apple.com; Expires=Wed, 22 Jul 2026 23:22:29 GMT; Max-Age=2592000; Secure; HttpOnly < Set-Cookie: df_shld_btm_prd=<redacted>; Expires=Tue, 23 Jun 2026 11:22:30 GMT; Max-Age=43200; Domain=apple.com; Path=/; SameSite=Lax; Secure < Age: 2 < Via: https/1.1 ussea4-edge-mx-005.ts.apple.com (acdn/302.16436), https/1.1 ussea4-edge-fx-007.ts.apple.com (acdn/302.16436) < X-Cache: miss, miss < CDNUUID: 42f00814-9cfb-4675-a0fa-4f3aa5ba89da-2134634100 < Transfer-Encoding: chunked < Connection: keep-alive < <!DOCTYPE html> … Failing: % curl -v https://developer.apple.com/forums/ * Host developer.apple.com:443 was resolved. * IPv6: (none) * IPv4: 17.253.83.137, 17.253.83.132 * Trying 17.253.83.137:443... * Connected to developer.apple.com (17.253.83.137) port 443 <redacted> * SSL certificate verify ok. * using HTTP/1.x > GET /forums/ HTTP/1.1 > Host: developer.apple.com > User-Agent: curl/8.7.1 > Accept: */* > * Request completely sent off < HTTP/1.1 403 Forbidden < Server: Apple < Date: Mon, 22 Jun 2026 23:16:25 GMT < Content-Type: text/html < Content-Length: 146 < Cache-Control: private, no-cache, no-store, max-age=0 < Age: 0 < Via: https/1.1 uslax1-edge-mx-005.ts.apple.com (acdn/302.16436), https/1.1 uslax1-edge-fx-015.ts.apple.com (acdn/302.16436) < X-Cache: miss, miss < CDNUUID: 4da2a4a9-3bd4-4135-b895-6b58b6d7f53b-1614544808 < Connection: keep-alive < <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> <hr><center>Apple</center> </body> </html> * Connection #0 to host developer.apple.com left intact The Spectrum response never reached the forums app at all — it was rejected at the edge node itself (uslax1-edge-mx-005 / uslax1-edge-fx-015, both LA-area). The working request happened to land on a Seattle-area edge (ussea4) via anycast routing. So this isn't an app-level or account-level block — it's a deny rule sitting on (or upstream of) the LA edge PoP for my specific IP. Thing is, I don’t know how to get help on this issue.
Topic: Developer Tools & Services SubTopic: Developer Forums
Replies
5
Boosts
0
Views
293
Activity
3d
Xcode 27 incorrectly links a Catalyst binary, _UIFontTextStyleCallout Expected in AppKit
I have a personal iOS project that I also compile for macOS with Catalyst. When built with Xcode 26.x, everything is linked correctly. When built with Xcode 27 betas, the following runtime error occurs: Termination Reason: Namespace DYLD, Code 4, Symbol missing Symbol not found: _UIFontTextStyleCallout Referenced from: <046ED276-F81A-31B4-82FF-6DC82E9041BC> /Applications/Photo Library.app/Contents/MacOS/Photo Library Expected in: <298B64F6-9BC0-3BFB-BE72-EBDC2BE0FF19> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit Any assistance? Thanks
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
2
Boosts
0
Views
96
Activity
3d
Betas not available to all developers?
It's been over 2 weeks and I still don't have the option to download the Mac or iOS 27 betas. All I see is the option for the current public betas for Tahoe and iOS 26. I am a registered developer and thought I would get access to the betas. I've submitted 2 tickets through the feedback assistant and both were closed with the comment "investigation complete - working as designed". I don't know where else to go. Is it true that not every developer gets access to beta software or that developer betas are released in phases? I've never read that anywhere nor heard that once released that beta software isn't available to all developers in the Apple dev program (not the public beta program). Can anyone shed light on this? is this true? Are betas released in phases to developers? At this rate as a developer I will have to wait until the public beta. Help!
Topic: Developer Tools & Services SubTopic: Apple Developer Program Tags:
Replies
6
Boosts
0
Views
165
Activity
3d
SB 2420 - I have no idea what to do.
I recognize that Apple has put out documentation on how to do things with the new Age APIs, but I have no idea what my apps are supposed to do to be in compliance with this law. Most of the law sounds like it applies to App Store developers like Apple, more than it pertains to individual app devs. If the age rating of an app changes, wouldn't we just put it in App Store Connect and have Apple disable those apps on the devices of the underage kids?
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
2
Boosts
0
Views
133
Activity
3d
How to get Ask Siri context menu button
In my UIKit apps, collection view cells that have a context menu gain an Ask Siri item in iOS 27 without me doing anything. In my SwiftUI app I have a LazyVGrid containing a ForEach of CellView which is a Button that has a contextMenu, yet there’s no Ask Siri button in the context menu. What determines whether or not it will be added? What do I need to do to allow the system to add it?
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
2
Boosts
0
Views
100
Activity
3d
Control center bug
Bluetooth does not show device options, whereas wifi shows the wifi options in control center.
Topic: Community SubTopic: Apple Developers
Replies
2
Boosts
0
Views
114
Activity
3d
How to clean Xcode build files？
When I tried to use Xcode to compile an app for my iPhone, it also compiled a macOS version, but they don't work. I tried to delete them from the Applications folder, but they're not there. According to the Xcode logs, I found that they're located in /private/var/folders/ and there are some deprecated projects. How should I delete them?
Topic: Community SubTopic: Apple Developers Tags:
Replies
3
Boosts
0
Views
158
Activity
3d
Xcode won't sign into ChatGPT Codex account anymore
As of May 8th, 2026, after I upgraded to "codex-cli 0.129.0" via Xcode, I can no longer sign into my ChatGPT account in Xcode Intelligence Settings. The Log In window is always successful, but the settings never update to show the login being successful. It's a constant loop. Perhaps a hand-shake fail. Versions: Tahoe 26.3.1, Xcode 26.4.1, codex-cli 0.129.0.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
8
Boosts
2
Views
1.2k
Activity
3d
Age assurance in Texas
Hello Apple Developer Support Team, We understand from the Declared Age Range documentation that, in some regulated regions, the system automatically provides the person’s age range and they can’t decline sharing it with the app. We have implemented the API as prescribed in the documentation. For certain users in Texas, the API returns: isEligibleForAgeFeatures == true declaredAgeRangeRequired == true However, in our testing we observe that these Texas users can still decline sharing their age range, either via the system prompt or later via Settings, which results in no age range being provided to the app. This behavior appears inconsistent with the documentation’s statement that, in regulated regions, the person “can’t decline” sharing their age range, and it also raises questions for us about how this aligns with the applicable legal requirements in Texas. Could you please clarify: Whether this behavior (Texas users being able to decline sharing their age range even when declaredAgeRangeRequired is true) is expected, and Under what exact conditions the “they can’t decline sharing” behavior is enforced for Texas accounts (for example, only for new Apple Accounts created in Texas after a certain date, or only for particular age categories)? Any guidance on how we should interpret isEligibleForAgeFeatures and declaredAgeRangeRequired in this scenario would be greatly appreciated. Thank you.
Topic: App & System Services SubTopic: General Tags:
Replies
0
Boosts
0
Views
89
Activity
3d
Clarification on the planned removal of UIDesignRequiresCompatibility
Dear Apple Developer Support, I am developing and maintaining an iOS application. In iOS 26, we understand that setting UIDesignRequiresCompatibility to true in the Info.plist file allows an app to opt out of the Liquid Glass design. However, we also understand that during WWDC25 Platforms State of the Union, Apple stated: "We intend this option to be removed in the next major release." We would appreciate clarification on the following points. Questions Should the phrase "next major release" be interpreted as iOS 27? Is it currently Apple's plan to make UIDesignRequiresCompatibility unavailable or remove it in iOS 27? Or is the statement above only an intended direction, with the actual removal schedule still subject to change? If there is any publicly shareable information regarding the future availability or deprecation timeline of UIDesignRequiresCompatibility, could you please provide it? Background We develop and maintain a business application that contains a large number of custom screens and UI components. Adapting the entire application to the Liquid Glass design system will require significant design review, implementation effort, and testing. As a result, the future availability of UIDesignRequiresCompatibility is a critical factor in our development planning and resource allocation. For this reason, we would greatly appreciate any guidance you can provide regarding Apple's current plans for this compatibility option. Thank you for your time and assistance. Best regards, Toshiyuki
Topic: UI Frameworks SubTopic: General Tags:
Replies
9
Boosts
0
Views
446
Activity
3d
Camera features
Hello Everyone, I am a student from India who is passionate about technology, coding, and design. I would like to propose a precise hardware and software design enhancement regarding the "LED Flash for Alerts" feature on the iPhone. Current Limitation: The existing feature utilizes the main camera flash/torch. While functional, it is incredibly bright and harsh, causing visual discomfort in dark rooms, study spaces, or classrooms. My Specific Idea: Instead of using the blinding main flash, Apple could integrate a subtle, soft white LED indicator directly inside or underneath the small black circle element located on the camera module (the sensor/microphone area). When a notification or call arrives, this exact black circle should softly pulse or glow with a clean, ambient white light. Benefits: Precision & Aesthetics: It utilizes an existing design element to create a beautiful, minimalist, and non-disruptive visual alert. User Experience: It provides a soft indicator that doesn't blind the user or disturb others in low-light environments. Power Efficiency: Illuminating a tiny dedicated ring/circle consumes significantly less battery than firing the main camera torch. As a student, I believe this subtle refinement would make the iPhone experience feel even more premium and thought-out. I would love to hear what Apple engineers and the developer community think about this!
Topic: Design SubTopic: General
Replies
1
Boosts
0
Views
97
Activity
3d
ApplePay create-session API timing out
We are an Apple Pay consumer and observed elevated response times and intermittent timeouts affecting the create‑session API (apple-pay-gateway.apple.com/paymentservices/paymentSession) between approximately 8:01 PM and 8:35 PM PST today. We are reaching out to understand whether there were any service disruptions during this timeframe, as we do not see corresponding updates on the system status pages. We would like to confirm whether this behavior was related to a broader Apple Pay issue or specific to our integration.
Topic: App & System Services SubTopic: Apple Pay
Replies
1
Boosts
0
Views
390
Activity
3d
problems of screen time
Yesterday I checked the screen time of the previous day and I thought it was 7h.But it is presented to be 10h and a half today.I'm confusing why the ended screen time could change.
Topic: Community SubTopic: Apple Developers
Replies
1
Boosts
0
Views
66
Activity
3d
Is UISceneAppIntent supported in Designed for iPad apps on macOS?
I'm seeing what appears to be different UISceneAppIntent behavior between iOS and Designed for iPad on macOS, and I'd like to confirm whether this is expected. I'm working on an iOS app that defines an AppIntent conforming to UISceneAppIntent from the AppIntents framework. The intent is handled by a scene delegate conforming to both UIWindowSceneDelegate and AppIntentSceneDelegate. On iOS, everything works as expected: If the app is launched for the first time from Shortcuts, the intent is available via connectionOptions.appIntent in scene(_:willConnectTo:options:). If the app is already running, scene(_:willPerformAppIntent:) is called. However, when running the same iOS app on macOS in Designed for iPad mode, the behavior is different: If the app is launched from Shortcuts, connectionOptions.appIntent is always nil in scene(_:willConnectTo:options:). If the app is already running, scene(_:willPerformAppIntent:) is never called, even though the application is successfully activated. Is this expected behavior? I noticed that the AppIntents framework explicitly marks both AppIntentSceneDelegate and UISceneAppIntent as unavailable on macOS: @available(iOS 26.0, tvOS 26.0, *) @available(macOS, unavailable) @available(watchOS, unavailable) public protocol AppIntentSceneDelegate : UISceneDelegate Since the app is running on macOS in Designed for iPad mode and still uses the iOS binary, I wasn't sure whether these scene-based APIs are expected to work in this environment or whether they are intentionally unsupported. Has anyone from Apple or the community been able to confirm whether this behavior is by design, or whether it should be considered a bug? I'd appreciate any clarification.
Topic: Machine Learning & AI SubTopic: App Intents Tags:
Replies
1
Boosts
0
Views
103
Activity
3d
NSFileProviderReplicatedExtension: uploading after completion handler
Hello, I'm implementing an NSFileProviderReplicatedExtension (iOS 26 and macOS 26) and would like to validate my approach. What I do To make my uploads efficient I batch them: instead of uploading file-by-file inside each createItem / modifyItem, I ingest all local changes into my extension's local state quickly and upload the content blobs in the background in batches. Concretely, for both createItem and modifyItem: I persist the item to my local store, write its content blob to a local cache, and schedule the upload in my internal queue. I call the completionHandler right away before uploading the item, returning the NSFileProviderItem with isUploaded = false. Once the upload succeeds, I flip the item to isUploaded = true and call signalEnumerator(for: .workingSet) so the change is delivered through the working-set enumerateChanges. This works in my testing, but I'm unsure it is the intended approach, and I have the following questions. Question 1 — Honoring the Progress object I call the completion handler early (step 2) and run the upload afterwards. The convenient part for my batched uploads is that I don't seem to need to honor the returned Progress at all — I never report into it and I just drop it, yet in my testing the upload still completes. I'd like to confirm two things: (a) Can I ignore the Progress? I'd like to never report into the returned Progress and simply drop it: I coalesce uploads into batches drained from a persisted queue, so I can't map one Progress to one upload, and retaining thousands of them is itself a cost. Is that allowed? What makes me unsure is that the docs read a little asymmetrically — for createItem the progress is "presented in the user interface until the completion handler is called", whereas for modifyItem it is "expected to include the upload progress … even if the provider chose to call the completion handler before the upload finishes". (b) If I ignore it, am I still granted execution time to finish the upload? This is what worries me, because the "Execution time" clause couples the two: the system "will grant enough time … to upload the file" but "will interrupt the call if it stops making progress." If I report no progress, does the system stop granting runtime? Question 2 — Upload pipeline depth When calling the completion handler before finishing the upload, both createItem and modifyItem are no longer gated by the NSExtensionFileProviderUploadPipelineDepth limit, and I can have thousands of items pending upload. This is crucial for my approach. Is this behaviour correct and intended?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
1
Boosts
0
Views
103
Activity
3d
Effect of iBeacon broadcast interval adjusting from 100ms to 50ms on iOS activation effect and system compatibility
Our current business goal is to improve the success rate of iBeacon wake-up on iOS. Apple's official iBeacon specification recommends a standard broadcast interval of 100ms; Now we are planning to shorten the broadcast frequency to 50ms, and we would like to consult the full dimensional impact of this change, and whether it can really improve the success rate of beacon identification and pull trigger on iOS devices.
Topic: App & System Services SubTopic: Maps & Location
Replies
1
Boosts
0
Views
88
Activity
3d
IAP products not loading in sandbox after activating Paid Apps Agreement
I activated the Paid Apps Agreement today along with banking and tax information. My app uses react-native-purchases (RevenueCat) with StoreKit 2. When tapping purchase buttons in TestFlight I still get "Product not available - Could not load this product." Products show "Waiting for Review" in App Store Connect. Sandbox tester is configured. Is there a delay after activating the Paid Apps Agreement before sandbox purchases work? How long should I expect to wait?
Topic: App & System Services SubTopic: StoreKit
Replies
0
Boosts
0
Views
59
Activity
3d
ESP32 USB-C to iPhone 16 USB-C communication
Hi everyone, I am seeking clarification regarding the communication capabilities between an ESP32 microcontroller and Apple's latest devices, specifically the iPhone 16 Pro Max and iPad Pro, both equipped with USB-C ports. Background: MFi Certification: Historically, establishing communication between external devices and iOS devices required MFi (Made for iPhone/iPad) certification. But I remember this being necessary in the Lightning Cable to USB era. With the introduction of USB-C ports in recent iPhone and iPad models, there is an indication that MFi certification may no longer be necessary for certain peripherals. Perhaps I'm not confident on the terminology here: https://mfi.apple.com/en/who-should-join Project Requirements: I am working on a sensor research project that necessitates the collection of low-latency time-series data from an ESP32 microcontroller, which features a USB-C port. The data needs to be transmitted to an iPhone 16 Pro Max or iPad Pro. Bluetooth communication has proven insufficient due to its limited data transfer rates (~1.2 Mbps with L2CAP). While NEHotspot could be an alternative, it restricts the iPad's internet connectivity. Therefore, establishing a direct USB-C connection between the ESP32 and the iOS device appears to be the most viable solution. Questions: MFi Certification Necessity: Is MFi certification still required for an ESP32 microcontroller to communicate with iPhone 16 Pro Max or iPad Pro via USB-C? USB-C Communication Support: Do the iPhone 16 Pro Max and iPad Pro natively support serial communication over USB-C with microcontrollers like the ESP32? If not, are there recommended protocols or interfaces to facilitate this communication? App Development Considerations: Would developing a custom iOS application be necessary to handle data transmission from the ESP32 over USB-C? If so, are there specific APIs or frameworks provided by Apple to support this functionality? Data Transfer Rates: Considering the need for high-speed data transfer, are there any limitations or considerations regarding the data transfer rates achievable through a USB-C connection between the ESP32 and iOS devices? Thank you!
Topic: App & System Services SubTopic: Hardware Tags:
Replies
6
Boosts
1
Views
2.3k
Activity
3d
Unable to receive 2FA SMS - TestFlight blocked, 250+ users waiting
Case ID: 102924093872 Case ID: 102924089648 Hi Apple Support Team, I’m reaching out regarding a critical issue that is blocking my app testing and affecting hundreds of users. I cannot receive the two-factor authentication code for my Apple Developer account. My mobile operator has confirmed that SMS messages from Apple are not reaching their network at all. I also receive no calls. Since my account is not logged in on any device, SMS is the only way I can verify my identity - and it’s not working. I have already submitted two support cases but have not received any response yet. Here is the impact this is having right now: • 250+ people are waiting to get access to test my app • 400 users are already using the app • I cannot sign the new agreement that appeared in App Store Connect • Because of this, TestFlight is completely blocked - both the 10,000 user limit and the 100 user internal testing • Even when I add someone to my team and grant them access, it still doesn’t work for them either I have been building this app for almost 7 months. We are in the final testing stage before I plan to release it for sale. Every day without access is a day my users are waiting and I cannot move forward. I am asking you to please help me resolve this as quickly as possible. I really need your support right now. Thank you so much for your time. Best regards, Tata
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
1
Boosts
0
Views
58
Activity
3d
Message Filter Extension: undocumented per-sender ILMessageFilterAction categorization state on iOS 26.5 — by design or bug?
Environment: iOS 26.5, Message Filter app extension (IdentityLookup framework), offline filtering. Setup My Message Filter Extension performs offline string matching on the message body and returns one of: ILMessageFilterAction.allow / .junk / .transaction / .promotion In the Messages app the filtering UI shows these folders: Messages (the main/default folder), Transactions, Promotions, Junk. .allow is expected to surface a message in the main Messages folder. The documented behavior (API docs + WWDC22 "Explore SMS message filters") only describes a static mapping from action → folder. On iOS 26.5 I'm seeing what looks like a stateful, per-sender behavior that I cannot find documented anywhere, and I can't tell whether it is intended or a bug. Test methodology All messages in every sequence are sent from the same single phone number. Before each Case, I fully clear the receive history for that number, so every sequence starts from a clean slate with no prior state for that sender. The notation shows how many conversations/entries appear in each folder after each step. Case A — first message = allow allow → Messages: 1 promotion → Messages: 2 (allow + promotion), Promotions: 1 junk → everything collapses into Junk; Messages & Promotions become empty every subsequent message lands in Junk regardless of the action I return Case B — first message = allow, then transaction allow → Messages: 1 transaction → Messages: 2 (allow + transaction), Transactions: 1 junk → everything collapses into Junk; Messages & Transactions empty every subsequent message lands in Junk regardless of returned action Case C — first message = transaction transaction → Messages: 1, Transactions: 1 ← also appears in Messages allow → Messages: 2, Transactions: 1 promotion → Messages: 3, Transactions: 1, Promotions: 1 junk → Messages: 4, Transactions: 1, Promotions: 1, Junk: 1 (NOTE: here junk does NOT collapse the thread, and there is no "sticky junk") Case D — first message = promotion promotion → Promotions: 1 only (does NOT appear in Messages) allow → Messages: 2 (the earlier promotion now also appears in Messages), Promotions: 1 junk → everything collapses into Junk (sticky, same as Case A/B) every subsequent message lands in Junk regardless of returned action My core question: are the following two behaviors by design, or are they bugs? (1) "Sticky junk" after allow-first / promotion-first. In Cases A, B and D, once .junk is returned the whole sender thread collapses into Junk, and from then on every message is forced into Junk regardless of the action my extension returns. Is this expected/by-design, or a bug? If by design: is it permanent, and what resets it — does the extension have any control, or is it purely user-driven (e.g. the user moving the thread out of Junk)? What concerns me is that the system appears to ignore my returned action entirely once this state is entered. (2) .transaction-first behaving differently from .allow-first. A sender whose first message is .transaction (Case C) behaves differently: the message also appears in the main Messages folder, and a later .junk does not collapse the thread (no sticky junk). Is this .transaction-first behavior expected/by-design, or a bug? If by design, what is the underlying rule that makes .transaction-first confer this state while .allow-first does not? Since the history is cleared before each test, this is determined purely by the first action returned. Additional clarifying questions Is any of this per-sender state behavior documented beyond the static action → folder mapping in the API docs / WWDC22 "Explore SMS message filters"? If so, where? More generally, what determines whether a categorized (.transaction / .promotion) message is also mirrored into the main Messages folder? Thanks — I'd like my extension's return values to produce predictable categorization for users, and right now this first-message-dependent behavior makes that hard to reason about.
Topic: App & System Services SubTopic: General Tags:
Replies
0
Boosts
0
Views
68
Activity
3d