4 ms·
A bunch of comments here are assuming this is something intentional on Google's part. Simply from the error message alone, it's obvious that this is a bug. As
by crazygringo 6y ago
A bunch of comments here are assuming this is something intentional on Google's part.
Simply from the error message alone, it's obvious that this is a bug. As well as from how easy the workaround is.
Google might do many things wrong intentionally, but I see zero evidence this is one of them. Just a bug, folks.
- mavidser 6y agoYeah, the comments seem to imply a case of 'commenting before reading the content' behavior to me.
- arnaudsm 6y agoThis is a feature: FLAG_SECURE is real and used by many apps. i.e. Chrome's Incognito mode. Sure, you have workarounds for power-users, but Google is locking the Android ecosystem progressively for regular users. Just like the Manifest v3 for Chrome. Maybe Google is doing the "Embrace, extend, and extinguish" strategy that worked really well for Microsoft in the past.
- crazygringo 6y agoDo you have any evidence for that? The thread is about behavior caused by a presumably erroneous ".nomedia" file residing in certain users' screenshot folders. The FLAG_SECURE feature doesn't appear to have anything to do with that. Two entirely separate things, unless you can show otherwise.
- arnaudsm 6y agoThe thread describes a bug indeed, but the feature really exists. Quoting the Android SDK reference : "FLAG_SECURE [...] Treat the content of the window as secure, preventing it from appearing in screenshots" [1] Try to screenshot while in Chrome's incognito, you'll see it in action. [1] https://developer.android.com/reference/android/view/WindowManager.LayoutParams#FLAG_SECURE https://developer.android.com/reference/android/view/WindowM...
- Dylan16807 6y ago> Two entirely separate things, unless you can show otherwise. Read the error message! It's clearly related to the real feature, which means the bug can't be "entirely separate".
- kllrnohj 6y ago> but Google is locking the Android ecosystem progressively for regular users. FLAG_SECURE has existed for as long as Android has. It can't possibly be evidence of locking down the ecosystem progressively as it's always been part of the ecosystem.
- umvi 6y ago> "Taking screenshots isn't allowed by the app or your organization." To me that implies Android supports individual apps locking down your device so that you can't use certain features (like screenshots) while the app is open.
- m45t3r 6y agoiOS and PS4 also does have this block if the developer wishes to do so (generally for "security" reasons).
- grenoire 6y agoor for DRM reasons...
- Spivak 6y agoNah, the DRM on iPhones is much stronger than screenshot protection. When you’re watching DRM protected media you can still take screenshots but the part of the screen that has the content will be blacked out. Basically all forms of reading pixels from DRM windows just return nothing.
- userbinator 6y agoThat's "hardware overlay", not exactly DRM (it's been there on PCs for a very long time) but certainly leans in that direction.
- Polylactic_acid 6y agoIt works different, you can always screen record but apps can detect it and stop playing content while the screen is recording.
- machello13 6y agoI don’t think iOS does have a way for apps to disallow screenshots. Do you have a source?
- solinent 6y ago> it's obvious that this is a bug If someone were to prevent screenshots intentionally, and I had mal intent, I would make my best effort to make it seem unintentional.