IOPresentment framework

Take this as well-intentioned advice, and not some busybody shaking the rulebook in your face.

If you intend to use private API, and aren't just curious…

• It's a violation of the developer license. But I can't see anyone getting excited about it if that's all it is.
• Apple keeps a framework private when it does not want to make it part of the operating systens' API contract. The preconditions, inputs, side effects, outputs, and existence of private frameworks are subject to change with any point release, or even with changes in hardware, hardware state, time zone shifts, race conditions, internal configuraton, installed applications, or system/user data.
• If you want to fool around, understand that you are placing a bet on not destroying data or bricking the device. Unlikely? Sure; it's only a slight chance of a high cost.
• The App Review bots can easily detect when an app hooks directly into private API. At best, the app will be rejected. At the very worst, but unlikely, if there's any whiff of malware, now you have to worry about the license because Apple has you on a legal hook. Again, very unlikely, but our world is full of unreasonable people.

It's no skin off my nose if you want to explore, but you should do it with your eyes open.

I don't believe it is a violation of any NDA to discuss Apple /S/L/PrivateFrameworks in the Developer Forum for which I paid good money for.

Don't confuse the use of undocumented APIS in IOS Apps with macOS. The former tends to be much stricter.

Again. Discussion of this is not forbidden, is it? Have you checked the PrivateFramework folder, do you mean all 600 or so are barred from discussion here, in a developer forum...

And yes, I've been at this for a while so undocumented APIs run their own risk, if you choose to use them. And no, I'm not trying to fool around...