I have a question about the operating procedure of the iPhone defaulting into satellite service. Post major storm we noticed that my phones would not allow us to connect to the satellite backup communication because the iPhone was still getting intermittent cell service even though the service that they were receiving via tower signal was that of the tower that had no connectivity (the individual cell tower may have been producing cell SIGNAL, but their ability to transfer data threw microwave or landline was terminated ). Previously, I asked if they could find a fix so that even if the phone is receiving what it is some or very little signal, you could opted to defer to settle in a situation such as this. When left in it’s current programming the phone will not make contact with either communication source leading it to be useless.

I recently updated iOS 26 beta and now my SingPass keeps crashing when I tried to open it. can I revert back to iOS 18?

Hi all, I’m running into a persistent build issue with my Swift project ORSOFINAL after migrating from Xcode stable to Xcode-beta.app (June 2025 version). ⸻ 💥 Errors displayed: 1. C99 was enabled in PCH file but is currently disabled 2. module file .../ModuleCache.noindex/SwiftShims-AXUM98L131W4...pcm cannot be loaded due to a configuration mismatch with the current compilation 3. missing required module 'SwiftShims' ⸻ 🛠 What I’ve already tried: • xcode-select -s /Applications/Xcode-beta.app/Contents/Developer • Deleted ~/Library/Developer/Xcode/DerivedData, ModuleCache.noindex, Archives, and Products • Ran sudo xcodebuild -runFirstLaunch • Clean Build Folder in Xcode-beta • Verified Command Line Tools setting points to Xcode-beta ⸻ ❓Looking for guidance on: • Whether this is a known bug in Xcode-beta • If SwiftShims/PCM conflicts are expected between versions • Best practices to safely migrate from Xcode stable to beta for Swift-based projects Any advice is much appreciated. Thanks, Mathéo

On recent versions of macOS (including current betas), when enabling Internet Sharing from Ethernet to Wi-Fi, the configured WPA2/WPA3 password is ignored and the shared network is broadcast as an open (unsecured) network. Steps to Reproduce: Connect Mac to Ethernet via USB/LAN adapter Go to System Settings > General > Sharing > Internet Sharing Set up Wi-Fi options with a valid WPA2/WPA3 password Enable Internet Sharing Expected Behavior: Devices should see a password-protected Wi-Fi network with a lock icon and require authentication. Actual Behavior: The network appears unsecured (no lock icon) Devices like iPhone connect without entering a password This can be verified immediately from iOS Wi-Fi settings Additional Notes: Reproducible across macOS 15.5 RC and 16.0,26.0 Developer Beta Feedback has been submitted via Feedback Assistant multiple times This is a serious security risk if used in public or shared environments Has anyone else experienced this? Any known workarounds besides terminal-level defaults or Plist edits? Thanks in advance!

Hello, is it anyone here ( or on this planet ) that can help with this issue on Catalina Mac OS 10.15.5 Beta 3 (19F72f).I am using MacBook Pro 16 inches. 😟

Hi everyone, I updated my iPhone 16 Pro to iOS 26 beta and my Apple Watch to watchOS 26 beta because I wanted to test out the new features. After a few days of testing, I found the iOS 26 beta too unstable and laggy for daily use, so I downgraded my iPhone back to iOS 18.5 stable. Now my Apple Watch is still running watchOS 26 beta. I tried resetting it to factory settings, hoping that would help, but now I can’t pair it back to my iPhone because it requires iOS 26 again — which I don’t want to reinstall and don't want to use it till it's stable. Is there any way to downgrade my Apple Watch back to a stable version or somehow pair it again with my iPhone running iOS 18.5? Thanks in advance for any help!

An error occurred while checking for a software update after the iOS 26 update. Is anyone else facing a similar issue?

Please expedite to Solve this bug , my Singpass is unable to launch in iOS 26. I believe this is more urgent than a new pride theme wallpaper 🏳️‍🌈

