Based on the screenshot, the response is:

{"error":"Google login is not enabled"}

This message does not appear to be a standard Google authentication error. It looks like an application/backend-generated response indicating that Google Sign-In has not been configured or enabled in the application.

Whether to raise it as a defect depends on the requirement:

Raise it as a Defect if:

• A "Sign in with Google" button is visible and intended to work.
• Google authentication is included in the project's scope/requirements.
• End users are expected to authenticate using Google accounts.

Suggested defect summary:

Google Sign-In option is displayed, but authentication fails with "Google login is not enabled" error.

Do Not Raise it as a Defect (or first seek clarification) if:

• Google Sign-In is still under development.
• The feature is intentionally disabled in the current environment.
• The client/developer has already communicated that Google authentication is not yet configured.

Recommended Action

Before logging a defect, check with the developer or product owner:

"We observed that clicking the 'Sign in with Google' option returns the message Google login is not enabled. Could you please confirm whether Google authentication is expected to be enabled in this environment? If yes, we will log this as a defect."

This helps avoid reporting an issue that may simply be a pending configuration/setup task.