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.

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.

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.

HiIm currently on iOS 11 Beta 2 (Build 15A5304i) With Update 1 Build 15A5304j just been released, will there be any difference since last weeks release?I can't update OTA to the new build released today.ThanksBarry

I am writing to report a significant battery drain issue after updating my Apple Watch SE (2nd generation) to watchOS 26.0 beta. Since the update, my watch’s battery life has drastically decreased: it goes from 100% to 0% in just 6 hours, whereas previously, under my typical usage, a single charge would last about 1.5 days. I have already tried the following troubleshooting steps without success: 1. Performed a fresh reset of the watch. 2. Reset my iPhone. 3. Disabled background app activity. 4. Enabled airplane mode and power saving mode. 5. Disabled Live Activities and Photo Memories Despite these measures, the issue persists. The battery health of my watch is at 90%, so I believe this is likely related to the software update. I am quite concerned about this situation. I have researched and noticed that similar battery drain problems were reported by beta testers of watchOS 11, and unfortunately, there appeared to be no clear resolution at that time. I rely on my Apple Watch daily, and I sincerely hope this can be addressed soon. I would appreciate your assistance in resolving this issue, as it is significantly affecting the usability of my Apple Watch. Thank you for your attention to this matter.

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.

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

Installed update on Monday night and since then keep losing Network connection despite resettting Network connections and iphone. Comes back for a short time after rsetting then is lost with nothing showing under Mobile Service.

After upgrading to iOS system 26, the local name broadcast type is 08, but before upgrading, it is 09 and will be included in the scan resp message; In version 26, the scan resp will also include Manufacturer Specific Data. Before the upgrade, the broadcast message may not necessarily include Manufacturer Specific Data; What I want to ask is, are there any restrictions on Bluetooth broadcasting in version 26? Is it necessary to include Manufacturer Specific Data data? If Manufacturer Specific Data data is included, it may cause fields in the local name broadcast to be truncated and use simple names of type 08

When I startAdvertising, my localName is long，Will not be truncated and the type is 0X09; self.advertisementData = @{CBAdvertisementDataLocalNameKey: localDevName, CBAdvertisementDataServiceUUIDsKey: @[[CBUUID UUIDWithString:serviceUUID]] }; [self.peripheralManager startAdvertising:self.advertisementData]; IOS 18.5: The service uuids in ADV_IND occupies 24 bytes, the local name in SCAN_RESP is 20 bytes in size and has not been truncated, and there is no manufacturer specific data in SCAN_RESP;You can view the following image： But in IOS26, why is the local name truncated to only 6 bytes for the same message, and why does SCAN_RESP always contain Manufacturer Specific Data; Why is there such a big difference, and what changes has iOS 26 made for broadcasting? Is it necessary to include Manufacturer Specific Data in the IOS 26 SCAN.RESP message? What documents are available for reference? Is there any way to ensure that the local name is not truncated? Is there a maximum length limit Are there other ways to broadcast longer data? Does anyone know why? thank

I am trying to connect to a google worksheet with a service account and have added the GoogleAPIClientForRest (Drive and Sheets) and GTMSessionFetcher (Core) dependencies to my project. However, this code import GoogleAPIClientForRESTCore import GTMSessionFetcherCore func test() { let x = GTLRServiceAccountCredentials.self let y = GTLRAuthorizer.self print("Classes Found") } I get the the following errors: Cannot find "GTLRServiceCredentials' in scope and Cannot find 'GTLRAuthorizer' in scope. The dependencies are listed in the Link Binary with Libraries section. I have am using the latest versions of OS and Xocod and have reinstalled both to try and resolve this issue with no luck.

I use DeviceActivityCenter to monitor app usage. For DeviceActivityEvent, I set 30 events, and the threshold of each event increases by 2 minutes: var events: [DeviceActivityEvent.Name: DeviceActivityEvent] = [:] for index in 0..<30 { let threshold = (index == 29) ? DateComponents(hour: 1) : DateComponents(minute: (index + 1) * 2) let name = DeviceActivityEvent.Name("\(prefix)|\(index)") events[name] = DeviceActivityEvent(applications: tokens, threshold: threshold) } After reaching the last DeviceActivityEvent, I will restart directly in DeviceActivityMonitor private func restartMonitoring(activity: DeviceActivityName) { let center = DeviceActivityCenter() let currentEvents = center.events(for: activity) do { try center.startMonitoring(activity, during: schedule, events: currentEvents) } catch { print("Fail: \(error)") } } But I found that after restarting, DeviceActivityEvent will be automatically executed even if I don't use the app. My iOS version is 18.5

Hi,Does anyone else encountered a delayed or unresponsive change when trying to change input languageon macos Sierra?Beta1 and 2 same problem.Working great on El Capitan.Thanks in advanced

After updating to another beta of High Sierra, my internal hard drive became read-only somehow. I have a user home directory on that and many things have stopped working. I tried re-installing the OS, but it didn't help. I'm out of options by now. Anyone has ideas how can I fix that?

Hello everyone, on August 31st, all the apps in my personal developer account were suddenly expired and deleted, I have not received any response from Apple. My apps are in compliance with Apple's policies. I then uploaded a new version and sent it to the review team, but I received the following error "There was an error processing your request. Please try again later." I have contacted Apple via Email and Phone but no one cares about my problem. Has anyone had the same situation as me, I am really worried.

I encountered some issues while developing a Vision Pro program using Unity. After binding an ARAnchor to a game object, I overlapped the virtual game object with a real-world cup. However, when I moved around with the Vision Pro on, the virtual game object shifted, causing the real-world cup and the virtual object to no longer coincide. Is there a way to solve this?

Hi, I've seen some apps that can have the widget background truly transparent ( not screenshot, code-level transparent) How did they do that? Is that allowed to publish in App Store?

calling this app store connect API returns 201 created but does not clear purchase history for sandbox account

I set iOS 26 to install overnight, put my iPhone 16 Pro on the MagSafe charger, watched it charge just fine, and went to sleep. When I woke up the iPhone showed the “plug into power” dead battery screen. I took it off MagSafe and put it back on. A half hour later the phone was warm but still wouldn’t power on, just showed the battery screen with a little red in it. I took it off MagSafe and plugged it into my iPad charging brick with USB cable to give it more power, still it did not turn on. I tried holding all the buttons to try to force a restart but didn’t work. For anyone else encountering this, do this to enter DFU mode and restore it. I had to do it a few times before I got the timing right. Plug into your Mac and open Finder (or apparently a PC with Apple Devices or iTunes) Press and quickly release volume up Press and quickly release volume down Press and hold right side button When the battery disappears and screen goes black, hold volume down and continue holding side button After a couple seconds release the side button and continue holding volume down A prompt to allow connecting to the iPhone should appear after a couple seconds, click Allow, and it’ll say the iPhone entered DFU mode - proceed to restore the firmware