Short answer
Log error.message, not only error.code. If it mentions a Cloud Function, a blocking function such as beforeUserCreated or beforeUserSignedIn threw an error: fix that function. A blocking function that runs past 7 seconds also fails the sign-in, so keep it fast. If nothing points to your code and it keeps happening, report it to Firebase support with the full message.
Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
What hides behind auth/internal-error, and the fix
01
A blocking function threw an error
“Regardless of whether you use a default or custom message, Cloud Functions wraps the error and returns it to the client as an internal error.” Firebase, Extend Firebase Authentication with blocking functions
An HttpsError thrown in a beforeUserCreated or beforeUserSignedIn function stops the sign-up or sign-in. Firebase returns it to the app as an internal error, with the function’s message inside, so show that message to the user.
try { await createUserWithEmailAndPassword(auth, email, password); } catch (error) { console.error(error.code, error.message); // the message holds the reason if (error.message.includes('Cloud Function')) { showError('Sign-up was blocked. Check the details and try again.'); } }02
A blocking function ran past 7 seconds
“Your function must respond within 7 seconds. After 7 seconds, Firebase Authentication returns an error, and the client operation fails.” Firebase, Extend Firebase Authentication with blocking functions
A slow database call or outside API in the function can push it past the limit, and every sign-in or sign-up that runs it then fails with an error. Firebase does not say which code that error carries, so read the message. Move slow work to a normal function that runs after sign-up, and keep the blocking function short.
03
The server hit an unexpected error
“The error message should contain the response from the Authentication server containing additional information.” Firebase, Admin Authentication API errors (auth/internal-error)
With no blocking function involved, read the full message from the server. If the same call keeps failing, send the message and the steps to reproduce it to Firebase support.
04
The app only logs the code
Also check: an error handler that shows “Something went wrong” and drops error.message hides the cause. Log the message to your error tracker before you change anything else.
Checked against the vendor’s docs on : Firebase docs: Admin Authentication API errors; Firebase docs: Extend Firebase Authentication with blocking functions; Firebase JS SDK reference: auth error codes.
Rather hand it over?
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
- from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.See scope and start
“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
Related: Firebase Functions timeout · Firebase auth/operation-not-allowed · Firebase auth/network-request-failed · Firebase auth/billing-not-enabled