İOS 26 beta battery %1

On iPad OS 26, the custom keyboard works correctly with a full keyboard, but with a floating keyboard, there is only one line and the console displays a constraint error. Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. ( , , , , , , , ) Will attempt to recover by breaking constraint Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger. The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in may also be helpful. iPad OS 26 custom keyboard, full keyboard mode is working normally.

Updated the phone to iOS 26.1 and now the app is not working anymore, even previously approved version published on App Store which works perfectly on iOS 26.0.1, and iOS 18+. I deleted the app from the phone and installed fresh from App Store, still the same. Logic is that on start app copies previously prepared SwiftData store file (using the same models) from app bundle to Documents directory and uses it. Currently app just hungs with loader spinner spinning as it can t connect to the store. Getting this error in console when running from Xcode on real device with iOS 26.1 installed: CoreData: error: CoreData: error: Store failed to load. (type: SQLite, url: file:///var/mobile/Containers/Data/Application/DA32188D-8887-48F7-B828-1F676C8FBEF8/Documents/default.store) with error = Error Domain=NSCocoaErrorDomain Code=134140 Persistent store migration failed, missing mapping model. UserInfo={sourceModel=() isEditable 0, entities { /// there goes some long models description

When we use AppIntents to configure WidgetKit complications, the description we provide in IntentRecommendation is ignored after applying a .watchface file that includes those intent configurations. In the Watch app, under Complications, the labels shown next to each slot do not match the actual complications on the face—they appear to be the first strings returned by recommendations() rather than the selected intent configuration. Steps to Reproduce Create an AppIntent used by a WidgetKit complication (e.g., .accessoryRectangular). Provide multiple intent recommendations with distinct descriptions: struct SampleIntent: AppIntent { static var title: LocalizedStringResource = Sample static var description = IntentDescription(Sample data) @Parameter(title: Mode) var mode: String static func recommendations() -> [IntentRecommendation] { [ .init(intent: .init(mode: A), description: Complication A), .init(intent: .init(mode: B), description: Complication B), .init(intent: .init(mode: C), description: Complicati

We’re preparing our 2026 iOS development roadmap and need clarification on upcoming App Store submission requirements related to Xcode versions. Our team plans to migrate our apps to Xcode 26 by December 2025, and we’ve seen references indicating that Xcode 26 or later may become mandatory for App Store submissions starting April 2026. Could Apple please confirm: 1. Whether April 2026 is the official enforcement date after which builds created with earlier versions of Xcode (e.g., Xcode 16.x) will no longer be accepted for App Store submission. 2. Whether there will be any grace period or continued acceptance for builds created with older versions of Xcode beyond that date. We want to ensure our upgrade plans and release timelines are aligned with Apple’s official submission policies to prevent any disruption to our delivery schedules. Thank you for your guidance.

I’m implementing App Store subscriptions using StoreKit 2 and testing in the Sandbox environment. Until about a week ago everything worked fine, but recently the Settings > Subscriptions screen shows this message for my test account: “Your current payment method is not available.” The behavior: • Using a Sandbox tester account (not a production Apple ID) • Purchase flow works successfully — the transaction completes, and I receive server notifications • However, the system Settings app still displays that message under the subscription entry • No code changes were made since it last worked Questions: 1. What exactly does this message mean in the Sandbox environment? 2. Could this be related to any Apple system issue or recent backend update? 3. Has anyone else seen the same behavior in recent days? Environment: • Xcode 15.4 • iOS 17.5 (physical device) • StoreKit 2 / Swift 5.10 • Sandbox tester (Japan region) Thanks in advance for any insights or confirmations from others who are testing

We’ve recently changed the name of our published app from “Gourmet Society Lloyds” to “Gourmet Society”. The current App Store link is: https://apps.apple.com/gb/app/gourmet-society-lloyds/id6447692472 After the name change, we expect the URL to look like this: https://apps.apple.com/gb/app/gourmet-society/id6447692472 However, we’re not sure whether Apple automatically updates the App Store URL (the text part before the ID) when the app name changes, and whether the old URL will continue to redirect to the new one. I couldn’t find any official Apple documentation confirming this behavior. Could someone from Apple clarify how App Store URLs are handled in such cases? Thanks in advance! Zoltan

I am trying to perform swiftUI instrumentation on my ios app. whenever i hit the rocord button, the app launches on target device and closes with the error: Failed to start the recording: Failed starting ktrace session. How do i resolve this please?

I am trying to make build for my project followed all step and all but Igot Showing Recent Errors Only Build target PCS_EmpApp of project PCS_EmpApp with configuration Debug ProcessInfoPlistFile /Users/mayankjain/Library/Developer/Xcode/DerivedData/PCS_EmpApp-bhccfqkphneiyabcysmesvskjrrm/Build/Products/Debug-iphonesimulator/PCS_EmpApp.app/Info.plist /Users/mayankjain/Downloads/RetailApp/PCS_EmpApp/obj/Debug/net9.0-ios/iossimulator-arm64/xcsync/Info.plist (in target 'PCS_EmpApp' from project 'PCS_EmpApp') cd /Users/mayankjain/Downloads/RetailApp/PCS_EmpApp/obj/Debug/net9.0-ios/iossimulator-arm64/xcsync builtin-infoPlistUtility /Users/mayankjain/Downloads/RetailApp/PCS_EmpApp/obj/Debug/net9.0-ios/iossimulator-arm64/xcsync/Info.plist -producttype com.apple.product-type.application -genpkginfo /Users/mayankjain/Library/Developer/Xcode/DerivedData/PCS_EmpApp-bhccfqkphneiyabcysmesvskjrrm/Build/Products/Debug-iphonesimulator/PCS_EmpApp.app/PkgInfo -expandbuildsettings -format binary -platf

I'm encountering unexpected behavior with @Binding in a UIViewRepresentable's Coordinator. The same Coordinator instance returns different values depending on how the property is accessed. Environment: iOS 17+ / Xcode 15+ SwiftUI with UIViewRepresentable Issue: When I access @Binding var test inside the Coordinator: ✅ Via self.test in Coordinator methods: Returns the updated value ❌ Via context.coordinator.test in updateUIView: Returns the stale/initial value Both access the same Coordinator instance (verified by memory address), yet return different values. Minimal Reproducible Example: struct ContentView: View { @State private var test: [Int] = [1, 2, 3, 4, 5] var body: some View { VStack { TestRepresentable(test: $test) Text(State: (test.description)) } } } struct TestRepresentable: UIViewRepresentable { @Binding var test: [Int] func makeUIView(context: Context) -> UIButton { let button = UIButton(type: .system) button.setTitle(Toggle, for: .normal) button.addTarget( context.coordinato