I don't have an issue with BSky's use, but I regularly run into the functionality's abuse elsewhere, such as multiple of the biggest Thai banks' apps where every screen in the app entirely blocks screenshots (iOS). Doing a P2P money transfer and want to send a screenshot to the recipient for them to confirm their info before you hit submit on a non-reversible transfer? Blocked. Want to screenshot a promotion's terms for proof or a personal reminder? Blocked. It's even worse as multiple of the biggest brick-and-mortar Thai banks wholly dropped web access and are now smartphone-only. (Or more obscure, want to translate a single-language screen into another language? Blocked.) Etc.

I want to take a screen shot of the transaction I just did. Can't because some ahole decided for me that it's too sensitive information and blacks out the whole screen. this API is stupid without control in settings of the os

OTOH, I might very well want to take a screenshot of my own bank details, transactions, or other sensitive information. It's annoying that my information is being protected from myself.

It's MY phone that I paid over $1000 for. Let me choose what is exposed and what is not.

The OS could draw an ugly censoring block over the sensitive information. That would protect the user's privacy when needed but also prevent apps mis-using the feature like this.

"accidentally end up in a screenshot" --- how often do you even take a screenshot on a phone, much less accidentally?

Account numbers appear on checks. They are not exactly secret, and if I want to take a screenshot of one, I should be able to.

I don't think they're abusing functionality at all. I don't think screenshotting a skeet should, by default, leak the follow state of the user taking the screenshot, which is what would happen without the secure input swap

"Secure inputs" take many forms, and it doesn't feel like this is abuse in any meaningful way

But how can I take a screenshot that intentionally shows the password or whatever?

If it's to prevent accidents, it should just prompt user to confirm saving the screenshot with sensitive information.

As it is, it is just an annoyance that requires you to do stupid workarounds like taking a photo of your screen.

Imagine if a password manager didn't allow you to copy the password since you might accidentally paste it somewhere incorrect.

If a dev forgot to obfuscate the password and rendered it as plain text on the screen, then what are the chances they remember to program the blur into this screenshot api hook. Or why not add an alert, “what me to blur sensitive info? Yes/No”

I can always just pull out my second phone to bypass all this shit.

Which is why everyone should root the their phone to turn this kind of shit off.

The app doesn't know. It just produces a widget tree, and the OS-provided renderer renders it this way or that way. In particular, it chooses not to render controls marked as "security-sensitive" when the rendering is intended for a screenshot; it could instead put empty boxes in their place, etc. The app has no idea and no control, AFAIK.

Reddit has a toggle in its settings to disable it. X, too, I think.

Personally, I wish iOS didn't even facilitate this.

edit: to be clear, I don't think iOS should notify the app at all. The app could register areas as "invisible to screenshots" perhaps - I'm torn on that functionality.

iOS allows something similar because this is iOS. iOS allows something exactly the same because this article is about iOS.

No, it's about saving the bank money - and what costs them a lot of money is the average person being fooled into sending people their account information easily.

I want those things included, at least by default. A screenshot normally captures the user’s screen size, brightness, zoom level, font choices, etc.

It is often important to people that the screenshot is an accurate record of what was on the screen.

The effects of cramming 2 separate workflows and 5 features into one thing called "screenshot" because anything else would end up with something too complicated for users to understand the interaction (sarcasm that figuring out what the behavior is locked to in these scenarios is just as confusing).

While we're at it, this "share" containing the copy/paste flow is the exact same kind of thing. And screw whatever logic decides to copy the URL of an image instead of the actual image sometimes from Safari when I select to copy it!