“swiftui”

Hey there! Still don't get any answer about this topic so I take the advantage of the WWDC to reopen it. I really would like to ensure I have not missed something. I did the full implementation using UIKit UICollectionView using performBatchUpdates to deal with my double sided pagination. But I still have some crashes issues or even strange animation when scrolling up to load above pages. So here are my 2 questions Is there a way to accomplish natively and properly a double-sided pagination in UIKit? Is this possible in SwiftUI? I'm attending WWDC this year so I would be happy to discuss irl about that topic. Best

I’m seeing what looks like the same issue in my app as well. In my case, I have a top control pill that uses Liquid Glass, and inside that pill there are two SwiftUI Menu buttons. The issue happens with both menu buttons: one uses the line.3.horizontal.decrease symbol and the other uses the number symbol. The glass pill normally renders correctly, but after opening and dismissing one of the menus, the control briefly appears as a solid/dark pill before returning to the expected transparent Liquid Glass appearance. Here is the relevant structure from my code: private var displayOptionsPill: some View { HStack(spacing: 0) { filterMenuButtonInPill displayModeMenuButtonInPill } .padding(.horizontal, 6) .frame(height: 44) .glassEffect(.regular.interactive(), in: Capsule()) } private var filterMenuButtonInPill: some View { Menu { filterMenuContent } label: { Image(systemName: line.3.horizontal.decrease) .font(.title2) .fontWeight(.medium) .foregroundStyle(.primary) .frame(width: 38, height: 32) .contentSha

After trying every option I can find, I don't believe notifications can wake a sleeping Mac and allow my third-party app to process data, but I really want to be wrong. Can anyone confirm whether or not this is possible? I'll cover a few details below but the short summary is that, no, I don't think this will really work, at least not in a way that's reliably tied to the notification itself. Getting into some specifics, let me start with some background context: Wake for Network Access This particular setting actually controls a ethernet hardware level feature called Wake-on-LAN (WoL). How this actually works is that the ethernet controller itself passively monitors the bus watching for a very particular packet (the magic packet), waking the machine up if it ever receives it. The critical point to that is that this ISN'T a generic wake me up for any traffic mechanism. It has very specific contents (notably, the device MAC address) and generally only originates from with the local network, not from a remote ho

@DTS Engineer Sure! Please try this code with the Settings → Accessibility → Display & Text Size → Reduce Transparency option enabled. Feedback ID: FB22913365 import SwiftUI struct ContentView: View { @State var tab = 0 var body: some View { TabView(selection: $tab) { TabContentView() .tabItem { Label(One, image: ) } .tag(0) TabContentView() .tabItem { Label(Two, image: ) } .tag(1) } } } struct TabContentView: View { @State var path = [Int]() var body: some View { NavigationStack(path: $path) { NavigationStackFirstView(onNext: { path.append(0) }) .navigationDestination(for: Int.self) { destination in Group { switch destination { case 0: NavigationStackSecondView() default: EmptyView() } } .toolbar(.hidden, for: .tabBar) } } .navigationViewStyle(StackNavigationViewStyle()) } } struct NavigationStackFirstView: View { let onNext: () -> Void var body: some View { VStack { Text(View with tabbar) .font(.system(size: 24)) .padding() Button(Go to view without tabbar) { onNext() } } .frame(maxWidth: .i

@SergioDCQ Thanks for the interesting observation. I didn't copy your code but looking at the dark setting I got the idea of what is happening, I think. When iOS suggests and fills a strong password, it forces the underlying TextField's background to yellow and its text color to black (to ensure the text is readable against the yellow highlight). When the yellow highlight fades out, the system is supposed to restore the original text color. However, because you are using a hardcoded color (colorScheme == .dark ? .white : .black) Since SwiftUI's state hasn't changed, it never re-applies the .white color, leaving you with invisible black dots on a black background. Instead of manually switching between .white and .black, use SwiftUI's semantic .primary color (or Color(uiColor: .label)). Replace your .foregroundColor modifiers on the TextFields with .foregroundStyle(.primary) you can force SwiftUI to re-apply the text color by slightly changing the color value when the password is auto

@SergioDCQ Thanks for the interesting observation. I didn't copy your code but looking at the dark setting I got the idea of what is happening, I think. When iOS suggests and fills a strong password, it forces the underlying TextField's background to yellow and its text color to black (to ensure the text is readable against the yellow highlight). When the yellow highlight fades out, the system is supposed to restore the original text color. However, because you are using a hardcoded color (colorScheme == .dark ? .white : .black) Since SwiftUI's state hasn't changed, it never re-applies the .white color, leaving you with invisible black dots on a black background. Instead of manually switching between .white and .black, use SwiftUI's semantic .primary color (or Color(uiColor: .label)). Replace your .foregroundColor modifiers on the TextFields with .foregroundStyle(.primary) you can force SwiftUI to re-apply the text color by slightly changing the color value when the password is auto

Hi, Sorry to hear you are having trouble viewing different locales while using previews. Unfortunately you have here found a situation where overriding the locale in the environment doesn't work for APIs that don't interact or read from the SwiftUI environment (Formatters is another common one folks are impacted by). The only suggestion I have for now is to use the scheme picker's UI affordance to manually switch between locales/languages as opposed to just overriding the SwiftUI environment's Locale.

I explicitly choose SwiftUI... so I will have to wait for the feature to appear again... I will not go back - especially since the apps I am currently developing shall work on Mac/iOS and SwiftUI makes that rather easy while building native apps ;) Fair enough. The one thing I'll add here is that, particularly in terms of new development, I'd suggest trying to design your product in ways that intentionally avoid relying on related item support. While this should work, by definition, you're getting access to a file the user didn't explicitly give you access to, which means it's also an area with significant security implications and higher risk of failure. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

is there a secure way for me to send the project to you? or maybe you can share your project? I observed the issue in SwiftUi Previews.

Thanks Kevin! I explicitly choose SwiftUI... so I will have to wait for the feature to appear again... I will not go back - especially since the apps I am currently developing shall work on Mac/iOS and SwiftUI makes that rather easy while building native apps ;) Best wishes, Volker