Overview On Xcode 27, when trying to run on a specific destination, the option to “Clear Recent” is missing. This was available in Xcode 26. Manage Devices option exists, but this is to permanently add / remove destinations, this is different from “Clear Recent”. Please bring back “Clear Recent” (from Xcode 26 to Xcode 27) option to Xcode as it is very useful Environment: macOS 26.5.1 (25F80) Xcode 27.0 beta (27A5194q) Feedback FB23055381

I have two lines through Verizon wireless, my main line for the account was acting like a dead eSIM every time it is on it kills my data completely even on the second phone line unable to send a receive phone calls, send a receive text messages, retrieve voicemails, or use data in any capacity from that line. I have completely deleted and reinstalled and reactivated eSIM for that line a handful of times in the last week/week and a half & it is the main account line being rendered completely unusabl.

Hi everyone, I am currently completely blocked from submitting my new app for TestFlight Beta Review (External Testing). The App Store Connect web interface fails to submit, and when I try to bypass the UI using the App Store Connect REST API to create a betaAppReviewSubmissions request, Apple's servers return the following 422 error: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Here is what I have already checked and verified on my end: Agreements, Tax, and Banking: My "Paid Apps Agreement", "Free Apps Agreement", "U.S. Tax Forms", and "Bank Accounts" all clearly show as "Active" status. There are absolutely no pending banners or unaccepted agreements on developer.apple.com or appstoreconnect.apple.com. Apple Developer App: I logged into the official iOS Apple Developer app with the Account Holder ID, and there are no hidden agreements to accept there either. App Privacy: All data collection questions are answered, and the App Privacy section is fully Published. Test Information: All required Beta App Review details (Name, Email, Phone) are correctly filled. Export Compliance: My Info.plist includes <key>ITSAppUsesNonExemptEncryption</key><false/>, and the build attributes confirm it. It appears that my TestFlight beta contract has somehow become detached, bugged, or failed to provision on Apple's backend. Has anyone experienced this specific API error recently? Is there a way to force the system to re-provision the contract, or does this strictly require manual intervention from an Apple Engineer? Any guidance would be highly appreciated. Thanks!

I have tried to upgrade to macOS 27 Beta from 26.1 Beta on my MacBook Air M1, but it just doesn't work. I've tried: Software update Installer Terminal both in normal boot and safe boot. Six attempts, none worked. Here are some screenshots: P lease help as I'm freaking out. Thanks in advance! Specs: OS: macOS 26.1 Beta (25B5057f) Chip: Apple Silicon M1 RAM: 8GB

Device: iPhone 17 Pro iOS Version: iOS 27 beta Problem Description I am experiencing the following issues on iOS 27 Beta: Bluetooth randomly turns off and on automatically • Bluetooth occasionally turns off by itself for a few seconds and then turns back on. • The issue is especially severe when connected to AirPods Pro 2 (latest beta firmware), but it also occurs even without AirPods connected. • It usually only starts happening frequently after the iPhone has been powered on for a long time. Restarting the device temporarily resolves it. 2. Network Connection Issues • Network frequently experiences lag and slow speeds. • The problem becomes particularly noticeable when cellular data is throttled to 1 Mbps. • Even when multiple strong Wi-Fi signals are available, the device often ignores them and continues using or automatically switches back to cellular data (relatively frequent intermittent issue). 3. Feedback Assistant completely broken • Trying to submit feedback through the Feedback Assistant app delay fails with the following error: 开始反馈时出错 请稍后再试。

https://support.apple.com/en-us/126655 As stated in the “Prepare your network environment for stricter security requirements.” my understanding is that additional security requirements will be introduced from OS 27 onward and that we need to prepare for them. However, I understand that the content on this page is mainly about distributing apps and operating the app itself. For example, I believe that simply accessing a web page within the app, or conducting HTTP communications with servers unaffiliated with Apple, will remain possible as before. Is my understanding correct?

I had recently updated my mac to beta 27.0, but regular Xcode isn't supported on this beta version. So, I downloaded Xcode Beta from Apple Developer. Now when I'm trying to deploy an app for AppStore review, it is prompting me that beta builds can't upload an app. Is there any fix that I can again use normal Xcode in my mac ?

