omniauth-google-oauth2 | Oauth2 strategy for Google | OAuth library

This seems to be a bug on part of the omniauth-discord gem. They concatenate the URL without checking whether an avatar is actually set.

But if you look at the Discord documentation, avatar is actually of type ?string so it can be null.

General advice: if something isn't working and it's open source, take a look behind the scenes. Chances are you'll not only quickly find an explanation or solution but you'll also learn something about the things you're working with in the process.

From your ruby -v, I see that you are in an Intel x86 Mac, but the gem that your trying to build (nokogiri-1.11.3-arm64-darwin) is for new Mac ARM M1 chips. If this is the cause, it means your are using precompiled gems.

Try uninstalling the gem, specify that you don't want to use precompiled gems, and reinstall.

This was resolved. the problem was the other user was using a google provided email that was not a gmail i.e. a email@domain.com email address. even though it is controlled by google, it seems like you need a gmail to auth. we switched to a gmail email and it worked fine.

Depending on the OmniAuth version (2.0.0):

OmniAuth now defaults to only POST as the allowed request_phase method

Change Links to POST requests:

This is probably and error with the stylesheet_link_tag and stylesheet_pack_tag, check out your layout files probably you are including sass files and you are using stylesheet_link_tag, this is breaking your code given that as I understand you can just link plane css files. so if you are including sass files use the stylesheet_pack_tag

From what I see your code, you're creating user without email, but you have this validation validates :email, uniqueness: true which won't work if you try to create 2 accounts.

Could you verify this? User.where(email: "").count and let me know. I think if it's more than 0, you can't register.

Either remove email uniqueness validation or try to get email from the auth params.

You can debug with printing the error logs in the callback controller

I figured out what the problem was. On the google developer console for my app, on OAuth 2.0 Client IDs, I had created an ID with type "Other" instead of "Web application".

Creating a new one on https://console.cloud.google.com/apis/credentials?project=myproject with the type "Web application" and adding the callback url (both http and https) to Authorized redirect URIs solved the problem.

First install oauth2

Going by where the links in the repo you linked navigate to (nowhere #), this is a known issue with turbolinks.

You can add data-turbolinks="false" to the link tags to prevent this type of behavior.