@nighthawk I mean sure 😛 But it’s a pretty meager gaming PC if you ask me.

I think this is their console. Now bring on the Steam Tower with a big honking GPU. Optimize the hell out of it to their OS. Make the gaming PC no one else can.

@gnyman Sandboxed apps cannot do it at all. Or install background items (basically old launch agents). So MAS apps cannot do these things.

But these are literally the two features I’ve been asked 90% of the time.

@gnyman Of course there’s an admin password prompt before macOS lets the app do that.

Mac App Store mandates sandboxing which limits the highlight features in this release to the direct download version.

I’ve documented the differences at https://proxygen.app/docs/license/#direct-download

There are lots of little improvements across the app, such as options for autosaving document and enabling proxy at launch. Hex view now colors bytes making it easier to see binary content.

As always, it’s all described in more detail at https://proxygen.app/docs so have a look!

The system HTTP/HTTPS proxy address is configured to first Proxygen listener address when you launch the app and reverted back to previous settings when the app quits.

Proxygen now automatically installs its CA certificate to login keychain and trusts it […]

[Original post on infosec.exchange]

@piidr0 Right?? 🤩

Okay I think I do now have the workaround for this:

Configure your table view cell with a .clear() background configuration *after* you’re done with all other setup that could potentially revert it into non-configuration mode.

if #available(iOS 18.0, *) {
cell.backgroundConfiguration = […]

Ooh this time I got a proper stack trace of the crash

*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid parameter not satisfying: configuration != nil'
*** First throw call stack:
(
0 CoreFoundation 0x00000001804f71d0 __exceptionPreprocess + 172 […]

Here’s the exception as captured by Xcode. I think it has to do with UITableViewCell.backgroundConfiguration but haven’t nailed down the fix just yet.

Okay I’ve now traced it down to there being any kind of UITableViewController presented as sheet. That crashes but nothing else.

So maybe the “configuration” here is referring to UITableViewCell and not UIButton

Invalid parameter not satisfying: configuration != nil

Interesting… the crash goes away if I remove the sheet presentation from this message view. It could have something to do with how the sheet changed in iOS 26 and 26.1.

I noticed that it takes a moment for the buttons at the bottom to become active, which didn’t happen before.

I happened to find this blog writeup that mentions this exact error message, so thinking perhaps UIKit internally uses UIButton configurationUpdateHandler where it shouldn’t. I’m not defining that handler anywhere in my code.

https://sarunw.com/posts/dynamic-button-configuration/#run-time-error

It was awesome 🔩🚀