Firebase Auth: Exception when signup has been blocked by cloud function is too generic

[janseeger]

[READ] Step 1: Are you in the right place?

I think so.

[REQUIRED] Step 2: Describe your environment

• Firebase Component: Auth
• Component version: 21.3

[REQUIRED] Step 3: Describe the problem

When the signup is blocked by the cloud function it returns a rather generic FirebaseException with the message:

An internal error has occurred. [ BLOCKING_FUNCTION_ERROR_RESPONSE:HTTP Cloud Function returned an error: {"error":{"message":"Signup with provider [google.com](http://google.com/) not allowed","status":"PERMISSION_DENIED"}} ]

This should be either a specific Exception (like FirebaseAuthBlockingFunctionErrorException) or a FirebaseAuthException with a proper code set.

Login logic shouldn't have to parse the returned exception message for magic strings or have to parse JSON to be able to react to errors.

Steps to reproduce:

1. Set up Firebase Auth with a blocking cloud function
2. Sign up with a data that matches the blocking criteria

Relevant Code:

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[argzdev]

Thanks for reaching out, @janseeger. Yeah, that makes sense, we should be able to get the exception message directly. I'll notify our engineers and see what we can do.

Update:
I've marked this as a feature request. While we are unable to promise any timeline for this, for others who find this useful, adding an emoji thumbs up on the original post would definitely help our engineers prioritize adding this to the roadmap.