Read the documentation of the use case for the property - for dictated or user-typed input. The UIBarButtonItem is none of the above. https://developer.apple.com/documentation/objectivec/nsobject/3197989-accessibilityuserinputlabels

func yougot(that right: Bool) -> (mine, mine, mine) { /* You should know once it is marked answered there is no way to unmark the post*/ }

This was my post, my issue, and my resolution. It's best you open a https://feedbackassistant.apple.com directly with Apple support.

Present day it’s no where to be found. If they post a profile in the site to enable the menu option that will fix this lingering problem.

One year after and still this issue is present. I upgraded from one device to a newer device the watch was wiped and paired to the new device. Now there is no way to get back developer mode on the watch.

@PASSTEWDIOS In the future, also use the correct tags.

Reimplement in SwiftUI using grids.

Just use swift package manager.

What I do notice with very large code bases is after the build is launched to the device, Xcode is still extracting strings after launch.

Xcode 15 introduces a new debugger architecture and new ways in how devices connect to Xcode, and it is 101 % buggy with us as the beta testers.

No, the entitlements were never designed to be used like that. Everything you need is in the build settings info.plist values.

APIs change during releases. This is why we test in between releases to see what side effects if any might have landed in our laps. But looking at the source implementation of AspectVGrid no ZStacks are being used so zIndex will never work. https://web.stanford.edu/class/cs193p/Spring2023/AspectVGrid.swift

@RodneyA, You were creating an error by not fulfilling the API requirement, someone gave you a solution to your problem, but you rejected the solution based on the requirements of how the .searchable(text:) modifier is supposed to be used. Either read the API documentation first and research how the APIs are to be used beforehand, and then when you have an issue, ask a question. No one is here to do your homework for you because this is what it sounds like.

@Claude31 He is not advising on how to bypass the review process. He is bringing to light the practices of an organization he once worked for that is doing this, and Apple does nothing about it when he mentions it here.

..