Hello, In iOS 26 beta, we are seeing an unexpected behavior when using SwiftUI WebView (or a custom WKWebView via UIViewRepresentable). When an alert is presented above the WebView, the WebView immediately reloads to its initial page. The alert itself also disappears instantly, making it impossible for the user to interact with it. This issue occurs both with the new SwiftUI WebView / WebPage API and with a wrapped WKWebView. The problem was not present in previous iOS versions (iOS 17/18). Steps to reproduce: Create a SwiftUI view with a WebView (pointing to any URL). Add a toolbar button that toggles a SwiftUI alert. Run the app on iOS 26 beta. Tap the button to trigger the alert. Expected behavior: The WebView should remain as-is, and the alert should stay visible until the user dismisses it. Actual behavior: As soon as the alert appears, the WebView reloads and resets to the initial page. The alert disappears immediately. Minimal Exam
Search results for
İOS 26 beta battery %1
253,916 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
My phone has been draining battery so rapidly even tho I don’t use it much
My banking apps was crashing when i installed IOS 16 public beta 1, is this issue fixed in ios 16 public beta 2. I seriously want to hands on ios 16 but cant do with this bug. Can you tell me is this issue fixed in public beta 2
After updating to ios 11 on Sep 19, 2017 the battery is getting drained fast. It was not like that in previous version of 10.3.3. Any update why is it so.?
I'm using an iPhone 6s and it won't let me update to iOS 10.1 beta so I can get the actual iOS 10 . I've done everything and every time and still said update Fail
Yes, I’m seeing the exact same issue since iOS 26 beta 3. Everything worked correctly up to beta 2. Since beta 3 and now also 4, UIColor.label and other dynamic colors no longer update properly when switching between light and dark mode—especially in the Sidebar (Primary View) of UISplitViewController. In my case, it also affects the Secondary View—for example, built-in system controls like the Date Picker or Context Menu UI are also rendering incorrectly, often showing incorrect colors. It definitely looks like a regression in iOS 26 beta 4. I’d recommend filing a bug report via Feedback Assistant if you haven’t already—this one needs Apple’s attention.
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
This is a good answer. So all the heavy processing had nothing to do with ios beta nor apple intelligence, rather the fact that I wiped and restored my iphone. now it finished and things look better, but I do believe that battery is getting drained faster on the beta. you also seem to believe that battery consuming processes wont harm the battery at all? You think this because they are infrequent or because it is other things that matter most, like staying in the 20-80 range?
Topic:
Community
SubTopic:
Apple Developers
I think they send beta questions here. Beta's may produce additional logging and have a shorter battery life. One if the many reasons you should think long and hard before installing beta software on your main device.
Topic:
Community
SubTopic:
Apple Developers
Tags:
On iOS 26 beta 4, those problem are not fixed yet!
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
This looks like it's fixed in iOS 26 Beta 1. If you use the extension workaround above you get a warning Conformance of 'Schema.Version' to protocol 'Sendable' was already stated in the type's module 'SwiftData' 'Schema.Version' declares conformance to protocol 'Sendable' here (SwiftData.Schema.Version)
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
Hi, I'm seeing an issue in iOS 26 beta related to UINavigationBar rendering in landscape. When a background color is set for the navigation bar and the device is rotated to landscape, an unexpected gap appears above the navigation bar. This also happens in the official sample project provided in Apple’s documentation: https://developer.apple.com/documentation/uikit/customizing-your-app-s-navigation-bar Is this a bug in the beta, or is there a workaround to avoid this behavior? Thanks in advance!
Hi, I'm trying to add an extension to my app on iOS 26. I've followed the instructions on https://developer.apple.com/documentation/extensionfoundation/adding-support-for-app-extensions-to-your-app and made it as far as being able to launch the extension: let monitor = try await AppExtensionPoint.Monitor(appExtensionPoint: .localWebServerExtension) currentIdentity = monitor.identities.first if let currentIdentity = currentIdentity { let myConfig = AppExtensionProcess.Configuration(appExtensionIdentity: currentIdentity, onInterruption: { NSLog(extension was terminated) }) myProcess = try await AppExtensionProcess(configuration: myConfig) myConnection = try myProcess?.makeXPCConnection() } None of these calls throw, and when I examine myProcess from inside that code, it seems to be normal (there's a pid, for example). Yet the code inside my extension seems to not be executed: breakpoints are not triggered, NSLog() calls do not appear on the console. The onInterruption() callback is also not tr
My AppleCare is about to expire (a week) and I am experiencing 1% battery health decrease every 10 days or so. I use my iPhone 14 pro max lightly, and usually full charge it every 2 days. Followed all the tips that Apple recommends to maintain battery health, all of them did not work. Went to Apple store to get it fixed, but I have to pay out out pocket because it is now 94% and not eligible for AppleCare coverage that is supposed to be 79% or less. Suggestions would be appreciated on what should I do to get the battery replaced with my coverage. thank you
After the last OS26 developer beta update the watch series 6 battery drains fast, in less than two hours life. I visited Apple Store , they said the battery was dead so I had to buy new watch series 10 The same issue happened in the new watch, the battery meter shows 50% after 1 hour Right now I’ve downgraded my update version to beta 11 until I can find a solution
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Environment iOS 26 (23A343) Xcode 26 Reproduces on device and Simulator Description When presenting a SwiftUI WebView (native iOS 26 component) or a WKWebView/UIWebView via UIViewRepresentable, focusing a text field inside the web view and then dismissing it breaks the keyboard layout behavior. After returning to the main app, tapping any TextField causes the keyboard to cover bottom controls (e.g. buttons). Expected safe area insets are not applied. The issue is only resolved after closing and reopening the keyboard once. Steps to Reproduce Open a SwiftUI screen with WebView (via .sheet or NavigationLink). Inside the web view, tap a text field to show the keyboard. Dismiss the web view. Tap a TextField in the main app. Expected Result Layout should adjust correctly. Bottom controls stay visible above the keyboard. Actual Result Keyboard covers bottom controls. Insets are ignored until the keyboard is dismissed and reopened. Notes Reproduces with: Native SwiftUI We