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!

มั่นคง ยั่งยืน

This started happening on iOS 26.5, and it is still happening after updating to iOS 26.6 beta. The issue is severe enough that my Apple devices are currently not usable for basic communication. I have lost money, time, and thought way too much about this, so I’m really hoping for a resolution. After setting up an iPhone 14 Pro Max on my Apple Account/iCloud, my Contacts, Messages, Phone, and related Apple communication services became essentially nonfunctional. This started after adding the iPhone 14 Pro Max, but it is no longer isolated to that phone. The issue has spread across my Apple devices, including my iPhone 15 Pro Max, iPhone 14 Pro Max, iPad, and Mac. Current Affected devices/apps: iPhone 15 Pro Max iPhone 14 Pro Max iPad Pro Mac Mini M4 Contacts Messages Phone/calls FaceTime or other calling/contact-related services iCloud Contacts / Apple Account syncing The apps themselves become unusable. When I open Contacts, Messages, Phone, or related services, I usually get a blank/white screen, a frozen interface, or a briefly visible cached state. Sometimes I can see old message previews or the previous app state for a split second, especially after force restarting or using the app switcher, but I cannot scroll, select, call, text, or use the interface normally. After about 10 to 15 seconds, the app freezes or crashes. This affects essentially all normal communication functions. I cannot open Contacts. I cannot read or use Messages normally. I cannot place or answer calls. I cannot use my contact list. I cannot use any of my phone numbers or receive verification codes to my phone number. The same failure appears across devices signed into the same Apple Account/iCloud. Contacts still appear to exist on iCloud.com, which makes me think this may be an iCloud Contacts, Apple Account sync, contact-card corruption, or cross-device sync corruption issue rather than simply a local device problem. Troubleshooting already attempted: Updated to iOS 26.6 beta Factory reset the iPhone more than once Tried restoring from backup Tried setting up from zero / fresh setup Tried force restarting Tried resetting SIM/cellular settings Tried setting up with no SIM Confirmed accounts were logged in Confirmed mail/accounts were present and Contacts were enabled where applicable Contacted Apple Support Apple Support escalated the case to a senior engineer Apple Support diagnostics reportedly came back “fine” or “flying colors,” but the devices are still unusable Posted on Apple Support Community, but apple deleted my post and told me to post on the developer forum because I mentioned I updated to iOS 26.6 is beta software.... One possible thing: before this started, I had an AI agent attempt to update my personal contact card with a new phone number. This is an operation that normally goes well, but it was my personal card. I did not verify exactly what it changed. I do not know if this is related, but I am mentioning it because the issue feels like something corrupted in the Apple Account/iCloud contact or identity layer, and somebody in my last thread mentioned emoji or unusual characters might cause this kind of issue. It might have changed my card with some unusual character, field, label, or operation that broke iCloud syncing. Another clue: this started after adding the iPhone 14 Pro Max to my Apple Account/iCloud. After that, the issue began affecting the rest of my Apple devices too. That is why I believe this belongs under iCloud / Apple Account / Contacts syncing rather than only iPhone.

Dear Apple Developer App Review Team, I hope you are doing well. I would like to clarify the nature of my application before publishing it on the App Store to ensure full compliance with Apple’s guidelines and policies. My application, called “Dukhan”, is a platform dedicated to cafés in Iraq. Its primary purpose is to help users: Discover nearby cafés. View café information and menus. Explore promotions and special offers provided by café owners. Improve the overall experience of finding and visiting cafés. The application is not intended to sell tobacco products or directly promote tobacco-related sales. Additionally, the app does not include any functionality for purchasing or delivering tobacco or nicotine products. However, due to the nature of café culture in Iraq and the surrounding region, some cafés may display images within their menus or venue galleries that include hookahs/shishas, as these are commonly associated with local cafés. These images are uploaded by café owners solely to showcase the atmosphere and available services of their cafés, not for the purpose of selling tobacco products through the application. We are fully willing to comply with any additional requirements from Apple, including: Prohibiting any direct sale or ordering of tobacco products within the app. Applying age restrictions if necessary. Removing any content that may be considered direct tobacco promotion. Moderating uploaded content from café owners to ensure compliance with App Store guidelines. I am also fully willing to provide screenshots, demo access, or even submit the application for review in order to help your team better understand the app’s purpose and functionality. We would appreciate your guidance on whether this type of content is acceptable within the context of a local café discovery and service platform, especially since the app’s focus is on helping users discover cafés and their services rather than facilitating tobacco commerce. Thank you for your time and consideration. Kind regards, Murtada Dukhan App

