“sign in with twitter” works well when my application is set to “read & write”, but I when I set the application type to “read” then the “sign in with twitter” stops working and the twitter log-on screen stays stuck in a loop.
100% repo over here. could someone else test this and confirm?
is this as designed for the API? If so I’d like to suggest a change: I just need users to sign-in to my app using twitter, but my app does not need “write” access to do anything on behalf of the user… however if I need to ask for write permissions just to authenticate it is likely that this will turn away some users from signing in.