OAuth not honoring redirect_uri if new account created

[Mike V]

A visitor attempts to authenticate with my application but isn't signed into Meetup. The Meetup signin form is shown with a link to sign up if the visitor doesn't have an account. If this route is taken, after creating an account and verifying their email, the visitor is taken through a series of questions to identify their interests and are then dropped on their Meetup personal page. No longer are they returned to the address specified in redirect_uri during the initial OAuth handshake.

If the visitor has a Meetup account and signs in or is already signed in then the process goes smoothly and the visitor is returned to our application.

The failure to do so after signing up for a new Meetup account is a new problem; new as far as it has worked fine for years until I just ran through some testing and identified it. Not sure exactly how long ago it stopped working however.

Mike

[Jens]

I've noticed this as well but wasn't sure if it had changed or was just some annoyance. 

A similar issue is with the standard /group-url/join or joining from an events page: we basically spend time & money to direct potential members here. Then they sign up, maybe even master the partially broken "complete your account" page... and now we lose them, i.e. they are taken on a detour into the world of meetup, with options to add interests and even other similar/competing groups and are then send back to their personal page instead to the even or group page.

We're not happy about this!

[Mike V]

Thanks for adding Jens. I just tested group-url/join and had a similar experience - I was notified in a small black and white box that I had joined the group at the top of the page after verifying my email, but was then taken through the interest questions and returned to the personal page like you mentioned, not the group. I also tested by "Join and RSVP" on an event page and that went well. I had a shorter and less intrusive interest questionnaire appear, but it didn't go so far as to prompt me to join other Meetup groups and I was returned to the event page when I was done.

Apart from this thread, I've also emailed their support. I did receive a curtesy email but nothing further.

[Doug Tangren]

This sounds like a regression to me. I'll file a developer ticket and follow up here with what we find. If you have the  additional information on hand, did you run into this behavior on mobile or desktop browser.

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to
meetup-api+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Doug Tangren]

On Sun, Dec 20, 2015 at 6:18 PM, Doug Tangren <do...@meetup.com> wrote:

This sounds like a regression to me. I'll file a developer ticket and follow up here with what we find. If you have the  additional information on hand, did you run into this behavior on mobile or desktop browser.

This should now be fixed. Let us know if you continue to experience this problem.

[Mike V]

Hi Doug, this issue has arose again. New users who create meetup accounts are not returned to our application once they confirm the email Meetup sends them and they complete the sign up process.

As an aside, having the users identify interests and join other meetup groups is a very distracting addition to our application sign up process. We would prefer to continue to have the same registration process for OAuth specific sign ups as it were in years past - once the email is verified the user is sent back to the application return_uri variable and not have any further distraction.

Mike