I think Apple should reconsider adding the 2018 iPad Pro to the iPadOS 27 compatibility list. The bigger issue here is that iPadOS 26 has become the final major OS version for the 2018 iPad Pro. That is a very disappointing end point for a Pro device, because iPadOS 26 has widely been perceived as one of the heavier, less stable, and less responsive iPadOS releases in recent years. This feels like a missed opportunity when considering that iPadOS 27 is mainly focused on refinement, performance, responsiveness, and stability. Excluding the 2018 iPad Pro means this model misses precisely the update that would matter most for its long-term usability. All the main features for iPadOS 27 have been about Apple Intelligence which is not compatible with this device anyways, so what we are missing from these A12X iPads is just the performance improvements (which is what it really needs!) The gap between the 2018 and 2020 iPad Pro models also makes the cutoff feel arbitrary. The 2020 models are supported by iPadOS 27, even though the real-world difference between A12X and A12Z is relatively modest compared with the later transition to M-series iPads. For a high-end Pro device that still feels physically and functionally modern, iPadOS 26 would be a poor final software version. I hope Apple reconsiders and gives the 2018 iPad Pro one more refinement-focused release.

itle NSPersistentCloudKitContainer sharing with relational Core Data graph fails with 134060 multi-zone corruption Post I’m looking for guidance from Apple or other developers on the supported limits of NSPersistentCloudKitContainer sharing for relational Core Data graphs. My app uses Core Data + CloudKit sharing with graphs like: Athlete -> Performance -> Compevents -> CompEventsSplits and Athlete -> NewYtp -> AthPlans -> PlanWeekRow The failure mode I keep hitting is: • export fails with NSCocoaErrorDomain Code=134060 • failure reason says related objects are assigned to multiple zones • after that, I may also see Zone Not Found, history-analysis corruption, and reset/recovery that still leaves the mirrored store unusable This seems to happen once one logical graph is effectively spread across multiple CloudKit share zones. Questions: Is this an expected limitation of Core Data + CloudKit sharing for related object graphs? Is there a supported pattern to guarantee one logical graph remains in one share zone? Once 134060 multi-zone corruption occurs, is there any supported recovery path besides resetting the mirrored store? For complex shared relational app data, is NSPersistentCloudKitContainer still the recommended approach? I’m mainly trying to understand whether this is: • a bug • a design limitation • or expected behavior with a required architectural constraint If Apple engineering has guidance on the supported boundary here, I’d appreciate it.

Didn't know these would be published on the Apple Developer YouTube channel, these are great if you have scheduling conflicts in attending live. Thanks dev team!

Title: Developer Beta option missing from Beta Updates settings Device: iPhone 16 Pro Software Version: iOS 27 Developer Beta 1 (24A5355q) Description: After installing iOS 27 Developer Beta 1 and confirming that my Apple Account is registered for developer beta access, the “Developer Beta” option is completely missing from the Beta Updates settings page. Observed issues: The Beta Updates page only displays “Off”. The “Developer Beta” option does not appear. Re-registering the Apple Account did not resolve the issue. The device is already running a Developer Beta build. The issue creates confusion regarding beta enrollment status and future beta update availability. Expected behavior: The Beta Updates page should display the “Developer Beta” option for eligible developer accounts. Actual behavior: The “Developer Beta” option is missing entirely. Impact: Users may be unable to verify their beta enrollment status or manage future beta update preferences correctly. Reproducibility: Occurs every time the Beta Updates page is opened.

Hello Apple, I have been facing an issue with charging, although I have beta updates off, but I faced an issue that in my opinion should show pulsing Amber on MagSafe, like I mentioned in my other thread. The MagSafe was glowing amber. Ok, can’t be on 80% yet. I opened the lid, and I found something I never expected: Although it was supposed to stop on 80%, it continued to 94% with no user notification. This happens every once in a while, but isn’t extremely rare. Last time this happened was about a week after macOS 26.5 was launched. I was running macOS 26.5 when this occurred Please consider this as an issue that needs to be fixed, and one of the ways is the MagSafe update, so the user at least knows something is wrong in case something like this ever happens. Please ask me for more information regarding this issue if needed. I am ready to mark the other post as answered if this gets a good reply, and keep in mind that I am conscious of what im doing, so please give this a good read and reply. Please do not count this as spam, I am only doing this to get it fixed, it may seem like a never reported before issue, but it’s still a real one. I am sorry that my previous replies on the forums were useless, and I promise to not reply to posts I don’t know about anymore. I am not a trained developer, and I hope you accept the apology. Thanks, Alyaman

When I open up the mail app, my memory usage for the app starts at 2gb then 4gb then 29gb then 49gb before my computer freezes and is asking me to force quit.

"My iPhone's battery health reading seems off. Even though it says 80% health, it instantly drops from 40% to 1%. The charge cycle count is already at 903."♻️

Can we please Have a Require Touch ID to unlock Certain App on Mac OS 27.

Working system and good experience for smoothly, working and lunch lunch apps for fast and iOS 27. Big update comparison on other updates. fast & optimise UI iOS 27. Siri intelligence add new features for accessibility, that’s good. but network connectivity is currently slow for 5G 4G. This is better this network, please network connectivity optimised. and focus network connectivity to stand line networks. or thank you so much.

