I assume they both call into the same implementation. I could be wrong about that though. Testing the way this API behaves when released is unfortunately difficult. I understand why Apple limits review presentation but IMHO a call to requestReview: should at least return a BOOL so you know if the alert actually popped up. Not providing a way for developers to know for sure if the alert was actually shown makes proper rate limiting difficult.

I did patch my Docker install of Hermes to get it working with Xcode ACP. It does work a lot better than using Xcode 'Chat' agent. Because the agent is in a Docker container it cannot use Xcode tools though (at least not easily). I don't get an option to 'revert' a change the agent makes from within Xcode like I do in 'Chat' (presumably because the agent is not working with Xcode tools).

I should slightly walk back this part of this post: "I don't have any reason to have fieldEditor set to YES so just removing that line fixes the issue." On further testing I discovered that I actually do have a good reason to turn this on. For what I'm trying to accomplish 'field editor' behavior is actually desired (for example I want to end editing when a tab key is pressed). I should be able to reimplement the field editor behavior I want without too much trouble though.

If you select in the menu bar View -> Inspectors -> Connections If you have a property with IBOutlet written in the interface of whatever object you have selected in your storyboard currently (for example the view controller) you should be able to wire the outlet from the Connections Inspector (in the 'sidebar' on the 'right' side).

Thanks!

Sure does. Thanks!

I was just filing a detailed feedback but I guess it wasn't meant to be. Feedback Assistant started to hang after I typed everything and I had to Force Quit. There is some Autolayout infinite loop in textviews/textfields/TextKit. All the data was lost it didn't save the draft!!! This dataloss bug is really frustrating. Also ran into this in Xcode recently when editing and the source code I typed is lost because the document isn't autosaved before we get trapped in the infinite loop!

Thanks!

"The only thing the new method does is require Swift." And require a view controller parameter which is completely ignored and unnecessary.

Thanks. Sorry for the multiple posts.

Great news!

Was up too late night. Just to add...as I can't edit the post (guess there is some time limit on edits) but the color space returned by CGColorSpaceCreateDeviceRGB() should be set to a variable and released with CGColorSpaceRelease instead of directly assigning the returned color space to rgbFormat.colorSpace like shown above.

I don't see how I can publish it with this feature being so broken on the latest version of iOS. I don't see how it helps me to release something that doesn't work. Not sure how they are doing versioning..maybe using a lower "base sdk" would cause AVFoundation to use an older codepath that would avoid the issue but then I'd lose all iOS 17 symbols and would get my codebase in a huge mess. I have doubts that that would work anyway.

And on iOS version 17.0.3.

I meant to say "Include the view controller's view that you are presenting from in the array."