Right now, Apple’s iCloud Keychain (where saved passwords are stored) relies on the same authentication methods as your iPhone in general: Face ID or device passcode. This means: • If Face ID fails, it falls back to the device passcode. • Anyone with your passcode can unlock not only your phone but also your saved passwords by allowing the phone to go into the “enter iPhone password to view passwords” on the password app. Why this matters if someone knows or coerces your device passcode, they could potentially: • Bypass Face ID • Access sensitive password data • Compromise multiple accounts and could access all passwords I have saved on the password app. So, Let’s say my girlfriend knows my phone passcode, she pretty much then has access to all other password and backup codes I have saved on the password app. For this security vulnerability I believe it would be beneficial to introduce more advanced security options for accessing the Password section on iPhone. Specifically, 1. The ability to require Face ID only, without fallback to device passcode. 2. An option to set a dedicated password just for accessing the Passwords section (separate from the phone passcode). 3. Additional optional layers of protection, such as two-factor authentication or a biometric lock, that would prevent access even if someone knows the device passcode. These features would provide an extra level of security for users who are concerned about unauthorized access if someone gains access to their phone passcode.

Hello all, We are in the process of deploying EAP-TLS Wi-Fi authentication across our corporate environment for both Windows and macOS devices. All endpoints are managed via Workspace ONE. As part of our macOS configuration, we are pushing device certificates to the login keychain of managed MacBooks. For testing purposes, we have explicitly set the Access Control List (ACL) of the associated private key to allow all applications access. This includes: eapolclient, which handles the EAP-TLS handshake for Wi-Fi panGPS, which is responsible for establishing the GlobalProtect VPN connection (we are using certificate-based authentication with pre-logon enabled) Additionally, we have configured and deployed a Wi-Fi profile via Workspace ONE to prevent users from having to manually select their device certificate - basically the identity preference card in Keychain Access. Despite these settings, we are still encountering Keychain Access prompts when eapolclient attempts to access the private key. This happens even though the key is configured to allow all applications access. This behavior is unexpected, and we’re trying to understand why these prompts persist. Has anyone encountered similar behavior on macOS, or is there something we're missing in terms of permissions or keychain configuration that could be causing this? We would greatly appreciate any insight or guidance. Thank you, Kyo

Hey, I cant can update or downgrade to a newer Version like IOS18.5 Can someone help me? And will Apple fix that?

Dear Apple: If a BLE advertisement carries both a 16-bit service UUIDs and a 128-bit service UUIDs along with a local name, the local name will be placed in the scan response, then when the advertisement is turned off, both the 16-bit and 128-bit service UUIDs disappear while the local name persists. Subsequently, when transmitting a new advertisement that includes the 16-bit service UUIDs and local name, the resulting advertisement contains two local names. What methods can be used to avoid having two local names appearing simultaneously?Thanks

i have a specific requirement as below. i have apartments in which i have 4 units and each unit will be of same layout. furniture etc.. might change but not walls and layout as far as i know. Step1: Now i will enter into one unit, scan the entire unit and save it using RoomPlan Api and at the end of the scan i will be saving the worldmap as well. Step2: i want to use the previously saved worldmap and enter into another unit and want to relocalize with only walls because the furniture might be different. is that possible. if not is there any otherway to achieve this functionality? i really appreciate you valuable time. Thankyou.