After I enabled Enhanced Beta Feedback in Privacy setting, several minutes later when I came back, it was turned off… I don’t know why… This happened many times. Anyone encountered the same issue?

Can you give my redeem code to my testflight

I’m not able to upload the photo but I hope you understand

Shadow of Control center stays for a while before disappearing, visible in dark mode.

Hey everyone, It’s very early in the Beta 1 cycle, but I wanted to see what other issues people are running into with macOS 27 Golden Gate. The only notable problem I’ve hit so far is the Safari sidebar bookmark editing - right-clicking and choosing “Rename” or “Edit Address...” does nothing (known issue in the release notes, Radar 177470803). On my M5 MacBook Pro, the beta otherwise feels pretty stable so far. Has anyone else encountered any bugs or regressions worth reporting? Thanks!

User might be caught in a Guided Access page with error like this when they trying to leave Guided Access. Please pardon me for shotting a photo with phone to show this condition, because I can't even get a screenshot with home button and power key pressed together. I can't lock the screen with power key or by the magnet sensor, can't get back home page with home button. The ways to exit is waiting for the exit button might could use, or the screen shutdown, or enforce the device to shutdown. After exit the Guided Access without rebooting the system, the Guided Access would be freezed for minutes, noticing the Guided Access can't be used. In iPadOS 26, since, I can prove confidently, 26.5beta1 even earlier, could discover that issue. The problem could happen several times in a day. I have raised that issue since April 25th and the ID is FB22608734, which has more than 10 similar reports. To say something beyond the issue, actually I guessed that my device, iPad mini 5th, might can't get the update of iPadOS 27, so I hoped that Apple Developer Teams could at least fix those annoying problems. Actually there is a long list in Chinese with problems summarised by some Chinese User I waited for a long time for a miracle in WWDC 27. But that's a miracle.

Why for it is

After MacOS 26.6 Beta (25G5028f), I see my hard drive constantly filling up in the system data area. It's not local snapshots because I deleted those and they only took up about 20 GB worth of space. This morning, the hard drive was down to only 500MB of space. The odd thing is if I reboot, it goes back to normal and I am back to around 250GB or my 500GB drive. This only started happened in 26.6 Beta, so I am thinking there is an issue with that update?

iphone 16 promax. software ios 26.6 public beta. no matter how long i take screen recoding, the video in photo will be 2 seconds. i have found this bug for a long time and hasn't been fixed

Mac: MacBook Pro 16-inch (Intel, 2019) macOS: Tahoe 26.5.1 I'm trying to determine whether this is expected behavior or a bug. Setup I purchased a new 2TB SSD to use exclusively for Time Machine. Before configuring Time Machine, I manually erased the SSD in Disk Utility and formatted it as: APFS (non-case-sensitive) Encrypted I specifically did not choose APFS (Case-sensitive). What happened After selecting the SSD as a Time Machine destination and allowing macOS to prepare the disk, I later checked the volume information and found: File System Personality: Case-sensitive APFS and: APFS Volume Disk (Role): Backup Name: Brad Mac Backups SSD (Case-sensitive) The volume appears to have been converted to a dedicated APFS Backup volume and is now reported as case-sensitive. Additional observations After backups complete: tmutil status reports: Running = 0 indicating Time Machine is no longer running. However, Spotlight processes (mds and mds_store) continue accessing the backup volume for many hours afterwards, preventing normal ejection of the SSD. Using: sudo lsof | grep "/Volumes/Brad Mac Backups SSD" shows Spotlight processes holding the drive open. Finder's "Force Eject" works successfully. Questions Is it expected behavior in macOS Tahoe for Time Machine to create a Case-sensitive APFS Backup volume, even when the destination was originally formatted as standard APFS? Has anyone else observed a Time Machine destination changing from APFS (non-case-sensitive) to APFS (Case-sensitive) during setup? Could the case-sensitive APFS format be related to Spotlight continuously indexing the backup volume and preventing normal ejection? Relevant Output diskutil info disk3s2 returns: File System Personality: Case-sensitive APFS and: diskutil apfs list shows: APFS Volume Disk (Role): Backup Name: Brad Mac Backups SSD (Case-sensitive) Mount Point: /Volumes/Brad Mac Backups SSD 1 Any insight would be appreciated, as Apple Support was unable to explain why the backup volume became case-sensitive.

Hi everyone, I am running into a critical issue while trying to set up TestFlight / manage builds via the App Store Connect API. The system constantly throws an HTTP 422 error with the following payload: { "errors" : [ { "id" : "d7e4e2fa-8c25-4a37-9695-f75da935b8aa", "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Important context about my setup: This is a brand new Apple Developer account. This app has never had a successful build uploaded or processed before. All agreements, banking, and tax contracts under the "Business" section are active and signed. There are no pending actions on my dashboard. It seems like the system is looking for a "Beta Contract" that should be automatically generated or triggered, but since this is the first deployment on a new account, it’s completely stuck. Has anyone experienced this specific issue with a new account? Is there any way to manually trigger the creation of this Beta contract, or is escalating this to Apple Engineering the only solution? Any advice would be greatly appreciated!