I can't send text messages from my MacBook Air (Tahoe 26.6) to Android phones. This just happened this week, after successfully being able to send them since purchasing this laptop (2023 - M2 chip). I've checked the settings to make sure that my iPhone and my laptop are signed into iCloud (they are), and that I have message forwarding set up on my iPhone. I can get texts on my laptop from Android users, but I can't reply - the texts fail every time. I've searched the community for an answer, and have tried previously suggested fixes to no avail. Any thoughts?

Hi all, Hoping someone has hit and resolved this exact pattern, or can point me to the right escalation path. I'm trying to enrol in the Apple Developer Program as an Individual (Bengaluru, India). The Apple Developer iOS app shows "ID Verification Rejected" under the Apple Developer Program status — but with no specific reason and no retry button. The app does not surface what was actually wrong with the verification. What I have already done: Confirmed my Apple Account name ("Adarsh P S") exactly matches my Passport and PAN card (no extra spaces, correct initials). Opened Developer Support case #102900128848 — the agent replied once on 2026-05-28 asking for a screenshot, which I provided the same day. No follow-up in 3+ business days. Filed a parallel case #102905434551 on 2026-06-02 explicitly referencing the first as escalation, not a duplicate. Apple ID has 2FA enabled, trusted device active, billing address on file. Questions for anyone who has gotten past this: Did the verification reset come from support, or did re-attempting from the app after some delay work on its own? For Indian developers — which ID type was finally accepted (Passport vs PAN)? I understand Aadhaar is not accepted per UIDAI restriction. Is there a specific support topic / contact path that routes to the identity-verification team faster than "Membership and Account → Program Enrolment → Email"? Any pointers appreciated — my iOS 26 / SwiftUI app is built, tested, CI-green, and waiting only on enrolment. Thanks, Adarsh P S

I’m using an Apple M4 iMac on macOS Tahoe 26.6 Beta and an iPhone 16 Pro Max on iOS 26.5. After updating, my iPhone 16 Pro Max no longer appears under iPhone Mirroring settings, and both iPhone Mirroring and AirDrop stopped working from my primary macOS account. The strange part: Apple Support had me create a new macOS user account, and everything worked immediately there. The iPhone appeared correctly, Mirroring worked, and AirDrop worked. When I switch back to my primary account, the iPhone disappears again and neither feature works. My primary account still works normally with my iPad Air M3 and iPhone 12 Pro, so the issue seems specific to the iPhone 16 Pro Max and my original macOS profile. Has anyone else seen this issue or found a fix?

Hi all, I'm hitting a wall trying to enroll my personal Apple ID in the Apple Developer Program. My company Apple ID has been enrolled and active in the program for over a year. I now want to enroll my personal account as well so I can ship side projects under my own name. Both accounts belong to me. Both use the same iPhone, mac and the same phone number for 2FA. I'm not trying to run both signed in simultaneously, I just want both Apple IDs enrolled so I can switch between them when needed. Every time I try to enroll the personal account, it's rejected. The rejection doesn't give a specific reason (Your enrollment could not be completed.), but I'm fairly sure the conflict is around the shared phone number or device. I've reached out to Developer Support but haven't had luck getting through: Email support: over 10 days with no reply on my ticket Phone support: on hold for 3 hours before the call dropped automatically Posting here in case someone has been through the same setup. Specifically: Has anyone successfully enrolled two Apple IDs in the Developer Program where both accounts belong to the same person on the same device? Is the shared phone number actually the blocker, or could it be something else? Is there a recommended way to escalate Developer Support when tickets go unanswered? Any pointers appreciated.

I will be in Beijing on a tour overlapping with the last 3 days of WWDC. There are likely to be at least a couple of 1-1 labs I'd like to attend as well as group forum sessions. I suddenly had the horrified thought that the Great China Firewall may interfere with either of these. Does anyone know how likely this is? Does the Developer app work there? Will be in a reasonable hotel and have Vodafone roaming on my phone. thanks

Hi, I am unable to enroll to the Apple Developer Program. After submitting my basic information a messaged appears stating "Your enrollment in the Apple Developer Program could not be completed at this time." Please help me. Thank you, The World Simpler

I have received this installation error attempting to upgrade from MacOS 26.4 beta 2 to beta 3 on my Intel 2020 27” iMac, and now trying to install beta 4 from beta 3 on my M1 Max MBP. I have seen from a sprinkling of post that some others have had the same issue. I was able to successfully perform the 2 to 3 upgrade on the iMac in safe boot, suggesting possible compatible, third-party app. But that did not work for beta 4 on either device. I have submitted feedback for each episode. Any others have this issue? Unusual for Apple, I have never had any issues installing beta software before.

