Hi! I've encountered strange bug in iOS 26. The MultiDatePicker component exhibits unreliable behavior when attempting to deselect previously chosen dates. Users often need to tap a selected date multiple times (e.g., tap to deselect, tap to re-select, then tap again to deselect) for the UI to correctly register the deselection and update the displayed state. This issue does not occur on iOS 18 or Xcode 26 previews, where MultiDatePicker functions as expected, allowing single-tap deselection. The bug only occurs on physical device or simulator. I can't lie, I have multidatepicker as crucial component in my larger app and can't really find a solution to this. Has anyone encountered this problem before? Here is the code to replicate the issue: import SwiftUI struct ContentView: View { @ State private var selectedDates: Set = [] var body: some View { NavigationStack { Form { Section { MultiDatePicker(Select Dates, selection: $selectedDates) } header: { Text(MultiDatePicker Bug
Search results for
İOS 26 beta battery %1
250,756 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi everyone, so I have a widget that is loading and showing images. When changing my icons and widget to transparent or tinted on iOS 26 they just turn white or the tint color. How can I mark images to preserve their appearance aka color? The Fotos widget has (long press and its configuration) and option to tint them or preserve the color. I just can't figure out how it's done and what API to use. Second, is there an API to learn which mode is currently being used to tweak other elements of the UI? Thanks for any advice.
UIGlassEffect is giving a black rectangle, I tried setting the effect directly and in the animation block, but It does not make a difference. Replacing the effect with Blur sets the effect as expected. If there is another view inside the visualeffect.contentView it's not displayed as well. I tried setting the layout constraints as well as manually setting the frame of the VisualEffectView with no luck. iOS 26.0 (23A341)
Topic:
UI Frameworks
SubTopic:
UIKit
As a very exclusive Apple only I want to share my thoughts on the new iOS 26 update, which I recently installed on my iPhone 16. While I genuinely appreciate Apple’s drive for innovation and personalization, this update introduces visual and stylistic changes that, in my opinion, compromise what has made iOS feel uniquely Apple for so long. Liquid Glass & Home Screen Aesthetics: When I first saw previews of the “Liquid Glass” design, I was excited. I assumed it would add more flexibility to things like the home screen customization — something like an optional effect that builds on the popular app tinting feature introduced in the previous iOS version. But instead, it appears that the Liquid Glass look is now the default and, more concerningly, unavoidable. The result is a visual experience that feels dramatically more bubbly and less refined. App icons appear more rounded and inflated in a way that — and I say this as constructively as I can — reminds me more of Androi
Found this thread when researching an issue with the same log message in a pure SwiftUI app. There's a nasty layout/animation associated with what I'm seeing (but I'm not sure it's related to the log). A sample project to repro is attached to FB20272800 (apologies for hijacking OP's thread, but I thought it might perhaps be interesting to them that issue reproduces in iOS 26 without using a UIHostingController in our own code. A simple Menu suffices)
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
Hi, after updating to iOS 26 I'm encountering an issue where the FamilyActivityPicker no longer opens. No errors are shown in the console, it just never shows up. It works fine pre iOS 26. I've never had any issues with the picker showing up until iOS 26. My latest update was rejected because of this issue, but I've changed nothing in the code. Is anyone else experiencing this?
Topic:
App & System Services
SubTopic:
General
Tags:
Family Controls
Device Activity
Managed Settings
My app is a VoIP softphone for Mac that allows people to make phone calls to a regular phone numbers. The app exists since before Mac App Store. The app declares itself to the system as capable of handling tel: URLs. Until now, people could change the default handler for tel URLs in FaceTime settings (Default for calls). In macOS Tahoe 26, this doesn't seem to be possible any more. That option is gone from the FaceTime settings. Is it completely gone or has it been moved somewhere else? If there is no UI control for this any more, is it possible to change it programmatically?
Topic:
App & System Services
SubTopic:
General
Hi, Since I updated my phone to 23A341, my Call filtering app is not blocking calls anymore. Same release checked on iOS 18 phone, it is working. I still see the callkit logs into the Console showing that numbers are loaded into the iOS-managed SQlite DB but the calls are not blocked nor identified. Anyone with the same issue? BR
Just tested this and see Not Valid Before=Tuesday, September 16, 2025 at 1:37:53 PM Pacific Daylight Time Not Valid After=Friday, October 16, 2026 at 1:37:52 PM Pacific Daylight Time Perhaps it was a glitch at the time
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
Tags:
I am scheduling critical user notifications with a custom sound. This worked for years both on devices and in the simulator. Since Xcode 26 it crashes in simulator. Example let content = UNMutableNotificationContent() content.title = Critical content.body = Example content.sound = UNNotificationSound.criticalSoundNamed(UNNotificationSoundName(notification.aiff), withAudioVolume: 0.5) content.interruptionLevel = .critical let trigger = UNTimeIntervalNotificationTrigger(timeInterval: 10, repeats: false) let request = UNNotificationRequest(identifier: exampleCriticalNotification, content: content, trigger: trigger) UNUserNotificationCenter.current().add(request) It seems that simpler variants such as just content.interuptionLevel = .critical or just content.sound = UNNotificationSound.defaultCritical also crash. I assume that critical notifications is a small niche use case but i still hope this gets fixed. This is filed as FB20272392 with a full crash log.
The ability to stay connected to a BLE device is not something that can be enhanced via an app. A whole lot will depend on the hardware, like antenna design; environment, like distance, RF interference; materials between the two devices; and various connection parameters including but not limited to the power profiles. Assuming you have no control whatsoever on any of these, the only thing you can do in the app is to make sure you are able to connect as quickly as possible when (not if) the connection drops. This means you need to make sure you have implemented Bluetooth State Restoration, so your app gets relaunched even if the app has been terminated in the background by the system. The document Performing Long-Term Actions in the Background explains how to implement this. The second thing you need to do is to make sure you issue a connectPeripheral command as soon as your app gets the callback that the connection has dropped. It is advisable to keep the CBPeripheral object from the last connection and send
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
While I am not new to programming, I am quite new to the Swift language. I am using the Swift Playground app on macOS 26 on an M1 MacBook Air. I am on the lesson about types. Perhaps it's a silly question, but what is a portal? It is never described or pointed out where to find it in the puzzle world. Similarly, the instructions reference a switch object without ever defining what it is. I cannot write code to call methods or set properties on objects about which I have no useful information. Can anyone advise, please? Thank you kindly.
Crashlog-0916-071225.log I have an app that crashes on OSX 26 only. I have a @StateObject which is an observer of the NSColorPanel. When I call let panel = NSColorPanel.shared in init(), SwiftUI will crash - apparently with an update while view is being updated. See crash log. I was able to work around it by adding let _ = NSColorPanel.shared in my AppDelegate before SwiftUI is initialized. The exact code worked fine in all previous OSX versions.
I recently updated to macOS sequoia 15.6 Afterward, I updated to Xcode 26 The project I've been running for the last couple years no longer compiles on existing simulators and doesn't build to a physical device. I'm getting an error I'm not familiar with and have no idea how to directly resolve it: The specific error is 'Command SwiftGeneratePch failed with a nonzero exit code' Looking up this issue via Google, there wasn't really a lot of information on this particular build failure. Most suggestions were to change the location of the Derived Data folder (Xcode -> File -> Project Settings -> update location of derived data from default to relative) This was one of the only actionable solutions I found online but this doesn't fully address the issue for me, it just creates a new issue: Command PhaseScriptExecution failed with a nonzero exit code I feel like with enough digging around I should be able to find a solution to the PhaseScriptExecution issue; there seems to be a decent am
Please see the Configuring Your App to Use Alternate App Icons that uses Icon Composer files and supports iOS 18 or later. Note: The sample only uses Icon Composer files. No old icons.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags: