what can i do?

Hello, Shortcuts and App Intents don't work on simulators running iOS 26 or iOS 27. It's working fine on simulators running iOS 18. It makes testing and adopting new technologies difficult. Please check this feedback which contains a video showcasing the issue with a sample code provided by Apple: FB23342158 Regards, Axel

Hello, I enrolled in the Apple Developer Program on June 14, 2026. The annual fee was charged successfully and I received the receipt from Apple. I also completed the identity verification (with my driver's license). Despite this, my account has been showing "Pending" status for more than two weeks now. As a result, I have no access to App Store Connect — it shows the message "Your Apple Account is not set up for iTunes Connect," so I cannot create my app or upload a build to TestFlight. My app is finished and ready; I am only waiting for the enrollment to be completed. I have already submitted a support request by email (the form mentioned a 2 business day response time), but I wanted to open a thread here as well, since I can see from other recent posts that I'm not the only one affected. Apple Developer Support — could you please look into this and let me know why the enrollment is not being completed? I would appreciate any help getting my account activated. Thank you.

Hi, I have been testing Xcode 27 beta 2 on macOS 27 beta 2 on a MacBook Air M2 (base model) with 16 GB of memory. When loading previews for the first time, it could take a while, but it looks significantly longer compared to Xcode 26.x on macOS 26.x. Then when trying to launch a simple app with a few screens, the Device Hub takes forever, and then on Activity Monitor, the swap used starts to climb up, almost as high as 12 GB or more. Running an app on Device Hub is almost impossible. Is this a limit of what a MacBook Air can do? This is not my primary machine by the way.

I was hoping this was fixed in Beta 2, but I am having the same issue. I run my app: on a simulator device Device Hub opens Begins installing the app I see the icon and it starts to fill in The launch screen loads and never finishes loading. I then stop running app in Xcode. Device Hub still shows launch screen I restart device in Device Hub I then can open the app and test Anyone else experiencing this? I would really like to solve this as it makes testing changes a frustrating experience. Because I then have to close Device Hub and Xcode to simulate again.

ChatGPT stopped working in Xcode MacBook Air M2 2022 MacOS 26.5.1 Xcode 26.5 ExpressVPN Version 11.71.0 (90727) Internet connection is working fine. On late night June 22, ChatGPT in Xcode was working fine. Then I started getting “cannot complete” messages with “network error”. Now ChatGPT in Xcode does not work at all. My subscription to ChatGPT auto-renewed on June 23. My bank confirms that the payment went through. I logged into ChatGPT in Safari and Firefox. The account looks fine. In Xcode settings/Intelligence/ChatGPT in Xcode, the Usage Limit says Under Limit. I signed out of ChatGPT from within Xcode, and signed back in. It still is not working. I quit and restarted Xcode, then signed out of ChatGPT again, and signed back in. Still not working. Restarted my Mac, opened Xcode. It still doesn’t work. Signed out and back into ChatGPT in Xcode. ChatGPT still is dead. Disabled VPN. Quit and restarted Xcode. ChatGPT still not working. 1-800-ChatGPT was no help at all. I can use ChatGPT while logged into my account on their website. I told it “ChatGPT in Xcode has stopped working”. It came back with: “I’ll help narrow this down. I’ll check current official OpenAI guidance/status first, then give you the fastest troubleshooting path for Xcode specifically. Thought for 6s Try this order: 1 Update ChatGPT for macOS — Work with Apps/Xcode needs ChatGPT macOS 1.2025.057 or later. 2 Restart both apps: quit ChatGPT and Xcode completely, then reopen Xcode first, ChatGPT second. 3 In ChatGPT macOS, check Work with Apps is enabled and Xcode is selected/available. 4 macOS permissions: System Settings → Privacy & Security → Accessibility and Automation. Make sure ChatGPT is allowed to control/read Xcode. 5 In Xcode, open an actual source file and put focus in the editor, then try ChatGPT again. 6 Check OpenAI status; current status page shows ChatGPT service status and incidents. 7 If on corporate/VPN network, try off VPN; OpenAI notes TLS/SSL inspection can break app access. Most common fix: update ChatGPT macOS + re-grant Accessibility/Automation permissions.” I never had the app ChatGPT for MacOS. I set up an account on ChatGPT.com and enabled it in Xcode. That was working fine until the June 23. ChatGPT is not in System Settings → Privacy & Security → Accessibility. Downloaded ChatGPT for MacOS. Quit Xcode. Added ChatGPT to. System Settings → Privacy & Security → Accessibility. Started ChatGPT. Started Xcode. Signed out of ChatGPT in Xcode, and signed back in. ChatGPT in Xcode still is dead. I am at a complete loss. Can anyone help? Doug

M4 Mac Mini: Xcode generates private keys with wrong label - codesigning impossible Background This is a follow up to my November 2024 thread "Keychain issues after installing backup on new Mac" which was closed because I had a temporary workaround. That workaround using my wife's MacBook Air for signing is not sustainable. I used AI assistance to determine the root cause. My DTS case 102877839447 is open but has not yet been forwarded to a DTS engineer. Environment Mac Mini M4, macOS 15.4.1 (Build 25E253) Xcode 26.4.1 (17E202) Team ID: Q23726668V (Computerade Products) Working comparison machine: MacBook Air, macOS 15.3 Precise Bug — Reproducible Every Time Every time Xcode generates a new certificate and key pair on my Mac Mini: Certificate: Apple Development: Michael Birch (9KD5TCGGHG) ✅ Private key: Apple Development: Michael Birch (Computerade Products) ❌ The key uses the organization name instead of the certificate identifier. They never pair as a valid codesigning identity. security find-identity -v -p codesigning always returns 0 valid identities. Cryptographic Evidence The internal application labels confirm the keys are cryptographically unrelated to their certificates: Key internal application label: 53C26EB056997276B5E938258D00665ACABD1F0F Certificate public key hash: 57cd1af4a9162f26b1a6d750e05a63a2166b75ff These do not match ❌ Confirmed Eliminated As Causes Keychain search list corruption — found and fixed Partition list — set correctly Access control — set to allow all applications Full Disk Access — granted to Xcode Xcode caches and preferences — completely cleared Login keychain — completely reset Orphaned certificates and keys — all removed SIP enabled, system fully up to date Valid P12 Import Also Fails A p12 exported from the working MacBook Air and cryptographically verified as a matched pair also fails on the Mac Mini: security import returns MAC verification failed Keychain Access import returns OSStatus -2 Importing certificate and key separately as PEM files succeeds but they are not recognized as a valid identity pair despite matching application labels A3F3F193B7896DA9055353F59AB450778CB09AE7 Question Is there a known issue with M4 Mac Mini keychain infrastructure where private keys are generated with incorrect internal application labels? Is there a lower level diagnostic or fix beyond what the security command provides? The problem is specific to my Mac Mini M4 and persisted thru more than a year of Mac OS and xCode updates.

I’m running into an issue in App Store Connect where I’m being blocked from creating a new app version because it says I need to accept the latest Apple Developer Program License Agreement. However, I already accepted the agreement two days ago. When I go back to the agreements area, it appears that the agreement has been signed ("Issued June 18, 2026. Accepted June 24, 2026."), but the prompt still appears and continues preventing me from creating a new version. I’ve tried refreshing App Store Connect and checking again, but the issue is still happening. Has anyone else run into a delay where App Store Connect takes time to recognize the accepted agreement? Is there anything else I should check, or is this something that requires Apple Support to resolve? Thanks!

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.

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

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!

My iPhone 14 Pro (running iOS 27 beta 1) is not booting after discharge of battery (due to not being used for about 10 days). How to restart and update to beta 2 or use it otherwise? I have kept it connected to wall outlet charger for the past 2 hours, and have tried Forced restart (press and quickly release the Volume Up button, press and quickly release the Volume Down button, then press and hold the Side (Power) button until the screen goes black and the Apple logo appears). But nothing works, and the iPhone remains dead.

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.

I know Xcode 27 is in beta but it appears that in Device Hub you can no longer drag and drop enterprise security certificates onto the simulators like you could in Xcode 26 (and earlier) simulators. I did put in a feedback request in (FB23369006) but I was wondering if anyone found a workaround. This hampers testing for enterprise users who don't have a physical device to test on.

We need help to structure our project to start using apple standard way to create Xcode project. let me first express how currently we are creating Xcode project. As of today, we are using CMake to generate our xcode project which we can open in XCODE IDE and build/debug/run/etc. XCode IDE can open those project but we notice that some build setting does not seem to have correct value while looking into XCODE IDE but it somehow builds. There are some other issues also. Along with those issues, we also could not share this xcodeproject generated via CMake to AppleDTS support team as Apple does not support project created via some third party tool (like CMake or others). Let me also express why we decided to use CMake at first place to generate Xcode projects. Our project is layered architecture project where in upper layers uses lower layer artifacts. Each layer has its own set of build targets . And each layer can have both C++ and Swift files. And each layer would have most of the compiler flag common, but we could also have compiler flag specific to each layer also. To achieve all these, we have developed our own tool, which basically creates CMakeLists.txt (for project model- all targets, dependency, etc) and CMakePresets.json (for all compiler and linker flags). Now this tool scans through repos/source folders on each layer and then creates these files (CMakeLists.txt and CMakePresets.json). This tool uses inputs to decide compiler/linker/other properties from one centralized location. Which means every developer would use these same input files and thus they all can have same compiler/linker/other properties set consistent. This makes generated build system consistent on all developer machine and it allows confidence of saying if build works on one developer's machine would also work on other developer’s machine and if build does NOT work on one developer's machine, it would NOT work on other developer’s machine also. So, it’s consistent. That was the main reason to use CMake to generate xcode project. So, our internal tools creates meta data for CMake (which is CMakeLists and CMakePresets) and then CMake generates Xcode build system using XCode generator. Now we want to move to xcode native way to create projects but at the same time we also want this consistency that each of my developer would use exact same compiler/linker/other properties. If we ask developer to use XCode IDE to create xcode project, we cannot guarantee that they all will use same compiler/linker/etc flags and thus we would end up having inconsistent behaviour on different developer machines. We need your help to figure out how we can achive this ? We read some ways that we can create some template project and then we can create some .xcconfig files and use them to set target properties but honestly, we are able to stich them together. So please help us directionally on this , how should we proceed ? Basically we need to know how can we have all my developer use same xcodeproject. I was also thinking how would I be setting my CI for apple builds if I have to use XCode IDE to create xcode project and since CI environments are non interactive and it can happen n number of times in day (if I have setup to run sanity for all Pull Requests). Any help/direction on this is highly appreciated.

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

Hi, I'm having a strange issue with my new MacBook Pro M5. My iPhone 17 is connected via USB. The phone appears in Finder, so the Mac clearly detects it, and I can access it there. However, the Xcode doesn't see the iPhone at all. Both the MacBook Pro and the iPhone are running version 26.5. What's confusing is that the exact same iPhone and the exact same USB cable work perfectly with my older Intel-based MacBook Pro. Has anyone else experienced this, or have any suggestions on what I should check?

Hi — I'm trying to notarize a Developer ID–signed macOS app (a small menu-bar .dmg, ~1.4 MB) and every submission has been stuck at status: In Progress for 7+ hours without ever reaching Accepted or Invalid. The Developer System Status page shows the Notary Service as green/operational. This is a recently enrolled account (Individual) and these are its first notarization submissions, so I suspect a first-time-on-new-account hang, but wanted to get it looked at. Team ID: C4GLRN98Q7 Submission IDs (all still In Progress): a206d94b-c0e7-4901-a35e-daaf69c8ec65 — created 2026-06-25 19:02 UTC (oldest, ~7h+) 71d08fb3-0ae0-413a-8004-e3fb99721403 — 2026-06-25 19:32 UTC a6687302-d7b2-43be-8098-1442f0b1d4ab — 2026-06-25 19:45 UTC a8428002-0cd0-4d46-bc6d-8e95b9df409b — 2026-06-25 19:58 UTC cb8602bf-386e-4d98-9d1a-ad7e5308e629 — 2026-06-26 02:16 UTC (newest) What I'm doing: Signing with codesign --options runtime --timestamp using a Developer ID Application cert, then submitting the .dmg with xcrun notarytool submit … --keychain-profile … --wait. codesign --verify --strict passes locally. xcrun notarytool info returns valid submission metadata, just perpetually In Progress. The very first --wait died on a local network drop, but the submission had already uploaded 100% and kept processing server-side; I have not been spamming — the repeats above were a handful of retries before I realized they were all hanging. I've stopped submitting new ones. Could someone check why these submissions aren't completing? Happy to provide a notarytool log once any of them finishes. Thanks!

I wonder is anyone at Apple still using Interface Builder for anything… Across Xcode 16.x and 26.x, IB has become increasingly and noticeably slower to open storyboard and xibs. I see zero improvements in Xcode 27 beta. This morning I had both 26 and 27 going fairly quickly into "application not responding" state when trying to render a rather simple layout in storyboard. What's making it worse is that force-quitting the app and starting again leads straight back into the same storyboard and then locks up again. It does not matter if I manage to switch to a .swift file — it's clearly still doing something in the background related to that storyboard and gets stuck. I eventually managed to open just the .storyboard (without the project), fix the offending layout bits and now it's at least not getting stuck although it still takes good 5-6s before it renders a layout with about a dozen components. I assume something with LLM agents is the reason for this issue but come on people — this is infuriatingly incapacitating tool for people like me that are still maintaining UIKit apps.

Hello, I have a problem with the Retention Message API. The default message is not displayed to users when they try to cancel their subscription in the device's Settings app. The API configuration was made with Revenue Request. The request to use this API was approved by Apple for our account. After configuring it for the Sandbox environment, everything worked as expected the image and text were displayed to users. Later, I applied the same configuration to the Production environment. I received the Approved status for the message, but after purchasing the subscription from the App Store, although I can see the subscription in Settings, the retention message is not displayed when I attempt to cancel it. I have tried different Apple accounts from different regions (both EU and non-EU) and tested from physical locations without using a VPN. Also, for clarification, we do not use real-time communication only the default retention message. For additional information: I also tried configuring this message from App Store Connect, as shown in WWDC 2026, but this section is not available under the Subscriptions category. When I deactivate and then reactivate the message, I notice that the deactivated state shows the text status "Waiting for sync (0/9)", while the active state shows "Approved". All other assets have an Approved state. In my case, the message is configured for all subscription types without any filters or other restrictions. What could be causing this problem, and how can I fix it? It seems that the issue is not on my side.