İOS 26 beta battery %1

I developed an app that uses the Core NFC framework to read tags. The feature works correctly on iOS 18 and earlier versions, but after upgrading to iOS 26, it stopped working. Details: Entitlement Near Field Communication Tag Reader Session Formats D2760000850101 D2760000850101 Info.Plist com.apple.developer.nfc.readersession.iso7816.select-identifiers D2760000850101 com.apple.developer.nfc.readersession.felica.systemcodes 12FC Privacy - NFC Scan Usage Description Signing and Capabilities: Near Field Communicating Tag Reading [Eanbled] My Sample Code Is: class NFCManager: NSObject, NFCTagReaderSessionDelegate { private var nfcSession: NFCTagReaderSession? let isConnectionNeeded = false func startNFCSession() { guard NFCTagReaderSession.readingAvailable else { // NFC is not available on this device. return } nfcSession = NFCTagReaderSession(pollingOption: [.iso14443, .iso15693, .iso18092], delegate: self) nfcSession?.begin() } func stopNFCSession() { nfcSession?.invalidate() } // MA

I created an APNs Auth Key in the Apple Developer portal and downloaded it successfully once. Later, due to some issues, I revoked that key. After that, I created a new APNs Auth Key. The download button appears, but when I click it, I get the message: Auth Key can only be downloaded once. This auth key has already been downloaded. This is incorrect because: The key is newly created in my account. I have tried multiple browsers (Safari, Chrome), private/incognito mode, and even a different laptop. I have no other active APNs Auth Keys in my account. Without this .p8 file, I cannot configure push notifications for my iOS app (using Firebase Cloud Messaging). This is blocking my production release. Has anyone else experienced this? Is there a way to reset or force a fresh APNs Auth Key when this happens?

Since 1st of September archives uploaded via Xcode 26 beta 7 or builds distributed via CD (fastlane deliver) don't appear in App Store Connect. No errors reported during/after upload process, no e-mails with errors received. Xcode reports successful upload (with a few warnings regarding dSYM) I'm not getting any e-mails with ITMS errors Builds don't appear at in App Store Connect in TestFlight section (not even in Processing or Failed states). For me it seems like App Store Connect outage but all statuses in https://www.apple.com/support/systemstatus/ are green.

I have a UISplitView with a UINavigationBar where I on iPhone have an issue with a containing UITableView which is not directly placed under the NavigationBar. When the new effect in iOS 26 kicks in it also seems to affect to topmost UINavigationBar which I do not want. It's when the clear UINavigationBar directly over the UITableView and passes over a content that it needs to invert its title over, it does. However it also inverts everything (background + title) of another topmost uinavigationbar which I don't want. This is even opaque and have no reason to invert its colors. Any ideas on how to disable this? navigationItem.style = .editor navigationItem.centerItemGroups = [editorNavigationHelper.iPadCenterItemGroup()] navigationItem.rightBarButtonItems = editorNavigationHelper.rightBarButtonItems() let documentProperties = UIDocumentProperties(url: document.fileURL) if let itemProvider = NSItemProvider(contentsOf: document.fileURL) { documentProperties.dragItemsProvider = { _ in [UIDragIte

I've recently upgraded to the RC candidates of macOS 26 and Xcode 26. The app I'm building has a helper tool using SMAppService. When I run the app and helper tool in macOS 15 or macOS 26, all works as expected. When it runs on macOS 13 or 14, which previously worked. The helper now crashes on launch with the following reason: Termination Reason: CODESIGNING 4 Launch Constraint Violation I found this developer session which seems to address this, but the plist I've added doesn't seem to satisfy the constraint. https://developer.apple.com/videos/play/wwdc2023/10266/ Here are the contents of my new plist: Are there any gotchas here that I might be missing? Thanks!

Hello- My company has an app written in Xamarin. We are aware of the fact that this is end-of-life, and that the app will no longer be releasable once the App Store requires apps to be built using the iOS 18 APIs sometime in April, which Xamarin will not support. We are working on building a replacement for the app, but there is some chance that it will not be ready by the time this requirement is in place. Does Apple offer any sort of system for requesting exceptions or extensions to policies like this? Thank you!

My app update submission has been in the Waiting for Review status for over 72 hours. A few days ago I already canceled and resubmitted after 3 days of inactivity, but this time it still hasn’t moved forward. I’d like to check if there might be any issues on my side that I should address, or if this is just part of the current review timelines. The update includes a critical bug fix, and unfortunately I’m losing users while waiting. Is there anything I can do to help move the review process along, or should I simply continue to wait? The problem is getting more absurd, since it is not a new app submission but an update for already existing one. Thank you in advance.

Hello, Our app gets rejected for the reason that the reviewer cannot purchase the subscription with the message, Guideline 2.1 - Performance - App Completeness We found that your in-app purchase products exhibited one or more bugs which create a poor user experience. Specifically, we were unable to purchase Auto-Renewable Subscriptions. The app launched back to the rendering when we tap on the Get started When we test this with our sandbox accounts in test flight version, we can see the subscribe pop up showing and purchase successfully. But turns out they cannot. Unfortunately we cannot see the reason why and even after requesting further explanation regarding how to move along, we are not getting any explanations. Our subscription products are submitted in the first time with the app and they are in In review state for more than a week. We requested phone calls and wrote messages to reviewers many times but unfortunately there's no help yet.

If an iOS application has a notification service extension which gets sent a push, but the user has not been prompted for notification authorization via requestAuthorization() then what is the expected behavior? Will the push get delivered to the NSE but the resulting notification not displayed? Or will the push not get delivered at all to the NSE?