I'm trying to install Mac OS 27 on my Mac Book Pro m1 pro and I'm getting this error: I have tried from the terminal, clearing the cache, and I've tried a couple of different days and the issue still occurs. Internet connection if fine, no VPNs and nothing that should block it.

On earlier iOS versions Live Activity displays correctly according to mode set.  Can't find an opened issue for that version: iOS 26 device: iPhone 16

Hi everyone, My TestFlight build has been stuck in 'Waiting for Review' for over 32 hours and I'm hoping someone can help or share their experience. The situation: I have an External Testing group with a Public Link set up. The build was submitted for Beta App Review on March 19th but it's been over 32 hours with no update. I have 25+ testers waiting to install the app. What I've tried: Waited patiently Checked App Store Connect multiple times No rejection emails received No issues flagged by Apple Questions: Is anyone else experiencing unusually long review times for TestFlight external builds right now? Is there anything I can do to speed up the process or check if something is wrong? Has anyone successfully resolved this by contacting Apple Developer Support directly? Any advice would be greatly appreciated. Thank you! Apple Support Case ID: 102846633409

I am seeing serious issues with iPhone Mirroring on macOS 27 Developer Beta 1. Environment Mac: MacBook Pro, Apple M4 Pro Model: Mac16,7 RAM: 24 GB macOS: macOS 27.0 Developer Beta 1 Build: 26A5353q SIP: Enabled Developer Mode: Enabled iPhone: iPhone 15 Pro Max Previously tested on: iOS 27 Beta 1 Currently restored to: iOS 26.5 Issue 1: iPhone Mirroring does not connect on iOS 27 Beta 1 and can leave the iPhone unusable When my iPhone 15 Pro Max was running iOS 27 Beta 1, iPhone Mirroring on macOS 27 Developer Beta 1 did not connect properly. I tried connecting multiple times. The iPhone appeared to think that the mirroring session had started successfully, because the iPhone screen turned off as expected for iPhone Mirroring. However, the Mac never actually completed the connection and never displayed the mirrored iPhone session. After this happened, the iPhone became completely stuck and unresponsive. The phone did not respond normally, and even force restart attempts were not working. The device remained unusable until the battery fully drained, which took about two days. After the battery was fully depleted, I was able to put the iPhone into DFU mode and restore it back to iOS 26.5. This suggests that something may be broken in the iPhone Mirroring / Continuity connection state between macOS 27 Developer Beta 1 and iOS 27 Beta 1. The iPhone seems to enter a state where it believes it is connected for mirroring, while the Mac never actually establishes the session. Issue 2: iPhone Mirroring crashes on macOS 27 Developer Beta 1 when used with iOS 26.5 After restoring the iPhone 15 Pro Max back to iOS 26.5, I was able to get a crash report from the Mac side. The iPhone Mirroring app crashed on macOS 27 Developer Beta 1 with the following details: Process: iPhone Mirroring Identifier: com.apple.ScreenContinuity Version: 2.0 Build Version: 114.38.15.1 OS Version: macOS 27.0 (26A5353q) Hardware Model: Mac16,7 Exception Type: EXC_BREAKPOINT (SIGTRAP) Termination Reason: Namespace SIGNAL, Code 5, Trace/BPT trap: 5 Triggered by Thread: 2 Dispatch Queue: com.apple.root.user-initiated-qos.cooperative The crashed thread shows a Swift assertion failure inside ScreenSharingKit.framework: Thread 2 Crashed: 0 libswiftCore.dylib assertionFailure(:_:file:line:flags:) + 216 1 ScreenSharingKit 0x29fbb60e0 2 libswiftCore.dylib _swift_release_dealloc + 64 3 libswiftCore.dylib RefCounts::doDecrementSlow 4 ScreenSharingKit 0x29fa894c0 5 ScreenSharingKit 0x29fb484d8 6 ScreenSharingKit 0x29fb48614 ... 15 libswift_Concurrency.dylib completeTaskWithClosure Relevant binary image: /System/Library/PrivateFrameworks/ScreenSharingKit.framework/Versions/A/ScreenSharingKit CFBundleIdentifier: com.apple.screensharing.ScreenSharingKit CFBundleVersion: 114.38.15.1 Crash interpretation The crash appears to be a first-party Apple framework crash inside ScreenSharingKit, caused by a Swift assertion failure. It does not appear to be caused by memory pressure, Rosetta, or third-party code injection. Relevant crash report details: External Modification Summary: task_for_pid: 0 thread_create: 0 thread_set_state: 0 System Integrity Protection: enabled Memory usage also does not look excessive: Writable regions: Total=251.0M MALLOC: 128.4M Expected behavior iPhone Mirroring should either connect successfully or fail gracefully. It should not: Leave the iPhone in a stuck/unresponsive state. Put the iPhone screen into mirroring mode while the Mac never completes the connection. Require the iPhone battery to fully drain before DFU restore is possible. Crash on macOS with an internal ScreenSharingKit Swift assertion failure. Actual behavior On iOS 27 Beta 1: iPhone Mirroring never completed the connection on the Mac. The iPhone behaved as if the session started. The iPhone screen turned off. The iPhone became completely unresponsive. Force restart did not work. Device only became recoverable after battery fully drained. I then restored the iPhone to iOS 26.5 via DFU. On iOS 26.5: iPhone Mirroring was able to run, but the Mac-side app later crashed. The crash occurred inside Apple’s ScreenSharingKit.framework. The crash type was EXC_BREAKPOINT (SIGTRAP) from Swift _assertionFailure. Reproducibility Partially reproducible. iOS 27 Beta 1 + macOS 27 Developer Beta 1: connection repeatedly failed and eventually left the iPhone stuck. iOS 26.5 + macOS 27 Developer Beta 1: iPhone Mirroring can connect, but the Mac app crashed with the attached report. Crash identifiers Incident Identifier: B6D4D86D-03C4-4466-B9D6-4CF70DF0B46F Crash Reporter Key: 8BD85D40-8AC8-E771-2D80-153D7C4C5366 Process: iPhone Mirroring [11429] Bundle ID: com.apple.ScreenContinuity The crash report points to ScreenSharingKit.framework, so this looks like a possible beta regression in the iPhone Mirroring / Continuity stack.

