The problem persists. However, I cannot recreate it with Chrome on my Android phone. I’ve had the button tested by a friend with a Nexus 7 and he hasn’t encountered any problems.
I’ve quite aggressive caching in place (Cloudflare and a local plugin) and its possible my Nexus 7 is hanging on to the old code - however, I believe the issue may not be strictly button related. The problem could be with how the Nexus 7 reacts to Twitter URLs (typically asking whether the user wants to progress in Chrome or switch to a Twitter app).
Given that the test of the new code passed clean on at least one Nexus 7 I’d be happy for you guys to mark this as solved. I’ll keep you in the loop if I pick up any other reports of Android devices struggling.