I applied for the Apple Developer Program on January 31, 2026, and as of today (February 5, 2026), my enrollment is still showing as Pending. The payment was completed successfully at the time of application. Since then: I have not received any requests for additional documents or verification. I have contacted Apple Developer Support twice, but have not received any response so far. I understand processing times can vary, but the lack of response from support is concerning. Has anyone else experienced similar delays recently? Is there any recommended escalation path or alternative way to reach the Developer Support team? Any guidance would be greatly appreciated, as this delay is impacting my app release timeline. Thank you.

I dont understand why it is so hard to develop an app on the Apple Watch. The watch never stays connected. The song and dance is just stupid: Go to Settings on the watch Tap on Privacy & Security Scroll down to Developer Mode Toggle developer mode off then on Tap on Restart After watch restarts Enter your pin Turn on Developer Mode Trust your dev laptop Enter your pin again Hope your watch connects Which works most of the time. If it doesnt restart XCode. Why cant Apple fix this?

I have the issue with simply trying to ssh to any other host on the LAN since Tahoe 26.5. last entries from ssh -v answer are debug1: Host 'answer' is known and matches the ED25519 host key. debug1: Found key in /Users/dgerman/.ssh/known_hosts:5 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1: kex_ext_info_client_parse: server-sig-algs= debug1: kex_ext_info_check_ver: publickey-hostbound (AT) openssh.com=<0> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey No problem from older MacBooks This worked before the update.

Hello, I am trying to enroll in the Apple Developer Program, but I cannot complete the payment. During the purchase process, I receive the following error: We are unable to complete your order. There was an issue when we processed your order. An invalid value '1549' was provided for State, Province, or Region. My details: Country: Kosovo State/Province/Region: Kosovo Region (selected from the available option) I have verified my information multiple times, but the error appears every time. I have contacted Apple Developer Support multiple times over the past month.I have not received any response (positive or negative). I need to complete enrollment to publish my apps, and this delay is blocking my work.

I am a huge techie person. I love programming, Macs and PC. my all of my codebase and projects use open source software. I am also been a fan of the environment. With the changes in climate in the past and lately I have been moderately conservative on my tech purchases. Because of this I have a pulsing question on what is Apple's end game for EOL Apple silicon? I mean if you look at the power packed Apple Silicon Macs and its enclosure it looks environmentally friendly, recyclable and sustainable. The enclosure is recyclable. the hardware interface looks minimal to the sense that the waste is just the PCB that the interface is laid out on. Think of the current iPhone it looks really recyclable and sustainable. But because I changed drastically and the price of tech right now is not buyable or viable to me I would like to ask what is Apple's end game on EOL Apple Silicon Macs. Price and sustainability? I am an avid watcher of current recycling break throughs and believe me it gave me solutions not just recycling but it also gave me a mission. The primary solution I want to solve and ask you guys if is there effort to put OpenBSD on apple silicon? I like Linux on my x86 machine but for Apple Silicon since it is unix based I want to work on BSD based projects. Any input from Apple developers out there would be nice. I just to find a way to repurpose Apple Silicon Macs because its has a great hardware and from the looks of it I would like to keep it and run it with an OS close to macOS. Please put your input. I/O peace out.

Videos recorded on older iOS versions (including beta builds) play choppily in the Photos gallery preview layer, appearing to drop frames or have incorrect frame pacing. The same video plays perfectly smoothly when opened in Edit mode, and also plays smoothly after trimming even 1 frame and saving as a new clip — suggesting the source file is intact. The issue appears to be stale or incompatible preview proxy data / frame timing metadata (likely elst/ctts box mismatches) generated by older or beta AVFoundation versions, which the current PLPlaybackView fast-path renderer cannot handle correctly — while the full AVAsset decoder used in Edit mode tolerates these gracefully. No workaround exists to bulk-rebuild video proxies on iOS without manually trimming each clip. A “Rebuild Video Previews” option (similar to the Mac Photos library repair tool) would resolve this globally. Steps to reproduce: Open any video recorded on iOS 16 beta or earlier in the Photos gallery. Observe stuttering. Open same video in Edit mode — stuttering gone. Trim 1 frame, save — new clip plays smoothly in gallery too. Expected: Gallery preview plays at the same smoothness as Edit mode. Actual: Gallery preview stutters; Edit mode is smooth. HDR off. Most Compatible format enabled. Issue persists after reboot.