Im getting the same isalah. Twitter are aware of the issue. its during
handshake for creating new tokens and maybe linked to several other
OAuth issues that came to attention this morning.

Im hoping it will be fixed shortly!

Reply via email to