4 ms·
The problem is that iOS doesn't differentiate between a call that merely checks for the presence of a clipboard entry (e.g. so you can enable "Paste" in a menu/
by riskable 6y ago
The problem is that iOS doesn't differentiate between a call that merely checks for the presence of a clipboard entry (e.g. so you can enable "Paste" in a menu/submenu) and actually copying the contents of the clipboard.
The workaround (for legitimate apps) is to simply always keep that "Paste" option enabled--even if the clipboard is empty. That way you won't freak out your users and only suffer the most minor of usability consequences.
Having said that I don't think TikTok has any relevant functionality such as enabling a "Paste" option so... Most likely nefarious!
- selsta 6y agoiOS differentiates between this since iOS 10: https://developer.apple.com/documentation/uikit/uipasteboard/1829416-hasstrings https://developer.apple.com/documentation/uikit/uipasteboard... Also iOS 14 has new clipboard related APIs to further check the content without actually accessing it.
- BoorishBears 6y agoIf iOS 14 adds new APIs to check, then I wouldn't be surprised if the codepath hasStrings uses triggers the warning The purpose of hasStrings was performance not indicating intent, so that wouldn't be surprising
- pininja 6y ago> I don't think TikTok has any relevant functionality Does pasting text into a video as an annotation require “Paste” to be enabled in this way?
- ladberg 6y agoI believe any time you paste with the native keyboard UI up it doesn't go through the app. You only need to snoop the clipboard if you want to proactively use the data without having the user paste.