I am testing out the new auto-generated subtitles feature on iOS 27 and tvOS 27. It works on iOS, but not on tvOS. Very same HLS videos. Anyone have any experience with auto-generated subtitles on tvOS 27? AFAICT, there is no special code needed to enable this feature for our apps, correct?

Summary On iOS 27 the top scroll edge effect of a UITableView is sized around the UIRefreshControl as an edge element, but appears to key on the control's presence in the scroll view rather than its current height. After endRefreshing(), the control collapses to zero height but stays attached, and the effect region keeps reserving a refresh-control's worth of space. The first row stays blurred and dimmed even though it is scrolled fully clear of the navigation bar. Environment iOS 27 (beta), iPhone Xcode 27.0.0 Beta 4 UIKit, UITableView inside a UINavigationController Reproduces with the default edge effect style and with an explicit .soft Steps to reproduce Push a UITableViewController with a UIRefreshControl onto a navigation stack. Ensure content extends under the navigation bar (default for UITableViewController). Pull to refresh and let the refresh end. Observe the first row after the refresh control has retracted. Expected Once the control retracts, the edge effect returns to its pre-pull height and the first row renders crisply. Actual The region stays roughly one refresh-control height too tall and the first row stays blurred. Row positions are unaffected — content offset and adjustedContentInset are correct. Only the extent of the effect is wrong. It corrects itself on the next push/pop. Two probes that isolate it These narrow the cause to the control's presence rather than a general staleness: Re-assigning tableView.topEdgeEffect.style after endRefreshing(), including on a later runloop turn, does NOT correct the region. The style is not what is stale. Detaching the control DOES correct it immediately: tableView.refreshControl = nil So the region is measured from the control being in the hierarchy, and is never re-measured when the control merely collapses. Secondary issue A UIRefreshControl that has been detached is inert if the same instance is re-assigned: tableView.refreshControl = nil tableView.refreshControl = sameInstance // never triggers again A freshly constructed UIRefreshControl must be assigned instead. This is not documented and looks like a second bug. Minimal sample Attached. A UITableViewController with a refresh control and a "Push" bar button that pushes and pops an empty view controller, so the incorrect region and the post-navigation correction can be compared in one run. Related FB20756572 reports the same "edge-effect extent is stale until the next navigation" behaviour for UIScrollEdgeElementContainerInteraction sizing, and notes a change in iOS 27 seed 1. That report received no reply.

Environment: Xcode 27.0 beta 6, Device Hub, tvOS 27.0 When focusing a TextField and using Device Hub to run on tvOS 27.0, I cannot type any text into the field. Focus moves to the TextField as expected, but keyboard input is not received. Has anyone else run into this? Any workaround would be appreciated.

Hi everyone! Could anyone testing iPadOS 27.2 Beta 2 on an iPad please check a Display Zoom keyboard bug for me? When setting Display Zoom to Larger Text (Settings -> Display & Brightness -> Display Zoom), the spacebar becomes extremely small and squeezed between the language/layout switching keys. Just to add — this applies to both Developer Beta 2 and Public Beta . Thanks to anyone who can test this! Is this UI bug fixed in Beta 2? Thanks!

I’m building a SwiftUI app that fetches public JSON data using URLSession.shared. The request works correctly in the iPhone 17 Pro Max Simulator, but fails on my physical iPhone 16 Pro Max running iOS 27 beta. Endpoint: https://api.jolpi.ca/ergast/f1/2026/driverstandings.json?limit=100 Error: NSURLErrorDomain Code=-1009 “The Internet connection appears to be offline.” NWPath: unsatisfied (Denied over Wi-Fi interface) Resolved 0 endpoints in 1ms The device can access the endpoint through Safari, and the same request works in Simulator. VPN, cellular permissions, Wi-Fi changes, and ATS settings have been checked. Could this be an iOS 27 beta networking regression affecting URLSession on physical devices? Are there recommended workarounds or diagnostics?

