They don't fix most reported bugs so not sure that indicates anything.
True. My point on the bug aspect is that it may not be a bug, but rather their intended implementation. Or perhaps it's only a partial implementation of a feature.
They don't fix most reported bugs so not sure that indicates anything.
Which doesn’t improve when you implement “always allow” 😀A problem with this, besides the annoyance factor, is that it may condition the user to quickly click “allow” every time the warning pops up… and so they may end up doing that reflexively if a malicious app actually does paste on its own.
Why not? It wouldn’t pop up for the (safe) apps you use regularly, so warning would be notable when it happens after downloading a malicious app (which pastes without the users intent).Which doesn’t improve when you implement “always allow” 😀
because being annoyed many will simply disable this security feature ”and they may end up” with ”a malicious app actually does paste on its own”. To paraphrase you.Why not? It wouldn’t pop up for the (safe) apps you use regularly, so warning would be notable when it happens after downloading a malicious app (which pastes without the users intent).
(Obviously, I’m assuming that “always allow“ would allow on a per-app basis.)
I’m not calling for it to be totally disabled, just for paste to be allowed on a per-app basis. If you’ve clicked “OK” ten times that day after pasting btw. Messages and Safari, you may quickly tap it without thinking when it pops up in SketchyApp69.because being annoyed many will simply disable this security feature ”and they may end up” with ”a malicious app actually does paste on its own”. To paraphrase you.
I get and agree that the granularity of this has to be improved - e.g. as long as you paste from the same website you shouldn’t be ask each time. But if you have opened a new webpage you should be informed - and you should have to authorize it, shouldn’t you?I’m not calling for it to be totally disabled, just for paste to be allowed on a per-app basis. If you’ve clicked “OK” ten times that day after pasting btw. Messages and Safari, you may quickly tap it without thinking when it pops up in SketchyApp69.
(As suggested in post #2 of this thread.)
I thought the issue was with apps, not specific websites. If you open a new Safari tab and are told “SketchyApp wants to paste” (b/c it’s trying to send you to a malicious page), you should get that warning – it’s not an action you initiated. If you open a new tab and paste a phrase you just copied from a trusted app (b/c you’re searching the phrase), you don’t need the warning.I get and agree that the granularity of this has to be improved - e.g. as long as you paste from the same website you shouldn’t be ask each time. But if you have opened a new webpage you should be informed - and you should have to authorize it, shouldn’t you?
Would love to know if this is true. I hopped off of os 16 beta 3 for these reasons:I. Think. It. Has. Disappeared. In. Beta. 4. …….
It sure is an annoying one. Reminds me of the early days of windows vista.I don't think it's going away as it was purposely implemented as part of Apple's security policies. It's not an issue in that sense, it's a feature.
I disagree and think you (and others) misunderstand the feature.
I disagree and think you (and others) misunderstand the feature.
My reading of that is that the permission check is meant to pop-up if the app tries to read the clipboard, by itself, programmatically, NOT if the user directly initiates a paste, which would be redundant. Apple's intent here is to stop apps reading the clipboard whenever they want, without the user's knowledge, not to get in the way of user's deliberately pasting.
So I do think this is a bug in their implementation.
The app isn't accessing the clipboard in that case, the iOS OS/keyboard/floating toolbar is. I appreciate this may seem like hair splitting, but at a technical level there really is a distinction. And this isn't a new idea that is obviously open to many interpretations (permissioning clipboard and similar APIs as used in application code has been done endlessly across multiple systems and OSes). It has nothing to do with the paste button on the toolbar; it's like pasting via cmd+v vs through a paste button in an app. One requires the app to access the clipboard, the other does not.And I disagree with that interpretation. It simply states, "requiring apps to ask users for their permission before accessing their clipboard." No caveats regarding user initiation. Nor is this identified anywhere as a bug, other than in user complaints.
The app isn't accessing the clipboard in that case, the iOS OS/keyboard/floating toolbar is. I appreciate this may seem like hair splitting, but at a technical level there really is a distinction. And this isn't a new idea that is obviously open to many interpretations (permissioning clipboard and similar APIs as used in application code has been done endlessly across multiple systems and OSes). It has nothing to do with the paste button on the toolbar; it's like pasting via cmd+v vs through a paste button in an app. One requires the app to access the clipboard, the other does not.
We shall see.
As an additional data point from beta 7: I only get the prompt when an app wants to paste automatically. Whenever I want to paste using the floating toolbar, I am never asked.
So did they solve the problem or does it only happen to some people?
I’m on beta 7, it still prompts me if I want to paste a second time, despite actively copying and pastingAs an additional data point from beta 7: I only get the prompt when an app wants to paste automatically. Whenever I want to paste using the floating toolbar, I am never asked.
So did they solve the problem or does it only happen to some people?
Having to bump this now that the official release is out. WTF. Is there a way to turn this off/disable it?!?! This is ridiculous.