Pasteboard counter exists to help apps to not ask again about the same item in the buffer.
replyAnd nothing stops from using reset it every day.
Why do you need a count for that? Couldn’t they just generate a UUID every time the clipboard changes?
replyAllowing an app to access the pasteboard without the user explicitly pasting into the app is weird to me. Maybe the thing I have in the pasteboard is not for this app but left over from use in another app. Since there's no easy way to clear the pasteboard, this will happen often. Maybe it's because I'm not an app dev that this doesn't make sense to me????
replyiOS will ask for pasteboard permission every time an app wants to read the actual contents.
reply& we can set ask each time, always allow, never allow per app.
replyWould you elaborate on both points?
replyAny way to reset it as an end user? (Not enough awareness of the issue for search engines to find much.)
I think something like a per boot delta added to a (per app?) random base would preserve such functionality.
replyJust generate a new random value instead of incrementing
replyEven that is overkill if all you're interested in is if a change occured.
replyWhat’s an easier way? I’m assuming they want the app to be able to detect when “a”, was copied, then “b” and then “a” again, so just looking at the value probably isn’t enough.
replyI don’t think an app should have access to that (without some sort of very special permission).
replyGraphene is way ahead of this
replyApps on grapheneos can see a list of other apps in the same profile.
reply