What happens Since installing macOS 27.2 b2, the Contacts app has become almost unusable on my two Macs. Opening a contact or moving to the next one often freezes the app for 8 to 10 seconds, with the spinning wheel. It happens many times in a row while browsing the address book. It comes back no matter what I try: restarting, letting iCloud resync the contacts, deleting and recreating cards. Once, it seemed to go away after restarting, but it returned after a couple of minutes into using Contacts again. Both Macs share the same iCloud account (~690 contacts): a MacBook Pro M4 Pro and a Mac mini M4, both on 27.2 b2 (26B5091g). Reported as FB24928119. Technical details All 18 Contacts_*.spin reports show the main thread blocked in CNCDContactFetcher withLockedContext_fetchPosterData, waiting on a synchronous XPC call to com.apple.contacts.poster.api. That service is postersyncd, which syncs Contact Posters. The kernel kills postersyncd with exceeded mem limit: InactiveHard 20 MB (fatal) at 30–35 MB. launchd relaunches it every ~10 s: 74 kills in 26 h on one Mac, 54 in 24 h on the other. log stream --level debug shows the same sequence on every relaunch: START: Background cleanup → Potential cleanup for missingLocalContactIdentifiers → FetchingContacts → killed within the same second. The cleanup never finishes, so it restarts forever. The poster store (group.com.apple.contacts/ContactsMetadata) is ~85 MB, with blobs of up to 9 MB each. The memory limit stays InactiveHard even while Contacts is frontmost. Moving the poster store aside doesn't help: iCloud rebuilds it in ~25 s. Posters deleted from iOS or iCloud.com get a deletion date but are never purged. Question: Has anyone else seen this on 27.2 beta? Is there a way to reset the Contact Posters data stored in iCloud?

Hi everyone, I recently updated my Mac to macOS 27 Golden Gate Beta and have encountered a strange issue with window management over a remote connection. Issue: When connected to my Mac via Chrome Remote Desktop (CRD), I can no longer move application windows by dragging their title bars (outer frames). Details: Curiously, I can still drag and move individual tabs within apps (like Chrome or Terminal), which means mouse drag input itself is being transmitted correctly to the OS. This issue only happens when attempting to drag the window title bar/frame over a remote session. Local mouse/trackpad control works perfectly. Everything was working completely fine before the update to macOS 27 Golden Gate Beta. What I've tried so far (with no success): Toggled Accessibility permissions off and on for ChromeRemoteDesktopHost and restarted the Mac. Disallowed and re-allowed Screen Recording permissions. Completely re-installed the Chrome Remote Desktop host application. Disabled "Tile windows by dragging to screen edges" in System Settings to avoid snapping conflicts. It seems like WindowServer or the system-level window management is blocking or ignoring virtual mouse drag inputs specifically on title bars since this beta update. Has anyone else experienced this on macOS 27 Golden Gate Beta, or is there a known API change / security restriction in this version that affects remote input handling for WindowServer? Any insights or workarounds would be greatly appreciated. Thank you!

iPadOS更新到27后它的这个iPad Pro五代12.9英寸，也就是M1芯片的那一个，更新以后屏幕存在完全失灵，无法进行手势操控的bug，是我买了当年买了这个妙控键盘，所以现在就只能用那空键盘上面的触控板来操作，所以有人来帮我解决一下这个事

