This is a continuation of this thread:
As there are reports as recent as last August that suspended Twitter users cannot access the applications that they have registered – despite both applications having different policies – the next best course of action would be to test this scenario for a client application and provide a way for a recovery/backup authentication.
What is the best way to test Twitter Oauth authentication with a suspended/banned user?
Thank you in advance for any assistance you can provide.
If it helps test things, there’s a reliable way to suspend your own account (obviously, use a brand new one specifically for this). If you make an account, and then set the birthday to something < 13 years old, you will get suspended, i think this still works but i haven’t tried this (last time i accidentally set the birthday on an organization account, which made it a year old, and twitter does not allow children to have accounts).
That way you could authenticate your app with this new user, get suspended and see how things work out with your app, and how you can work around that.
1 Like
LOVE!!! That is an EXCELLENT idea @IgorBrigadir and I can confirm that I have been victim to that very “feature” with my project account when I initially signed up for Twitter in 2020. I put the birthday as my start date and was instantly suspended. 
I should have thought of that.
I very much appreciate your assistance here, as well the creative thinking to get me unblocked. 
1 Like
