Ok, that helps. It sounds like the idea is that we consider increasing the limit to get better performance, rather than decrease it because it's already low. Do you have a percentage you recommend vs. physical memory?

Still a bit confused. If the intermediates are volatile, then I would think that they wouldn't matter for the memoryLimit budget, right? So the memoryLimit is for things other than intermediates? If so, what fraction of real memory do you advise on iOS?

What use cases or types of images benefit from disabling highlight recovery?

Does Draft Mode change the size of the image (it does for some formats in RAW 8)?

Thanks for the information. I already have code to prompt the user for folder access and to save the bookmark. Yes, I could ask them instead for a save dialog for just the XMP file, but as you point out, that's not better from an experience standpoint. This API has been on Mac since 10.8 and the underlying OS / file system are similar between Mac and iOS, AND the security / privacy benefits of having this API on iOS are clear. Can you provide some insight as to why the API is hard to implement or (perhaps) not important to implement? At least when customers ask me why I have to do this, I can give them a proper answer.

OK - I was able to upload three different sysdiagnoses: iPad -> Mac mini (works) Mac -> UGreen (works) iPad -> UGreen (doesn't work) - just to give an updated one

I just made one. But Feedback Assistant is down, so I will have to add it when it comes back up.

I should mention that my customers are reporting the same thing with their UGreen, so it's not specific to my unit.

How would I collect packet captures? I don't have experience with that. There is a feedback already in the system. FB22955130

Yes, it's mounted using SMB. The NAS supports either SMB2.x or SMB 3.

I found it. I was looking in the application delegate, but needed to look in the scene delegate. The method is func scene(_ scene: UIScene, openURLContexts URLContexts: Set)

This appears to be resolved in Sequoia Beta 5.

Popovers can be applied to Toolbar items on Ventura and later. There is a new API for that - see UIPopoverPresentationController // Accepts UIBarButtonItem as well as NSToolbarItem in Catalyst. @available(iOS 16.0, *) open var sourceItem: UIPopoverPresentationControllerSourceItem?

I made a clean install of Ventura + Xcode 14.1 on another machine (intel based) and it builds / debugs fine. So it's not a problem with the way the project is set up.

I am having the same problem on Ventura with Xcode 14.1. I tried the command listed by Quinn, but codesign just reports a usage message instead. I added a colon which apparently is deprecated, but it does produce some output (I am using the path to extension stored in the container app as built by Xcode). I see com.apple.security.get-task-allow. What can I do to get debugging to work? % codesign -d -v --entitlements :- (path to extension inside container app) Format=bundle with Mach-O thin (arm64) CodeDirectory v=20500 size=93466 flags=0x10000(runtime) hashes=2909+7 location=embedded Signature size=4790 Signed Time=Nov 27, 2022 at 5:30:25 PM Info.plist entries=24 Runtime Version=13.0.0 Sealed Resources version=2 rules=13 files=401 Internal requirements count=1 size=208 Warning: Specifying ':' in the path is deprecated and will not work in a future release <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "https://www.apple.com/DTDs/PropertyList-1.0.dtd"><plist version="1.0"><dict><key>com.apple.security.app-sandbox</key><true/><key>com.apple.security.application-groups</key><array><string>6MR872QP3J.group.com.gentlemencoders.RAWPower</string></array><key>com.apple.security.files.user-selected.read-write</key><true/><key>com.apple.security.get-task-allow</key><true/><key>com.apple.security.network.client</key><true/></dict></plist>