I'm stuck. I'm trying to install the beta of macOS 27 (Golden Gate) for testing. I have: Created a new APFS volume Installed a fresh copy of macOS 26.7 Booted new volume, created an account, and logged in using my developer account Followed the instructions for "Installing and using Apple Beta Software" (https://developer.apple.com/support/install-beta/#macos-beta), specifically Opened System Settings > General > Software Updates Clicked on Beta Updates (i) button But the only options it gives me are "Off" and "macOS 26 Developer Betas". There is no place to select "macOS 27 beta" It shows my developer account in the beta updates window. I've confirmed that my account is up-to-date. There's obviously some step I'm missing, but I don't know what.

I'm running the latest beta 27.2 (26B5086k) on a 2022 Mac Studio M1 Max, and I'm experiencing a new issue. I do a lot of writing, dictating, and reading, so I frequently use the text-to-speech feature. After the recent update, my shortcut for "Speak Selection" stopped working. I tried restarting the machine, but it still won't read the selected text. I also attempted to adjust the settings, but the system settings froze. Also its not even loading the controller. Any help getting this feature working again would be greatly appreciated!

For the life of me, I cannot find how to bring up the Siri Remote in the Apple TV Simulator in Xcode 27 Device Hub (Beta). Is it no longer available? I have always seem to have had issues using the computer's keyboard for navigating my tvOS apps. Maybe it's me, but the Siri Remote always worked perfectly fine. I hope the remote will make a reappearance in the next beta... ?

Hi everyone. I’m just an ordinary user with no programming knowledge—and certainly not a developer. I simply wanted to try out iOS 27 before the final public release. I logged into "Apple Developer" with my Apple ID, and now, it seems I’m stuck receiving developer versions on my device forever. My question is: Is it possible that Apple might soon allow Apple IDs that merely logged in—but never actually became developers—to stop receiving developer versions on their devices? It would be great if that happened. Thanks a lot.

Using iPad as sidecar for Mac, how to make full use of iPad keyboard? What I meant by that is, right now if I press Cmd+Tab or Cmd+Space for example, the shortcuts are intercepted by the iPad itself instead of passed to the Mac through sidecar. Can I turn off these iPad shortcuts while using sidecar somehow?

My phone no longer shows the waitlist for Siri and has the option to "Try New Siri." I select it, continue, continue and the settings change to "Siri (Beta)" and the waitlist option is no longer there, but when using Siri it's the old pre-Apple Intelligence Siri that activates (little bubble at the bottom) and it does not work. Going to Safari and typing "Siri://" opens the New Siri App, but it says "Siri Update in Progress; Adding support for Siri hasn't completed. Open Settings to check the status." The app does not show up in Spotlight. My phone is done Indexing and all signs point to my phone being enrolled to use the New Siri, but it isn't working at all and still has not shown up. I've tried restarting a few times. Anyone experiencing this too?

In Xcode's Settings → Intelligence section, there's no built-in AI agent/model available, only chat bots. I'm not able to download a model through the Components section as well, but no models are offered or downloadable there either. Environment: Xcode 26.6 and Xcode 27 beta 6 macOS 26.6.2 MacBook Pro (Apple M4 Pro)

Now that Apple has apparently removed the web interface from CUPS from MacOS27 (though there's no mention of it in the Release Notes); what is the sanctioned method of configuring print queues and setting their defaults? Have we got to use lpadmin and lpoptions? #progress

Hello, I am tracking a severe local networking regression on macOS Golden Gate 27.2 Developer Beta (build 26B5086k) running on MacBook Pro M4 Pro hardware. Despite negotiating a strong physical Wi-Fi connection with high PHY rates (1200+ Mbps) and excellent RSSI, actual throughput collapses dramatically and local gateway latency spikes uncontrollably whenever AWDL and AirDrop discovery are actively processing. Key Diagnostic Metrics Observed AWDL Manually Disabled: Executing sudo ifconfig awdl0 down completely drops packet loss to 0%, stabilizes gateway latency entirely, and restores baseline throughput. AirDrop Turned Off (AWDL Active): Disabling AirDrop via System Settings while keeping AWDL active stops the catastrophic latency spikes. This strongly suggests the trigger is linked directly to AirDrop's continuous background discovery/scanning activity rather than basic AWDL link states. Environment Isolation Performed Safe Mode: The issue persists cleanly while booted into macOS Safe Mode, ruling out third-party launch kexts, background daemons, or custom VPN software. Cross-AP Testing: The behavior follows the Mac across completely different access points, occurring on a dedicated Wi-Fi 7 home environment (tested across 5GHz and 6GHz channels) as well as an iPhone Personal Hotspot over cellular. Control Device: Same-location control testing with an iPhone shows perfect gigabit-class speeds, confirming the RF environment and network backhaul are perfectly healthy. I have already submitted a comprehensive sysdiagnose archive and wireless diagnostic log package directly to Apple. Feedback ID: FB24842970 Curious if anyone else with an M4 Pro on this build is seeing similar behavior. If this is happening on your end too, it might be worth submitting a bug report and referencing FB24842970 so Apple can group our logs together and look into a patch.

Hello, I found a difference in application lifecycle behavior between iPadOS 26.5 and iPadOS 27 beta when the app is running in the foreground and the iPad top button is pressed to put the device into sleep. Test condition Device: iPad App state: app is running in foreground (active) Action: press the top button once to put the device to sleep Observed via UIApplicationDelegate lifecycle callbacks Observed behavior iPadOS 26.5 The following callbacks are called in this order: applicationWillResignActive applicationDidEnterBackground iPadOS 27 beta The following callbacks are called in this order: applicationWillResignActive applicationDidBecomeActive applicationWillResignActive applicationDidEnterBackground Expected behavior I expected the lifecycle sequence on iPadOS 27 beta to be the same as, or at least consistent with, iPadOS 26.5 when the device is put to sleep from the foreground app state. In particular, I did not expect applicationDidBecomeActive to be called during the transition to sleep/background. Question Is this changed behavior expected in iPadOS 27 beta, or could this be a bug in the beta? If this is expected, could you clarify the intended lifecycle behavior when the top button is pressed and the device transitions to sleep? Thank you.

In iOS 26, the mini keyboard bar does not consistently appear when typing with a hardware keyboard. This behavior differs from iOS 18, where the bar was always visible. See screenshots:

I have a project that builds fine in macOS 26 with Xcode 26. On macOS 27 b4 and Xcode beta, the same project can't build because of a framework that should be pulled from a Swift Package from a package-registry (named Registry, for example below), hosted on JFrog. I have the registry set up and have the token in keychain. The resolution of the packages works. But when I build, I get error like this: error: Missing package product 'Registry.Package_Package.Package' (in target 'Target' from project 'Project') . The real package should just be 'Registry.Package'. Any help with that? Is it a bug?