“swiftui”

@Frameworks Engineer iOS27 launched in beta a few days ago - Are there any news about this clustering feature - or any other Map additions in SwiftUI? Currently in our team we're stuck with UIKit for the map.

From a WidgetKit standpoint: There's no new capability for this, and it's not something widgets are designed to do. Widgets are intentionally timeline based to protect battery and system resources. The system decides when a widget is refreshed, and updates are mostly budgeted. However, on macOS the cadence is somewhat more relaxed than iOS, but even that depends on device conditions. In terms of how this can be achieved in general: The recommended approach is to write the meter value from the audio thread to a thread-safe primitive such as an atomic variable or lock-free ring buffer, then have the UI thread poll and redraw on a timer. For Cocoa/AppKit, CADisplayLink is the right tool for this. For SwiftUI, the idiomatic equivalent is TimelineView.

Hi @harshit090891, You wrote: What triggers this popup during the authentication process? This is not the native authentication flow via the Authentication Services framework or the SignInWithAppleButton in SwiftUI. This alert is presented due to the web auth flow—using the Sign in with Apple REST API, instead of the native API flows mentioned above. If you follow the guidance in the sample code project below, the authentication flow will be presented without an explicit user confirmation to authenticate against the Services ID. This is because the native auth flow is already validated against the app's bundle ID (used as the Client ID). Cheers, Paris X Pinkney |  WWDR | DTS Engineer

Thank you for filing this report. This looks to be brought with the changes of @State becoming a Swift macro rather than a property wrapper. I can see some activity in that feedback report you shared, I'll make sure it is seen by the relevant engineering team directly. Keep an eye on the report. There, updates will be provided to you - if they have questions or updates if your report has been resolved in any way. Please use the inline workaround you provided. I encourage you to test new versions as they are released and update us here and in the Feedback Report so the engineers have a good sense of timeline for this issue. For more information, see TN3211: Resolving SwiftUI source incompatibilities for State and ContentBuilder  Travis

That TabView uses UITabBarController under the hood is an internal implementation detail, and replacing its delegate or otherwise modifying the UITabBarController is not a supported path. If you need full control over a UITabBarController within a SwiftUI view hierarchy, you can use UIViewControllerRepresentable to wrap the tab bar controller.

Hi, thanks for getting back Here is a code snippet where this issue will occur: import SwiftUI struct TestItem: Identifiable { let id = UUID() let color: Color } struct POSView: View { @State private var items = [ TestItem(color: .orange), TestItem(color: .purple), TestItem(color: .teal), TestItem(color: .blue), TestItem(color: .pink), TestItem(color: .green) ] let columns = [GridItem(.adaptive(minimum: 100))] var body: some View { ScrollView { LazyVGrid(columns: columns, spacing: 16) { ForEach(items) { item in RoundedRectangle(cornerRadius: 15) .fill(item.color.gradient) .frame(width: 100, height: 100) } .reorderable() } .reorderContainer(for: TestItem.self) { difference in items.apply(difference: difference) } .padding() } } } extension Array { mutating func apply( difference: ReorderDifference ) where Element: Identifiable, Element.ID: Sendable { guard let sourceIndex = firstIndex(where: { $0.id == difference.sources[0] }) else { return } let movedCard = remove(at: sourceIndex) var destination: In

Is there a way to set the global default to soft for an app? We do not provide API for changing this app-wide, you'll need to use UIScrollEdgeEffect.style in UIKit or the scrollEdgeEffectstyle modifier in SwiftUI for each scroll view where this is relevant. especially since hard edge effects don't work with pinned views in LazyVStack We would be interested in looking into this more; if you could file a feedback or provide a example here, that would be greatly appreciated!

In general we recommend letting the system‘s default ordering persist here. VO users have an expectation when they open a new screen or app that their focus will be at the top, so they can navigate liberally through your content from start to finish. I would probably not recommend moving focus to the tab bar in your case for example. However, if you find cases where the default ordering is incorrect or confusing, you can use .accessibilitySortPriority() in SwiftUI to change the linear order. In UIKit, you can set the accessibilityElements property to a list of ordered accessibility elements to navigate through in the parent view to control the ordering.

To get the best performance, you want to render the CIImage using a SwiftUI view via Metal. There is a presentation from WWDC 22 that describes how to do this https://developer.apple.com/fr/videos/play/wwdc2022/10114/ There is also an associated sample code project: https://developer.apple.com/documentation/CoreImage/generating-an-animation-with-a-core-image-render-destination

We don't have any APIs to automatically combine elements in UIKit like we do in SwiftUI, but manually appending labels of UI elements together is the right approach. Comma separating the labels is typically the right approach, and this is actually what SwiftUI's combine does under the hood. Even for non-latin scripts, the built in synthesizers should apply a pause when encountering a comma. If you are not seeing a pause added when using a comma in a specific language, please file a feedback report so that we can take a look (especially if you are seeing combine in SwiftUI adding a pause for the same language)!