Hello! I developed a vpn application with PacketTunnel target. And I found that an app can pop up a system alert when connecting through VPN settings. I want to know how this approach is achieved.

Under iOS 17, I need to set view.backgroundColor when using UIActivityViewController, otherwise the navigationBar will be transparent. (iOS 17 does not have this problem) I have checked many tutorial examples but this situation is not mentioned. Is there any implementation missing from my code? Sample Code: let sharedURL = URL(string: "...")! let activityVC = UIActivityViewController(activityItems: [sharedURL], applicationActivities: nil) present(activityVC, animated: true) Sample Image:

In iOS 26.1, SwiftUI's tabViewBottomAccessory API cannot control visibility properly. The tabViewBottomAccessory remains always visible, which is inconsistent with the behavior in iOS 26.0 / iOS 26.0.1. ` struct ContentView: View { enum Tabs { case first } @State private var selection: Tabs = .first @State private var showBottomAccessory: Bool = true var body: some View { tabView } var tabView: some View { TabView(selection: $selection) { Tab(value: .first) { content } label: { VStack { Text("first") } } } .tabViewBottomAccessory { if showBottomAccessory { Text("BottomAccessory") } } } var content: some View { Button("change") { showBottomAccessory.toggle() } } } `

I'm encountering an issue with navigation title behavior in watchOS SwiftUI. When using a String for the navigation title, long titles automatically scroll as expected. However, when switching to Text with custom foreground color, the scrolling behavior is lost. Important Observation: The system Settings app on watchOS successfully displays navigation titles with blue color while maintaining scroll behavior. This suggests it should be technically possible - am I missing some implementation approach? struct ContentView: View { var body: some View { NavigationStack { NavigationLink("Go Next") { LinkView() } } } } struct LinkView: View { enum NavigationTitleMode: String { case string case text } @State private var titleMode: NavigationTitleMode = .string let title: String = "Watch UI Test Navigation Title" var body: some View { switch titleMode { case .string: content .navigationTitle(title) case .text: content .navigationTitle { Text(title) .foregroundStyle(.blue) } } } var content: some View { VStack { Text("Mode: \(titleMode.rawValue)") Button("Change Mode", systemImage: "pencil") { if titleMode == .string { titleMode = .text } else { titleMode = .string } } } .padding() .navigationBarTitleDisplayMode(.inline) } } String Mode: Text Mode: Environment watchOS 26.0 Xcode 26.0 (17A324) Swift 5.9

Hello everyone, I am facing a critical and blocking issue regarding watchface sharing on iOS/watchOS 26 and would appreciate any immediate guidance or updates from the community or Apple. The Problem: We are unable to share watchfaces containing any complications from our app in TestFlight and App Store distribution environments. The operation fails with an error indicating the app and complications are unavailable. However, the exact same functionality works perfectly in all development builds (both Debug and Release schemes). This issue was not present on iOS/watchOS 18. We have testing, including: Successfully sharing the watchface in development environments. The failure occurs consistently across TestFlight and App Store builds. Exporting the watchface configuration from a TestFlight/AppStore build on iOS, transferring it to a paired watch, and finding it still shows as "Unavailable". We suspect this may be related to the dual-target architecture of Watch apps. Any guidance or updates would be greatly appreciated. Thank you for your time and support!