I've done this before, but it was a long time ago and I don't remember the caveats to making this work, nor do I have access to that project any longer so I can't really be of help. But I do wonder - can you just use one UITextView and concatenate all of your text content together? I do remember due to performance reasons this is what I eventually moved towards.

Not sure how much it helps but it might be worth boosting this thread, which already has some replies: https://developer.apple.com/forums/thread/779006?answerId=837660022#837660022

Trying to think of potential workarounds here for the moment. I know there are command line tools that can be used to parse through Memory Graphs, but that requires a memory graph which currently can't be made. I guess depending on what you're doing need to rely on print statements and the like. One interesting thing is that jumping back to Xcode 16.2 and verifying the command line tools version is correct doesn't work for me now either.

I do believe this to be an SDK bug, or at the very least a documentation bug, so I filed FB13724367

There's a couple of problems with your code: Assuming that self is a View Controller, you're only looking at its view property's subviews, and not its entire hierarchy. So for example, if view contained a Stack View of buttons, those buttons would be missed. You'd need to write a recursive function instead. if views == UIButton is not the correct way to check if a view is a button. You'd probably want to instead downcast it as such: if let button = subview as? UIButton In your question you ask about to iterate all views in the running app. If the code above was correct, it would only iterate the buttons in whatever self is, which I presume is a single view controller and not the entire app. However, there is a way to customize appearances in the entire app, using UIAppearance proxies. But this is only for properties that are marked with UI_APPEARANCE_SELECTOR. In the case of UIButton, that includes properties like titleColor and backgroundImage, not isPointerInteractionEnabled.

Seeing this too. Filed FB9801719 about it