file uri scheme

Thank you for your post. If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, make sure to: Provide specific reasons why you believe your app complies with the App Review Guidelines. Submit only one appeal per rejection. Respond to any requests for additional information before submitting an appeal. Once you have submitted the appeal we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they've completed their investigation.

Is there a guide for macOS on the steps you describe at the end, that is on how to allocate a swapfile, Just to be clear, you're not actually creating a swapfile as such. Your mapping a file into memory which means, assuming the mapping MAP_SHARED, the VM system will then use that file as the backing store for that memory range. That gives you basically the same behavior as swap backed system memory, but it isn't ACTUALLY the same as using true swap (for example, you'll be writing the data directly back to file, so there won't be any compression or VM level encryption). mmap that swapfile into memory, mmap is a standard Unix API, which means we don't really provide specific documentation for it, however, there is an old code snippet here showing how it works. One note I will note is that some of the recommendations there aren't really relevant anymore, particularly any recommendation about limiting mapping size. Those concerns where driven by the limited 32-bit address space, but th

I also have the same problem on a MacStudio M1Max (and not on a MBP M1Max) after upgrading to Xcode 26.1.1: no MetalToolchain accessible from this application. Running on Tahoe 26.1 Running today xcodebuild -downloadComponent metalToolchain gives: `Beginning asset download... Downloaded asset to: /System/Library/AssetsV2/com_apple_MobileAsset_MetalToolchain/68d8db6212b48d387d071ff7b905df796658e713.asset/AssetData/Restore/022-20369-066.dmg Done downloading: Metal Toolchain 17B54.` Then when I run xcrun metal --version, I got an error message: error: error: cannot execute tool 'metal' due to missing Metal Toolchain; use: xcodebuild -downloadComponent MetalToolchain Last when I run: xcodebuild -showComponent metalToolchain, I got: 2025-12-12 18:34:14.045 xcodebuild[27394:1591467] IDEDownloadableMetalToolchainCoordinator: Failed to remount the Metal Toolchain: The file “com.apple.MobileAsset.MetalToolchain-v17.2.54.0.BttmuJ” couldn’t be opened because you don’t have permission to view it. 2025-12-12 18:3

Thank you for your post. If you disagree with the outcome of the review, we recommend submitting an appeal to the App Review Board. When filing your appeal, please ensure that you provide specific reasons why you believe your app complies with the App Review Guidelines. Additionally, please submit only one appeal per rejection. It is also important to respond to any requests for additional information before submitting an appeal. Once you have submitted the appeal, we can escalate it to the App Review Board for review. The App Review Board will contact you directly as soon as they have completed their investigation. App Review is not in the forums, only engineers are answering questions in this place is for questions about the API and frameworks. Use this link for the app review: https://developer.apple.com/contact/request/app-review/appeal/ Good luck and hope to see your app in the store soon. Albert Pascual
  Worldwide Developer Relations.

Apps cannot initiate any AV sessions while in the background, and definitely not when they are not running. Critical alerts are handled by the system, and the app has no control over the sounds once the notification is created. What you can do is, perform the TTS beforehand, create a sound file with the required speech, and use that sound file as the sound for the critical alert. While you can technically do this in a Notification Service Extension - to create the sound file locally - it might be a practical challenge due to the memory and time limits imposed on extensions. The solution I could suggest would be to have your push notification server to create the TTS sound file, pass on the URL for this sound file in the notification payload, and then have your Notification Service Extension to download this file and reconstruct the critical alert notification using the downloaded file. If you want to try to create the sound file locally,

I am including a picture of the contents of the RiotPad ipa zip file (minus all graphic files) that was created for upload that is giving these errors.

First up, you’re correct that there’s a contradiction here: Apple has effectively deprecated the file-base keychain in favour of the data protection keychain. But the Personal Team limits, which come from iOS, run counter to the expectations of macOS developers. I don’t have any answers for you on that front, but if you file a bug describing this contradiction and post the bug number here, I’ll make sure that the relevant folks see it. Coming back to your real issue, there’s a lot to unpack there and I don’t have time to dig into it all. However, you seem to have bumped into a pretty fundamental limitation: You want the system to protect your item such that only your program can access it. But you’re not giving it any code-signing credentials to do that. Something has to give. The file-based keychain has a bunch of legacy access control centred around code-signing requirements — see TN3127 Inside Code Signing: Requirements — so that’s one thing you might explore. But that still requ

So, I got some more time to look at this today and need to change my answer a bit. Let me actually jump back to here: All the documentation I was able to consult says that macOS is designed to use up to all available storage on the startup disk (which is the one I am using since I have only one disk and the available space aforementioned reflects this) for swapping, when physical RAM is not enough. Did you actually see this in our documentation and, if so, where? If any of our modern documentation actually says that we do this, then that's something I'd like to clean up and correct. So, let me go back to the idea here: macOS is designed to use up to all available storage on the startup disk That's the classic” UNIX system machine swap and, historically, it's how Mac OS X originally worked. However, the downside of this approach is swap death in one of two forms: Soft, meaning the system has slowed down to the point that the user is now no longer willing to use the machine, even though it technically still wor

@viktor_runcoach Thanks for providing me the FB number for the filed bug. I see you produced the trace files. I don't see what's the last version of iOS you have used to test if still happens. Albert Pascual
  Worldwide Developer Relations.

I created an App Intents extension (AppIntent + @Parameter(file)...) but the app still does not appear in Shortcuts “Share with App”. I suggest going the App Intent route, but the way you invoke it from a Shortcut is a bit different. When your app is installed, iOS will be informed of the intents in your app, and will display them as dedicated actions in the Shortcuts app that you can choose to use in a Shortcut. It replaces picking a system action like Share with App, and will likely give your customers the most flexibility with how they can interact with your app through Shortcuts. As to making your app appear in the Share with App menu, take a look at implementing an Action Extension. — Ed Ford,  DTS Engineer

Albert, I have also filed a bug report FB21320686 I have attached a trace and a project file to reproduce the issue. ray_cai, what has your fix been? Does removing the legacy launch image fix the issue?

Please file an enhancement request using the Feedback Assistant so that your request can be seen by the appropriate decision makers. If you file the request, please post the Feedback number here so we can make sure it gets routed to the right team. Please note that filing an enhancement request does not guarantee Apple will add any requested functionality to Apple products in the future. However, with that said, filing an enhancement request is a good way to get your ideas in front of the folks who make decisions about that sort of thing. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?