Request failed with http status code 503

Hello Ikester, have you tried giving the button a modifier .zIndex() or applying an .overlay() to the detail view of your NavigationSplitView? Maybe if you implement the two buttons in an .overlay() and give those buttons an .offset() as well it might work. NavigationSplitView() { //your navigation views } detail: { //your content views } .overlay() { Button(click me) {} .offset(CGSize(width: 10, height: 10)) } For accurate positioning you could add a GeometryReader(){geometry in}. If this doesn’t work this maybe will: .toolbarVisibility( .hidden, for: .navigationBar, .tabBar) you add this modifier to your first nested view inside the NavigationSplitView. This is much better explained here: https://developer.apple.com/documentation/swiftui/view/toolbarvisibility(_:for:) I hope this helps.🙂

I reported something similar in March without any response: https://developer.apple.com/forums/thread/778640

Okay, I made it working exactly as I wanted, so I'd like to inform all people participating here, but also others who might see this while searching for similar content. The first stumbling block was making sure the application can actually send Apple Events in the first place. And in that regard I admit I should've listened better to @Etresoft and I apologize to him for not listening more carefully and dismissing his remark about hoops so that the app can actually send Apple Events too easily. It turned out that, even though the application is NOT sandboxed, com.apple.security.automation.apple-events entitlement is mandatory in the entitlements file. I couldn't assume it would be necessary even for a NON-sandboxed app, but it is. From my experience with executing AppleScript from another, sandboxed, application I remember that defining com.apple.security.automation.apple-events in the entitlements file and NSAppleEventsUsageDescription in the Info.plist file always go together and that's the case here too. S

The model appears to have not pasted correctly, I used the code block. So here it is again. import SwiftData //Model one: type of contract, i.e. Firm Fixed Price, etc @Model final class TypeOfContract { var contracts: [Contract] @Attribute(.unique) var typeName: String @Attribute(.unique) var typeCode: String var typeDescription: String init(contracts: [Contract], typeName: String = , typeCode: String = , typeDescription: String = ) { self.contracts = contracts self.typeName = typeName self.typeCode = typeCode self.typeDescription = typeDescription } } //Model two: the Contract @Model final class Contract { var contractType: TypeOfContract? var costReports: [CostReport] @Attribute(.unique) var contractNumber: String @Attribute(.unique) var contractName: String var startDate: Date var endDate: Date var contractValue: Decimal var contractCompany: String var contractContact: String var contactEmail: String var contactPhone: String var contractNotes: String init(contractType: TypeOfContract? = nil, costR

Thanks @Claude31, I have found stuff like that, yeah. For the section in my list that can be expanded and contracted, ScrollViewReader and .scrollTo work to keep you in the right place, so thanks for the hint. This is the code for the List, if it helps: ScrollViewReader { proxy in List { // Standard items ForEach(modelData.filteredItems.filter { !$0.archived }) { item in ItemRow(item) } // Archived items if(modelData.filteredItems.filter { $0.archived }.count > 0) { ListSectionHeader_Archived() .id(ListSectionHeader_Archived) .onTapGesture { modelData.archivedItemsExpanded.toggle() DispatchQueue.main.asyncAfter(deadline: .now() + 0.1) { proxy.scrollTo(ListSectionHeader_Archived) } } if(modelData.archivedItemsExpanded) { ForEach(modelData.filteredItems.filter { $0.archived }) { item in ItemRow(item) } } } } // List .id(UUID()) } I still can't figure out a way to stop the list from jumping back to the top when the device's Dark Mode setting changes. Why does SwiftUI think the data is different?

If that may help, I found this, but did not test, using ScrollViewReader, but you've probably found as well: Get the scroll position: https://stackoverflow.com/questions/62588015/get-the-current-scroll-position-of-a-swiftui-scrollview Set the scroll position (in .onAppear ?): https://www.hackingwithswift.com/quick-start/swiftui/how-to-scroll-to-a-specific-row-in-a-list Or would it be enough to set the selection when it exists ? https://stackoverflow.com/questions/74365665/force-deselection-of-row-in-swiftui-list-view/74368833#74368833

Thank you for ensuring that this issue is properly routed. That means a lot to us. I understand the risk involved in our approach, but that has to be balanced against the risk of not doing this. For us, our app resulting in a users disk continually filling over time is a far worse problem than any evident side effect of clearing the cache. As far as we know, this, like the vast majority of bugs we submit around wallpapers and screen savers, with either never get fixed, or only partially fixed. You can get the beta with the new cache cleaning feature here: https://testflight.apple.com/join/Bnbm6uJY Thank you.

Here's a link to download a sample code that will run a server with the Network API and with the GCD API. Instructions are included, in the Instructions.txt file, as you may have guessed. ;-) https://softron-downloads.s3.amazonaws.com/bvcwb546r7ret8hyj9tpm413a57zagf6qdf6h8/DualHTTPServer.zip Thank you! Pierre

I'm unable to reproduce it. It randomly has happened for me and other users. It only happened to me once. Sometimes rebooting the watch fixes it, sometimes it does not. The app was installed before updating to 26. This never happened before WatchOS 26. We also put out an update for 26, so that could be a factor too, but all we did was recompile it. The app is SwitchUI/WidgetKit. I can't imagine it's a problem with our app if it only happens randomly, but are there any things we should look for in the project that could cause this? This is what the icon looks like when it goes blank: https://imgur.com/a/SKo6w9D Thanks