Yep, it was the cache clearing that solved the problem. I did a deep scan with malware detection, but both came up clean. Weird problem...can’t imagine why there’s a tie-in with the cache.
can’t imagine why there’s a tie-in with the cache.Because you were logged in. Bet you aren't anymore and that the request will pop up again when you log in again.
I'm an infrequent twitter user, but IIRC there's an X or a tiny "no thanks" somewhere on the request you can use to close it without giving them a phone number. Been a while since I looked at twitter, though, so maybe they're getting more insistent.