Request failed with http status code 503

The code submitted is the entire project. Sorry - I don't have a spare device to try the beta.

Thanks for that, have you tried iOS 26.1 beta? What results do you get there? Have you tried disabling Liquid Glass? https://developer.apple.com/documentation/BundleResources/Information-Property-List/UIDesignRequiresCompatibility Do you have the project showing the issue? Albert Pascual
  Worldwide Developer Relations.

Thanks for the post. We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to the Apple Developer Program. For your question, please contact the Apple Developer Program Support Team. https://developer.apple.com/help/account/ We hope this information is helpful to you. Albert Pascual
  Worldwide Developer Relations.

I can see in the IORegistry that my sentinelProperty is applied to the interface, but bInterfaceProtocol is not. ... I expect that tweaking the bInterfaceProtocol value on the IOUSBHostInterface at driver match time doesn't make any difference. That's unfortunate. So, looking at our code, it turns out that AppleUSBHostMergeProperties will actually only work in one of two ways: If a property is absent, it will add that property. If a property already exists AND that property is a dictionary, then it will merge/modify your dictionary into the KEXT dictionary. I hadn't looked closely at this today, but, ironically, that's almost certainly why many properties at the root get merged into a dictionary by the nub layer, as it then allows those properties to be modified. In this particular case, that modification point would be the USB Device Info dictionary of IOUSBMassStorageDriverNub. The good news here is that I think a codeless DEXT might still work for this. I haven't had a chance to test this, but my

OK, I had a conversation with a Foundation framework engineer and my colleague Kevin Elliott, and would like to confirm that the behavior the guide describes is right: On iOS (and its variants), you need to call startAccessingSecurityScopedResource before accessing a URL from a file picker, and match with a stopAccessingSecurityScopedResource call when you are done with the file. On macOS, you can access a URL from a file picker without calling startAccessingSecurityScopedResource beforehand, but need to call stopAccessingSecurityScopedResource when you are done with the file. This is so that existing code written before sandboxing being introduced can still consume URLs from a picker. Failing to call stopAccessingSecurityScopedResource will leak a security scope resource. With this in mind, now to your questions: From my testing, iOS does not provide the same implicit startAccessingSecurityScopedResource when using UIDocumentPickerViewController. Is this a correct observation/per design? Co

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

@cloudleadanis Nice job!! Happy coding! Albert Pascual
  Worldwide Developer Relations.

So, let me start here: But there are problems with clicking on recorded audio on Bluetooth devices (all noise or no sound during playback). The thing to keep in mind here is that Bluetooth has two entirely separate audio mechanisms, which have very different levels of audio quality and behavior: A2DP -> Playback only, higher quality, modeled as music player. HFP -> Play and record, lower quality audio, modeled as a phone. Switching between those modes isn't immediate, so manipulating the audio session configuration can change how audio sounds and/or cause odd glitches. These issues will also be worse in the background, where your app no longer has direct/less control over the audio session state. In terms of your code, there are a few different issues: (1) AVAudioPlayer should not be used for exactly the same reasons you should not use AVAudioRecorder. All your playback and recording should be going through AVAudioEngine. (2) This code here is wrong and doesn't really work, at least no

Should I be doing as I currently am, where I create modelData as a global let so I can access it everywhere, or should I pass it through the view hierarchy as an Environment variable, like @Environment(ModelData.self) var modelData: ModelData? Bear in mind that some functions are outside of the view hierarchy and cannot access modelData if I do this. Various things like controllers that need access to values in modelData cannot get to it. Since It's an observable object, make it a State at the App level and pass that down your view hierarchy using environment modifier. You can also have a singleton instance of ModelData if you only ever need a single instance of the object. We’ll need more information to fully understand the issue. If you encounter the same problem with the relevant code in a small test project, please share a link to it. This will help us better comprehend the situation. If you’re not familiar with creating a test project, refer to Creating a test project.

It's a Mac app built using Mac Catalyst based on our iOS app code. Customer complaints are only for our Mac app, not our iOS app. It seems like (our guess) macOS uses some set of app data (e.g. app name, location, entitlements, etc) to determine if macOS should create a new entry in the Settings > Privacy & Security > Local Network list. Could some difference between a prior version of our app and our latest version of our app be causing the multiple entries in the Local Network list? Why would our app not actually have Local Network access even though all of the switches are turned on? Any thoughts?