All Errors

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.

TypeScript lacks Node types. Fix: run npm i --save-dev @types/node and add "node" to types in tsconfig.json.

Harmless apt warning from a repo (e.g. Google Chrome) lacking i386 packages. Fix: add [arch=amd64] to the repo's sources line.

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.

Postgres rejects an INSERT/UPDATE when a string exceeds a VARCHAR(n) column limit. Fix by widening the column with ALTER TABLE or truncating input.

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.

Exit code 143 means the container was stopped by SIGTERM during shutdown. Fix premature kills by adding a SIGTERM handler and raising terminationGracePeriodSeconds.

GitHub blocks requests past the hourly cap (60 unauthenticated, 5000 authenticated). Fix by sending a token via the Authorization header and honoring Retry-After.

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.

Git needs the Xcode Command Line Tools, which are missing on this Mac. Fix by running xcode-select --install and accepting the install dialog.

Pushing to an archived GitHub repo fails because it is read-only. Fix by asking an owner to unarchive it in Settings, or fork the repo to make changes.

This error occurs when Firebase App Check cannot verify the authenticity of requests to your Firebase services. Token validation failures can stem from misconfigured providers, server time mismatches, expired tokens, or incorrect app registration.

Git stopped a merge because MERGE_HEAD still exists. Finish it with git commit, or discard it with git merge --abort.

PostgreSQL error 2202H occurs when a TABLESAMPLE clause receives an invalid argument. The sampling percentage must be between 0 and 100, and arguments must be numeric constants that can be evaluated at query planning time.

ERROR 1060 occurs when a CREATE TABLE, ALTER TABLE, or SELECT statement tries to define the same column name twice. Resolve this by identifying the duplicate column and either removing, renaming, or qualifying it uniquely.