“swiftui”

I have a SwiftUI app that opens a user-selected audio file (wave). For each audio file, an additional file exists containing events that were extracted from the audio file. This additional file has the same filename and uses the extension bcCalls. I load the audio file using FileImporter view modifier and then access the audio file with a security-scoped bookmark. That works well. To clarify here, do you mean that you’re able to access both the directly selected file and its related sidecar? Or just that you're able to access the direct file? After loading the audio, I create a CallsSidecar NSFilePresenter with the URL of the audio file. I make the presenter known to the NSFileCoordinator and then add it to the FileCoordinator. This fails with NSFileSandboxingRequestRelatedItemExtension: Failed to issue extension for; Error Domain=NSPOSIXErrorDomain Code=3 No such process Is the failure here about opening an existing file or about writing a new file? Also, what directory are you working out of? __ Ke

No, I don't think there is a way to find a SwiftUI view via its accessibilityIdentifier. If your intent is to retrieve the frame of a Text and do something based on that in a parent view, GeometryReader + PreferenceKey / anchorPreference will be the way to go, even though it needs some additional code. In iOS 16, onGeometryChange(for:of:action:) allows you to perform an action when a geometry value of a view changes. If you target iOS 16 and later, that may be even easier. Best, —— Ziqiao Chen  Worldwide Developer Relations.

On the workaround front, you’re using MKMapView via UIViewRepresentable. If you switch to the shiny new Map SwiftUI view, does that avoid the problem? Haha I knew you were going to say that. :) Probably, but we still support back to iOS 16 so that's not currently an option. And, since it's just annoying log entries... Another option is to filter these log entries out in Xcode: Thanks for that! I also found the right-click / hide option in the logs that allow the filtering by various categories which definitely helps a lot. As always, thanks so much for your help.

[quote='873874022, FT-cfoy, /thread/811791?answerId=873874022#873874022, /profile/FT-cfoy'] I wish I could ignore it [/quote] )-; [quote='873870022, FT-cfoy, /thread/811791?answerId=873870022#873870022, /profile/FT-cfoy'] I've submitted a bug report with this FB21768382 [/quote] Thanks. That’s definitely the right choice in this situation. Also, please add a sysdiagnose log to that bug, one taken on your device shortly after reproducing the issue. That helps with the triage. On the workaround front, you’re using MKMapView via UIViewRepresentable. If you switch to the shiny new Map SwiftUI view, does that avoid the problem? Another option is to filter these log entries out in Xcode: Locate the Filter box at the bottom of the Console debug area. Copy the string subsystem:com.apple.PerfPowerServices and paste it into the box. That’ll create a Subsystem filter. In the menu hanging off that filter, select “≠ is not”. For many other systems log hints and tips, see Your Friend the System Log. Share and Enjo

[quote='873863022, DTS Engineer, /thread/813853?answerId=873863022#873863022'] may I ask you to file a bug with that project? [/quote] Before you do that, I’d like to clarify what you mean by this: [quote='813853021, OC_s, /thread/813853, /profile/OC_s'] How do I determine the real values? [/quote] What specific information are you looking for here? And what do you plan to do with that information? This matters because Mac Catalyst is returning values that make sense in the iOS-ish environment that’s expected by such apps. It is possible to get ‘real’ values, but the best way to do that depends on your specific setup. For example, the systemName property is uninteresting in a Mac Catalyst app because the real system name is macOS. So you can do this [1]: let systemName: String #if targetEnvironment(macCatalyst) systemName = macOS #else systemName = device.systemName #endif However, that’s just one of these properties. The best path for the other properties varies based your the specific property and your ulti

Thanks Quinn. This looks to possibly be an internal Apple bug with MKMapView. I can recreate the issue with the following code: import MapKit import SwiftUI struct MyMapkitView: UIViewRepresentable { typealias UIViewType = MKMapView func makeUIView(context: Context) -> MKMapView { return MKMapView() } func updateUIView(_ uiView: MKMapView, context: Context) {} } struct ContentView: View { var body: some View { VStack { MyMapkitView() } .padding() } } Which immediately gives the errors below that match what I'm seeing in my app. I wish I could ignore it, but it quite literally is happening 2-3 times a second so the log is completely buried with these messages. This only started happening when I upgraded Xcode to 26.

SwiftUI view hierarchy is internal to the framework. When using SwiftUI, you won't need to traverse the view hierarchy – If you do, I'd say that you probably aren't on the right track... Having said that, I'm quite curious why you need to traverse the view hierarchy in SwiftUI. Would you mind to share? Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hello @Julsalim , You don't need to programmatically hide the TabBar, it can be done by restructuring your Views. Make sure the NavigationStack contains the TabView, and the Tab contains the NavigationLink. Here's an example view structure that achieves what you're looking for: Also, welcome to iOS Development! SwiftUI is my favorite!  Travis Trotto - DTS Engineer NavigationStack { TabView{ Tab(, systemImage: ) { List{ NavigationLink(... }

Solved. An iOS 2.0 feaure that I assume is being set automatically by SwiftUI. [[ UIApplication sharedApplication ] setIdleTimerDisabled:true ];