İOS 26 beta battery %1

Hi Ed, Thanks for the detailed response. I’d like to clarify one point: my app is still using the UIApplicationDelegate lifecycle and not the scene-based lifecycle. Could this duplication be related specifically to using the AppDelegate lifecycle rather than the scene lifecycle? If so, is there a recommended way to handle or prevent the duplicate delivery without migrating to the scene lifecycle? Thanks in advance for your guidance.

People say sometimes, 'You work in the fastest-moving industry in the world.' I don't feel that way. I think I work in one of the slowest. It seems to take forever to get anything done.

@DTS Engineer I just upgraded Xcode to version 26 and downloaded the official release of iOS 26. The issue with fixed elements being incorrectly positioned after the keyboard has been pulled up within a WebView still exists. I hope Apple can intervene and address this as soon as possible. The changes in iOS 26 have affected web pages across the entire internet.

lol rip -- same issue -- trying to find a workaround while we wait. but ay - what's up iOS devs! everyone building an app, from jr to sr, is prob hanging in this thread right now

Additionally, it was working with a beta version of a Yamaha Steinberg USB Control Panel (4.0.3b). When it stopped working, I reverted back to the official release of the Yamaha Steinberg USB Control Panel. (3.1.4) I've deleted and installed both versions and neither seems to work now.

Yep, had no issues for weeks (nothings expired)- i hit the build button and it doesnt work, tried updating to ios 18.7 but no help, reset location and privacy settings, followed everything here but no luck :(

OK, so you’re dying from a launch constraint violation. That launch constraint can come from two places: You can bake a constraint into your executable. The code running your daemon can apply a constraint. I believe you’ve eliminated the first possibility, but it’s a good idea to check that. You can do that using codesign: % codesign -d -vvv Desktop/My App.app/Contents/MacOS/com.myCompany.myDaemon … Launch Constraints: … You shouldn’t see a Launch Constraints field. As to the second possibility, there are two things to check: Make sure your daemon is signed with the some code-signing identity as the container app. Move your app from the desktop to a directory that isn’t protected by MAC. MAC-protected directories — like the desktop, Documents folder, and Downloads folder — cause all sorts of weird behaviour. I generally recommend that you run your app from either the Xcode build directory or /Applications. For more info about MAC, see On File System Permissions. Share and Enjoy — Quinn “The Eskimo!” @ Develop

@hibye seems spot on about the issue, also as reported in this stackoverflow post: https://stackoverflow.com/questions/79758083/ios-26-safari-visualviewport-change-after-dismissing-keyboard before opening the keyboard, visualViewport.height and window.innerHeight match... but after opening the keyboard there's always a 24px difference (and this persists after the keyboard is closed)

Hi, I'm also integrating the passkey feature on my Mac and have meet the same error. Told not to present authorization sheet: Error Domain=com.apple.AuthenticationServicesCore.AuthorizationError Code=1 (null) ASAuthorizationController credential request failed with error: Error Domain=com.apple.AuthenticationServices.AuthorizationError Code=1004 (null) Application with identifier a is not associated with domain b I have config the apple-app-site-association link and use ?mode=developer

// // SettingsHelper.swift // batteryZz // // Created by Nguyen Quang Minh on 15/9/25. // import UIKit class SettingsHelper { static let shared = SettingsHelper() private init() {} enum SettingsType { case appSettings case notificationSettings case microfonSettings case cameraSettings case locationSettings case photosSettings case siriSettings case wifiSettings case bluetoothSettings case cellularSettings case batterySettings case privacySettings var urlString: String { switch self { case .appSettings: return UIApplication.openSettingsURLString case .notificationSettings: if #available(iOS 16.0, *) { return UIApplication.openNotificationSettingsURLString } else { return UIApplication.openSettingsURLString } case .microfonSettings: return App-Prefs:Privacy&path=MICROPHONE case .cameraSettings: return App-Prefs:Privacy&path=CAMERA case .locationSettings: return App-Prefs:Privacy&path=LOCATION case .photosSettings: return App-Prefs:Privacy&path=PHOTOS case .siriSettings: return App-Prefs

[quote='858072022, .steve, /thread/798328?answerId=858072022#858072022, /profile/.steve'] those apparently don't show up in the Console app. [/quote] Yeah, that’s an annoying pitfall. You have to explicitly enable those via the commands on the Action menu. If you’re working at this level, it’s worth spending the time to learn more about the system log. There are lots of hints, tips, and references to docs in Your Friend the System Log. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='858181022, PeterSenyszyn, /thread/800521?answerId=858181022#858181022, /profile/PeterSenyszyn'] none of those suggestions worked for me unfortunately [/quote] OK. We’re currently tracking an issue that affects provisioning profile generation for TestFlight (r. 160638630). It’s possible that this is also affecting development profiles. I’m currently researching that. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I've tried it on a completely fresh app and an app that was working previously. Hasn't been working for the past 3 hours or so. Glad to hear I'm not the only one

I have a theory as to what’s going on here, and I’d like you to run a test to exercise that theory: First, create a new app, with a new unique bundle ID, and try running that. For specific instructions, see the first numbered list in Investigating Third-Party IDE Code-Signing Problems [1]. If that works, repeat the process using the bundle ID of your main app. For specific instructions, see the second numbered list in Investigating Third-Party IDE Code-Signing Problems. If that fails: Quit Xcode. Go to ~/Library/Developer/Xcode/UserData/Provisioning Profiles and delete all your profiles. Relaunch Xcode. Try again. Lemme know how you get along. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] I realise your issue has nothing to do with third-party IDEs, but those instructions are good for basic tests like this.