Skip to main content
k
3mo ago

New user flow is down at Rive main site (rive.app) for Google OAuth

Hi folks,

  1. Excited to try Rive, go to rive.app

  2. Click "Get Started" button to go to login page

  3. Click Google button, go through the Google OAuth flow (select account, authorize, etc)

    Result

    Error message "No user found for account".

    If I had to guess, you have a step that creates a corresponding user record when you see an new oath user, and that step is failing. Or at least, something isn't working in the auth on that rive.app side. (relevant: this google account auths fine to other services)

3 replies
k
m
k
(edited) 3mo ago

Ok I see it isn't actually down, but it definitely looks that way to a new user with the way this page is implemented

A user arriving with the sign up intent needs to click the "Sign Up" tab in order to use the social auth buttons. This is a UX issue, and a bug in your oath implementation.

Here's an opinion from someone who cares about new user flows, which are important to your numbers.

Underlying Bug:

You're treating the oath signup and oath login case separately. Most apps choose to implement this in a way where the button can be clicked in either case and the app figures out whether it is signup or login. (Your page design also suggests this - the oath buttons are outside of the login / signup tabs.

The buttons should just do a call to authenticate with oath and then in your server-side oath callback you would do something like:

on oath success:
   if oauth user id not recognized:
       create new user
       log that user in
       return
   else:
       log that user in
       return

Easy mitigation if you don't want to refactor your oath code:

in the red error message just add a pseudo link "create account?" which just switches the tab over to "sign up". The new user will try again and succeed.

m
3mo ago

somebody knows if this was already fixed?

3mo ago

I'm not sure what it was but yes, it's fixed now.