System: OS: macOS 15.5 CPU: (10) arm64 Apple M1 Pro Memory: 82.02 MB / 16.00 GB Shell: 5.9 - /bin/zsh` IDEs: Xcode: 16.1/16B40 - /usr/bin/xcodebuild Managers: CocoaPods: 1.15.2 - /Users/liuxiwei/.rvm/gems/ruby-3.3.5/bin/pod SDKs: iOS SDK: Platforms: DriverKit 24.1, iOS 18.1, macOS 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1 Android SDK: Not Found i use react-native to build ios app . when archive than it happens: ld: Assertion failed: (it != _dylibToOrdinal.end()), function dylibToOrdinal, file OutputFile.cpp, line 5184.

After updating to iPad iOS26 , the software update area shows that it cannot check for updates. Is this normal?

Hey everyone, I've got a feature suggestion for iOS that I believe would significantly benefit users by optimizing battery life and data usage through more intelligent Wi-Fi prioritization. While iOS already favors Wi-Fi over cellular when available (due to its lower power consumption), there's room to enhance this behavior with more granular user control. My proposal is to introduce an explicit option: "Prioritize Wi-Fi for Energy Saving." How It Could Work Global Toggle (Settings > Wi-Fi or Settings > Battery): A simple switch that makes the iPhone more "aggressive" in maintaining a Wi-Fi connection. When active, it would reduce the likelihood of switching to cellular data during minor Wi-Fi signal fluctuations. This ensures the device stays on the more energy-efficient Wi-Fi network for longer periods, even if cellular signal is strong. This could also subtly influence Wi-Fi Assist, making it less eager to use cellular when Wi-Fi is slightly weak but still usable, prioritizing energy savings. Per-Network Option (Settings > Wi-Fi > [Network Name] > "i" icon): Adding an option like "Prioritize This Network for Energy Saving" within individual Wi-Fi network settings. This would be perfect for trusted networks like home or work, where users want to ensure maximum battery life. The iPhone would then make an extra effort to remain connected to that specific Wi-Fi network. Integration with Low Power Mode: For seamless optimization, this feature could automatically be enabled or its behavior enhanced when Low Power Mode is active, aligning perfectly with the goal of battery conservation. Key Benefits Extended Battery Life: By consistently favoring the more energy-efficient Wi-Fi radio, we minimize cellular power draw. Reduced Cellular Data Use: Helps prevent accidental or unnecessary shifts to cellular data, saving precious megabytes. Greater User Control: Gives users who prioritize battery longevity and data limits a direct tool to fine-tune their device's network behavior. This feature would be a valuable enhancement to iOS, offering users more control and a genuinely optimized experience.

I don't know if this is the right place to raise this, so apologies if not. For years now, I have exported an NFS share from a host Mac which I connect to from a Raspberry Pi on the same network. I configure this by adding a line in /etc/exports - /Users/Pi -mapall=myusername This has always worked flawlessly, but since updating my Mac (M4 Mac Mini) to Sequoia 15.5 last week, it has developed a problem. If the NFS share is not accessed from the Pi for five minutes, it dies, and the Pi's file manager locks up necessitating a complete reboot. If I run a script on the PI which does an ls on the mounted share every 5 minutes, the lockup does not happen. But if I extend the period to 6 minutes, the lockup occurs. Something on the Mac NFS server seems to be dying in an unrecoverable fashion after five minutes of idle. Even with nfsd logging set to verbose, there is nothing helpful in the console logs. I am open to suggestions to further investigate or to try and fix this, but this is basically a showstopper for me - I need to be able to share data between Mac and Pi, and this is now broken.

Hey there, Just writing here to say how I do enjoy the latest update, but I can’t seem to run it on my iPhone 14 Pro well because it tends to overheat. i can deal with the stuttering issues and app crashes, that’s understandable, but for some reason the hardware seem to really heat up after normal use (scrolling on social media platforms). oh also, I do think rolling back your phone‘s software should be a simpler process as well. It’s not impossible, but the demand of a computer in reinstating a previous backup when iCloud backups your device through WiFi seems like a missed opportunity. Okay. Thank you for reading.

I have created an app and for the final stage i added subscription feature. This works great in testflight, but not when i push out to external testers. I set up what i needed to in apple store connect (i must have done it right as it works in testflight), and i linked it to th emost recent version. Nothing I do seems to get the sub info to display and pull through to the app in the sub box when selected. No price and the usual stuff. I was told send for review. Failed the review and im working on that but something tell sme this is a glitch athat needs fixed on my account maybe. Can anyone help please

Hello Apple Developer Community, I'm encountering a persistent issue while attempting to create a new partition on my Mac, and I'm hoping to get some assistance or insights from anyone who might have faced a similar problem. Issue Description: I'm trying to partition my internal drive. I initially used Disk Utility.app for this purpose. The partitioning process starts, but consistently freezes when it reaches approximately 10-20% completion. I've left it running overnight (for over 9 hours), but there was no progress, and the application remained unresponsive at that percentage. After several attempts with Disk Utility, I decided to try using the diskutil commands in Terminal to see if that would yield a different result. I used commands such as diskutil apfs resizeContainer and diskutil partitionDisk. Unfortunately, these commands also result in the same behavior: the process starts, reports progress up to about 10-20%, and then completely freezes without any further output or completion, requiring me to force-quit Terminal. Mac Model: Apple M4 Pro MacOS Version: Sequoia 15.6