Authenticate -> Authorize -> Authenticate loses DM access

justunfollow · 2011-11-01T19:06:00.000Z

“Trying to narrow the problem area down to whether this only happens when the login sequence is additionally invoked within the OAuth sequence”

Yes, that’s the exact case when this happens.

justunfollow · 2011-11-02T14:15:00.000Z

anything on this?

episod · 2011-11-02T18:13:36.000Z

Still investigating; a bug is filed with our team. It won’t be fixed in the extremely short-term.

Out of curiosity, for which product features does JustUnfollow utilize DM permissions?

justunfollow · 2011-11-02T19:59:00.000Z

it’s not for justunfollow… it’s for our new app http://www.buffr.com

justunfollow · 2011-11-02T20:10:00.000Z

I presume this bug would affect all apps that need RWD and provide ‘sign in with twitter’. Most wouldn’t realize the error, or probably end up prompting users for DM access every time this bug occurs

But I’m also interested in seeing how you guys end up fixing this bug. Since the current sign in window explicitly mentions that "Direct Message’ permission would not be granted, my suggestion would be to specify somewhere informing the user that this holds true only if DM access is not already granted.

justunfollow · 2011-11-09T13:59:00.000Z

Hi,

Sorry to be pestering you but any news if this would be fixed soon?

episod · 2011-11-14T14:50:05.000Z

There’s no news on with this will be fixed yet; it’s a filed bug awaiting prioritization. I will continue to look after it to see that it gets prioritized.

justunfollow · 2011-11-14T18:39:00.000Z

thank you so much

CodeInChaos · 2011-11-15T06:14:42.000Z

I’ve noticed this problem as well, following the same flow as @justunfollow …

CodeInChaos · 2011-11-15T06:23:39.000Z

also another by-product of this issue is that the /authenticate screen will now always prompt the user to sign in whether they’ve previously approved the application or not, which breaks the whole “login with twitter” experience …

kmore · 2011-11-26T21:26:00.000Z

Would really like this to get addressed. Any updates.?

A fix would very much help us out on a project we’re nearing the end of.

Thanks guys.

karimawad · 2011-11-27T16:35:01.000Z

I’d also like to find a resolution for this. Excited to get the login flow worked out for our apps as well.

Thanks for looking into this!

GrabInbox · 2011-11-28T19:28:18.000Z

The worst thing about this bug is that not many notice it. And unless your users are really enthusiastic about giving feedback, you as the app developer would have a hard time realizing that your application is facing this problem.

IMO, this should be fixed on priority.

justunfollow · 2011-12-07T04:12:07.000Z

@episod anything on this? This is such an important thing as it breaks the oAuth flow. Users are displayed the sign in screen on every login and it’s annoying them

GrabInbox · 2012-01-04T06:55:06.000Z

Anything on this? I’m sorry, but I’ll be pestering you often. This is important as it’s irritating to see the permission screen every time I login to my own app!

GrabInbox · 2012-01-31T09:05:08.000Z

How I wished, someone got this fixed.

creativerelax · 2012-02-12T21:05:04.000Z

Thanks for your help twitter!

CodeInChaos · 2012-03-22T18:21:35.000Z

wow 4 months and this is still not fixed … what’s going on? how hard can this be to fix?

CodeInChaos · 2012-03-22T18:23:28.000Z

out of curiosity, just checking if you guys found any work around for this bug since Twitter is not fixing it yet?

I noticed you’re using /authorize for now on your login, so I’m guessing not?

thanks.

GrabInbox · 2012-03-23T01:53:48.000Z

Nope we haven’t. There’s no work around per se except the /authorize which is annoying for a user. It’s hard to believe something this important hasn’t been fixed.