All Errors

Firebase Hosting blocks cross-origin requests to Cloud Functions and APIs unless CORS headers are explicitly configured. Enable CORS by setting headers in firebase.json or adding CORS middleware to your Cloud Functions.

Firebase custom claims cannot use OIDC reserved names like "iss", "sub", "aud", "exp", "iat", or Firebase reserved names. This error occurs when you try to set custom user claims with these reserved keywords.

This MySQL client error occurs when attempting to call mysql_real_connect() on a connection handle that is already connected to a MySQL server. The error indicates that your code is reusing a connection handle without properly closing the previous connection first, or attempting to reconnect on an already-active connection.

This error occurs when a Firebase Callable Function rejects a request due to missing, invalid, or expired authentication credentials. The client must be signed in with Firebase Authentication, and the ID token must be valid and properly included in the request headers.

MySQL Error 2005 occurs when the client cannot resolve or reach the specified MySQL server hostname. This is typically caused by DNS resolution failures, incorrect hostnames, or network connectivity issues.

You exceeded Firebase Cloud Messaging's per-project rate limit by sending too many messages within a short time window. FCM enforces a default quota of 600,000 messages per minute across your entire project.

This MySQL client error occurs when the client process runs out of available memory while fetching or processing query results. The error typically appears when executing queries that return extremely large result sets, processing large BLOB columns, or when the client application has insufficient memory allocation. Breaking queries into smaller chunks, increasing memory limits, or using unbuffered result fetching resolves this issue.

This error occurs when you pass invalid parameters to Firebase Authentication methods. Common causes include empty strings, null values, wrong parameter types, or incorrect method syntax. Most fixes involve validating inputs before passing them to Firebase functions.

This Firebase Storage error occurs when you pass an unsupported data type to the upload function. Firebase Storage upload methods accept only Blob, File, Uint8Array, or ArrayBuffer types. Passing strings, objects, or other data types will trigger this validation error. The fix is to ensure your data is converted to one of the supported formats before uploading.

This error occurs when attempting to upload a file or access an object in Supabase Storage with an invalid file path. Common causes include special characters in the file name, empty path strings, non-ASCII characters that get URL-encoded, or structural issues in the path format.

This error occurs when a scalar subquery in your SQL query returns multiple rows instead of the expected single row. In Supabase, this commonly happens during INSERT/UPDATE operations with triggers, RLS policies, or computed columns.

The Firebase Cloud Messaging "messaging/too-many-topics" error occurs when a single app instance (device) attempts to subscribe to more than 2000 topics. Each device has a hard limit of approximately 2000 topic subscriptions to prevent resource exhaustion.

Users can enroll up to 10 MFA factors in Supabase Auth. When this limit is reached, attempting to enroll another factor fails with the 'too_many_enrolled_mfa_factors' error. This commonly happens when users cancel enrollment flows, leaving unverified factors that count toward the limit.

This error occurs when a Cloud Function takes longer to execute than the maximum allowed timeout duration. By default, Firebase sets a 60-second timeout for HTTP functions and 540 seconds for background functions, with higher limits available for 2nd generation functions.

This PostgreSQL error occurs when the TRIM() function receives invalid arguments or data types. The error happens when TRIM(), LTRIM(), or RTRIM() are called with incompatible parameters, typically when the character argument is invalid or when passing non-string data types that cannot be trimmed.

The "PGRST118: Could not find function" error occurs when you attempt to call a PostgreSQL function via Supabase's PostgREST API, but the function cannot be found in the schema cache. This typically happens after creating a new function, due to schema cache not being refreshed, or when the function lacks proper permissions.

This error indicates that Firebase Cloud Messaging encountered an unexpected condition on the FCM server while processing your request. It's a server-side issue that is typically temporary and should resolve with retries using exponential backoff.

The PostgreSQL "most_specific_type_mismatch" error (2200G) occurs when UNION, CASE, INTERSECT, or EXCEPT queries combine columns or expressions with incompatible data types that cannot be implicitly coerced to a common type. Fixing requires explicitly casting mismatched columns to compatible types.

The "REALTIME_DISCONNECT: Websocket disconnected from Realtime server" error occurs when a WebSocket connection to Supabase Realtime unexpectedly closes. This can happen due to network interruptions, server-side timeouts, authentication token expiration, or quota limits. Implementing proper reconnection logic with exponential backoff is essential for maintaining reliable realtime features.

A foreign key constraint violation (error 23503) occurs when you try to insert or update a record with a reference that doesn't exist in the parent table. In Supabase, this PostgreSQL error prevents orphaned data and maintains database integrity.