All Errors

This warning occurs when rendering an array of elements without assigning a unique "key" prop to each element. Keys help React identify which items have changed, been added, or removed, enabling efficient updates and preventing state mismatches.

React (and bundlers that target it) throws this error when you import a component as a default export but the module only exposes named exports. Align the import/export style or re-export the named symbol as the default so React actually receives the component it expects.

React bundles sometimes leave Node-style `module` references inside browser chunks, so the runtime throws `ReferenceError: module is not defined`. Make sure every file and dependency emits ES module syntax or that your bundler rewrites CommonJS APIs before shipping the code.

This warning occurs when a React component returns an invalid value instead of a valid React element, null, or undefined. React expects components to return JSX elements, but sometimes components accidentally return functions, promises, or forget the return statement entirely.

The Prisma P5011 error occurs when your application exceeds the request rate limits of Prisma Accelerate. This typically happens during traffic spikes, high-concurrency scenarios, or when implementing aggressive retry logic without proper backoff strategies. The fix involves implementing rate limiting, adding exponential backoff, and optimizing your query patterns.

The 'dial tcp: i/o timeout' error occurs when Docker cannot establish a network connection within the expected time. This typically indicates DNS resolution problems, network connectivity issues, firewall restrictions, or proxy misconfiguration.

This error occurs when a SQL/JSON path expression tries to access an array element on non-array data. Resolve it by verifying your JSON structure matches the path expression and using jsonb_typeof() to check data types.

The "sms_send_failed: Sending SMS failed" error occurs when Supabase Auth cannot send SMS messages for phone authentication or OTP verification. This typically happens due to misconfigured SMS provider settings, rate limiting, invalid phone numbers, or insufficient credits with the SMS service provider.

The PostgreSQL error "42P10: invalid_column_reference" occurs when a SQL statement references a column in an invalid context, such as using a column that doesn't exist in the current scope or referencing it incorrectly in subqueries, joins, or window functions. This syntax error prevents query execution and requires correcting the column references.

This error occurs when you attempt to insert or update a row with a primary key value that already exists in the table. SQLite enforces primary key uniqueness strictly, rejecting duplicate key values to maintain data integrity and ensure each row is uniquely identifiable.

The Prisma P5007 error occurs when authentication fails to Prisma Accelerate due to an invalid or missing API key in your connection string. This error prevents your application from connecting to the database through Accelerate's managed proxy service. The fix involves verifying your API key, checking the connection string format, and ensuring your Accelerate project is enabled.

This error occurs when Supabase cannot find a valid refresh token during authentication. Refresh tokens are used to obtain new access tokens without requiring users to re-enter credentials. The fix typically involves checking token storage, session management, and authentication flow configuration.

The "anonymous_provider_disabled: Anonymous sign-ins are disabled" error occurs when Supabase Auth attempts anonymous authentication but anonymous sign-ins are not enabled in the project settings. This prevents users from creating temporary anonymous accounts until anonymous authentication is properly configured and enabled.

The Prisma P3010 error occurs when a migration name exceeds the maximum allowed length (typically 200 characters). This happens during migration creation when using descriptive names or auto-generated names from schema changes. The fix involves shortening migration names or using the --name flag to specify a shorter name.

This error occurs when accessing a non-existent field in JSON data with strict mode enabled. Switch to lax mode or use error handling clauses to suppress or handle missing JSON members gracefully.

The "PGRST117: HTTP verb not allowed" error occurs when you attempt to use an HTTP method (GET, POST, PUT, DELETE, etc.) that is not permitted for a specific Supabase API endpoint or database resource. This typically happens due to Row Level Security (RLS) policies, table permissions, or incorrect API usage.

The "EdgeFunctionError: Function invocation timeout" error occurs when a Supabase Edge Function exceeds its maximum execution time limit. This typically happens with long-running operations, infinite loops, or inefficient code that takes too long to complete within the function's time constraints.

This error occurs when PostgreSQL encounters data that doesn't conform to UTF-8 encoding. Common causes include importing data from non-UTF8 sources, null bytes in text fields, or client/server encoding mismatches. Ensure data is properly encoded or use appropriate binary formats.

This error occurs when Git tries to switch branches or perform a rebase, but detects that untracked files in your working directory would be overwritten by files from the target branch. Git refuses to proceed to prevent accidental data loss.

SQL logic error is SQLite's most generic error code, indicating a problem with your SQL query, virtual table, or internal SQLite issue. This error is difficult to debug because it lacks specificity—the actual cause could be a malformed query, corrupted virtual table, or even memory corruption in your application code.