Hello Apple Developer Support, After updating my iPad to iPadOS Beta 27, the Notes+ app has started crashing frequently. This issue did not happen before the system update. The app often crashes when I open notes, edit content, or try to use files inside Notes+. Another serious issue is that I cannot properly download or import files from iCloud Drive into Notes+. When I try to select a file from iCloud Drive and add it to Notes+, the process may fail, freeze, or cause Notes+ to crash. This has made Notes+ very difficult to use on iPadOS Beta 27. I rely on Notes+ for study notes, file organization, and daily productivity, so this problem has a big impact on my normal use. Steps to reproduce: 1.Use an iPad running iPadOS Beta 27. Open the Notes+ app. 2.Open or edit an existing note. 3.Try to import or attach a file from iCloud Drive. 4.Notes+ may freeze, fail to import the file, or crash. Expected result: Notes+ should run normally, and files from iCloud Drive should be imported into Notes+ successfully. Actual result: Notes+ crashes frequently, and iCloud Drive files cannot be imported reliably. This issue started after updating to iPadOS Beta 27. Please check the compatibility between iPadOS Beta 27, Notes+, and iCloud Drive file importing. Thank you.

Retrained Siri multiple times, turned off and on, hard reboots, cannot clear the badge on Settings icon asking to reset Siri. Siri working, new Siri on waitlist. How to clear? IOS 27 beta 1, iPhone 17 Pro.

