This exists for a very good reason.

It’s so if an app is showing a password or bank account number or other piece of sensitive information it doesn’t accidentally end up in a screenshot. I think there are other places sensitive information won’t show.

Bluesky, and apparently others, are abusing the functionality for advertising purposes.

I think it’s a good thing it’s there. This functionality should be easy for apps.

I’d say this is one for app review or an App Store rule. But we all know those are a total joke.

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.