Feature need: User WILL take screen shot (Needed API)

Originator:lordandrei
Number:rdar://22518462 Date Originated:9/1/2015
Status:Open Resolved:
Product:iOS Product Version:iOS 9+
Classification:New (Feature Req) Reproducible:
 
Summary:
There is an API notification that a user has taken a screen shot. It is HIGHLY needed to have a manner with which to be warned in advance to make adjustments. From a business point of view there may be sensitive or copyrighted material on the screen that must NOT be copied in any form.

By not having this API intercept point the developer can inevitably be liable for information that they are required to display but not permit to be copied.

Examples of Apple doing this are:
in screen shots of certain video assets when playing thru iTunes.
the MFI documentation where the document is watermarked, locked, and screen shots are unavailable.

As a developer my option is to not display the information (defeating the purpose of the app) or run the risk that a user will screen shot and release information otherwise protected. Since there is limited information about a user available (Apple's admittedly great privacy practices) it does not afford easy watermarking on the fly of information.

With this API/Notification, the developer can black out / water mark screen composition that a user is attempting to capture.

This theoretically could be added with an enhancement to a UI View that allows the user to set a 'no screen shot' delegate or image.

Steps to Reproduce:
screen shot in an app

Expected Results:
Preferred (not expected)
screen shot an app with a protected image
image can be blacked out for screen shot

Actual Results:
image capture with full screen intact.

Version:
iOS 9.0 (13A4325c)

Notes:
This is a VERY HIGH / ESSENTIAL need.

Configuration:
Any

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!