The documented template for @AppEntity(schema: .messages.message) at Integrating your messaging app with Apple Intelligence and on the MessagesEntity.message reference page shows: var reaction: <#ReadReaction#>? with <#ReadReaction#> rendered as a placeholder (the Xcode placeholder syntax). A natural reading is "fill in your own type that you want to use here". I tried several: Tapback? where Tapback is @AppEnum(schema: .messages.customReaction) MessageReaction? (same, renamed) MessageReaction? with manual AppEnum conformance (no schema decoration) AttributedString? AttributedString (non-optional) field omitted entirely Each variant produced one of: error: Property 'reaction' type does not match required AppSchemaEntity property type 'ReadReactionCases:(Schema<Tapback> | AttributedString)' error: Required AppSchemaEntity property 'reaction' must be optional error: Missing required property 'reaction' from AppSchemaEntity 'messages.message' The phrase ReadReactionCases:(Schema<Tapback> | AttributedString) is opaque — ReadReactionCases isn't a public type, Schema<Tapback> isn't constructable from outside, and the documentation doesn't mention @UnionValue in this context. The actual working pattern, which I only found by downloading the UnicornChat sample and reading MessageEntity.swift, is: @UnionValue enum MessageReaction: Sendable { case customReaction(CustomReaction) } @AppEnum(schema: .messages.customReaction) enum CustomReaction: String, AppEnum { case sticker static let caseDisplayRepresentations: [Self: DisplayRepresentation] = [ .sticker: "Sticker" ] } Two suggestions: Update the schema-template comment in the docs to either name MessageReaction explicitly with a @UnionValue annotation, or include a one-line note: "The reaction field is a @UnionValue enum wrapping the customReaction schema enum — see UnicornChat sample." The current placeholder <#ReadReaction#> plus the prose suggesting "you can generate the properties... with the @AppEntity(.messages.message) Swift macro" reads as if the developer just supplies any AppEnum-conformer. Improve the diagnostic. Property type does not match required AppSchemaEntity property type 'ReadReactionCases:(Schema<Tapback> | AttributedString)' is unhelpful because ReadReactionCases doesn't appear in any reachable type. Either rename to something developer-facing, or include a fix-it that suggests @UnionValue. iOS 27.0 beta, Xcode 27 beta, macOS Tahoe 26.4.

There are two beta restore files for A16, both are for ipad15,8. Please post one for ipad15,7

Ever since I updated my Mac mini M4 to macOS 27 (Golden Gate), the Applications icon in my Dock has stopped working completely. Clicking it does nothing. Is this a known bug, or is there something wrong with my system? Has anyone else experienced the same issue after updating? If there's a fix or workaround, I'd really appreciate the help. Thanks!

Can anyone help me with this error message? Beta contract is missing for the app. Error IDs: 3976de05-9ac1-41e1-9294-a8827535015e 96bfccea-8fe8-450a-8cff-fbc55b696b29 I have tried looking at agreements, there is nothing to sign or that I have not accepted. I cannot find any agreement related to this. I have tried sending my app for TestFlight review from web browser or TestFlight app in my iPhone but no help at all I get the same error message. I have tried sending request to Apple support to call me but that also ends up with error. Is there anything wrong going with Apple. How can we contact Apple? They are not replying to my emails either.

I'd like to use Xcode 27 Beta, for its Coding Intelligence features, on existing iOS 17 thru 26 production code. As long as I don't allow iOS 27 as a target, will I be able to use Xcode 26 to submit the Xcode 27 project files now to the App Store for distribution? I can imagine situations where Xcode 27 makes use of a new backward-compatible API feature that Xcode 26 balks at. Perhaps I'll have to watch out for that, unless there's a way to tell Xcode 27 to avoid it automatically?

Since the iOS 18 and Xcode 16, I've been getting some really strange SwiftData errors when passing @Model classes around. The error I'm seeing is the following: SwiftData/BackingData.swift:409: Fatal error: This model instance was destroyed by calling ModelContext.reset and is no longer usable. PersistentIdentifier(id: SwiftData.PersistentIdentifier.ID(url: x-coredata://34EE9059-A7B5-4484-96A0-D10786AC9FB0/TestApp/p2), implementation: SwiftData.PersistentIdentifierImplementation) The same issue also happens when I try to retrieve a model from the ModelContext using its PersistentIdentifier and try to do anything with it. I have no idea what could be causing this. I'm guessing this is just a bug in the iOS 18 Beta, since I couldn't find a single discussion about this on Google, I figured I'd mention it. if someone has a workaround or something, that would be much appreciated.

Anyone unable to configure their widgets on iOS 27? I can edit a widget’s configuration but that doesn’t have any effect on the widget. I’m seeing this in the simulator and I have some users seeing it on-device. Is this a known issue or are there workarounds?