[{"data":1,"prerenderedAt":1331},["ShallowReactive",2],{"blog-en-supabase-function-not-found":3,"blog-index-en":804},{"id":4,"title":5,"body":6,"category":761,"cover":762,"coverAlt":763,"description":764,"draft":765,"extension":766,"faq":767,"image":783,"keywords":784,"meta":793,"navigation":794,"ogTitle":5,"path":795,"published":796,"seo":797,"stem":798,"tldr":799,"updated":796,"__hash__":803},"blog_en\u002Fblog\u002Fsupabase-function-not-found.md","Supabase PGRST202: \"Could not find the function in the schema cache\"",{"type":7,"value":8,"toc":747},"minimark",[9,13,24,31,47,52,55,62,73,100,103,109,113,116,124,135,144,179,208,211,219,225,253,257,264,279,285,296,299,306,320,325,329,344,347,376,396,422,426,429,465,468,482,486,513,516,522,529,533,540,546,556,559,565,568,573,577,593,599,613,619,627,631,634,643,663,672,690,694,740],[10,11,12],"p",{},"Your builder wrote a database function to load a customer's orders, and the page\nthat calls it stays empty. The browser console shows this:",[14,15,20],"pre",{"className":16,"code":18,"language":19},[17],"language-text","{\n  \"code\": \"PGRST202\",\n  \"details\": \"Searched for the function public.get_orders with parameter userId or with a single unnamed json\u002Fjsonb parameter, but no matches were found in the schema cache.\",\n  \"hint\": \"Perhaps you meant to call the function public.get_orders(user_id)\",\n  \"message\": \"Could not find the function public.get_orders(userId) in the schema cache\"\n}\n","text",[21,22,18],"code",{"__ignoreMap":23},"",[10,25,26,27,30],{},"Supabase \"Could not find the function in the schema cache\" means PostgREST has no\nfunction with that name that accepts exactly the arguments your app sent.\nPostgREST is the part of Supabase that answers your app's ",[21,28,29],{},"supabase.rpc()"," calls,\nand it keeps its own list of every function it can call, called the schema cache.",[10,32,33,34,38,39,42,43,46],{},"Here is the part most answers get wrong: ",[35,36,37],"strong",{},"they tell you to reload the schema\ncache."," On Supabase that list updates itself whenever a function is created or\nchanged. The message has already told you what is wrong. ",[21,40,41],{},"userId",", in the\nbrackets, is what your app sent. ",[21,44,45],{},"user_id",", in the hint, is what the function\nexpects.",[48,49,51],"h2",{"id":50},"what-does-could-not-find-the-function-in-the-schema-cache-mean","What does \"Could not find the function in the schema cache\" mean?",[10,53,54],{},"It means no function in the schema PostgREST searched has that name together with\nexactly those argument names.",[10,56,57,58,61],{},"Think of each database function as a printed form pinned up behind a counter: its\nname across the top, and one labelled box for each argument. When your app calls\n",[21,59,60],{},"supabase.rpc('get_orders', { userId: id })",", it hands over a filled-in copy.\nPostgREST looks for a pinned form with the same name and the same box labels. If\nnone has them, the copy is turned away at the counter, and the message reads back\nthe labels you filled in.",[10,63,64,65,72],{},"Four details are fixed in\n",[66,67,71],"a",{"href":68,"rel":69},"https:\u002F\u002Fgithub.com\u002FPostgREST\u002Fpostgrest\u002Fblob\u002Fmain\u002Fsrc\u002Flibrary\u002FPostgREST\u002FError.hs",[70],"nofollow","PostgREST's own code",":",[74,75,76,84,91,97],"ul",{},[77,78,79,80,83],"li",{},"the code is ",[21,81,82],{},"PGRST202"," and the status is HTTP 404, the status a missing page\ngets",[77,85,86,87,90],{},"the brackets list the argument names your app sent. When it sent none, the\nmessage says ",[21,88,89],{},"without parameters"," in their place",[77,92,93,96],{},[21,94,95],{},"public."," in front of the name is the schema PostgREST searched",[77,98,99],{},"the hint, when there is one, names the closest function PostgREST does know,\nwith that function's own argument names",[10,101,102],{},"Compare the brackets with the hint before anything else.",[104,105],"diagram",{"alt":106,"caption":107,"src":108},"A filled-in copy of the get_orders form beside the pinned get_orders form. The limit box on the copy connects to the limit box on the wall and is ticked. The userId box on the copy runs in amber to a not-equal sign beside user_id, and drops to a plate reading PGRST202 and 404.","PostgREST matches a call by the function's name and every argument name. userId and user_id are two different labels, so no form on the wall matches.","\u002Fblog\u002Fsupabase-function-not-found\u002Fargument-names-must-match-1600x680.png",[48,110,112],{"id":111},"cause-1-the-argument-names-do-not-match","Cause 1: the argument names do not match",[10,114,115],{},"PostgREST picks a function by its name and its argument names together, so a\nfunction called with the wrong names is, as far as PostgREST can tell, a function\nthat does not exist.",[10,117,118,119,72],{},"The rules, from the lookup in\n",[66,120,123],{"href":121,"rel":122},"https:\u002F\u002Fgithub.com\u002FPostgREST\u002Fpostgrest\u002Fblob\u002Fmain\u002Fsrc\u002Flibrary\u002FPostgREST\u002FPlan.hs",[70],"PostgREST's planner",[74,125,126,129,132],{},[77,127,128],{},"every argument that has no default value must be sent, under its exact name",[77,130,131],{},"an argument with a default value may be left out",[77,133,134],{},"a name the function does not declare rules that function out, even when every\nother name matches",[10,136,137,138,140,141,143],{},"A name can be wrong in three ways that are easy to miss. The first is JavaScript\nmeeting SQL: your app writes ",[21,139,41],{}," and the function declares ",[21,142,45],{},".",[10,145,146,147,150,151,153,154,157,158,163,164,167,168,171,172,167,175,178],{},"The second is a prefix. Some functions name their arguments ",[21,148,149],{},"p_user_id",", so that\nthey cannot be mistaken for a column called ",[21,152,45],{},", and then the call has to\ncarry the ",[21,155,156],{},"p_"," as well. In one\n",[66,159,162],{"href":160,"rel":161},"https:\u002F\u002Fgithub.com\u002Forgs\u002Fsupabase\u002Fdiscussions\u002F28379",[70],"Supabase discussion"," the call\nsent ",[21,165,166],{},"id",", ",[21,169,170],{},"nombre"," and three more, the function declared ",[21,173,174],{},"p_id",[21,176,177],{},"p_nombre"," and\nthe rest, and the hint printed every one of the right names.",[10,180,181,182,185,186,189,190,195,196,198,199,202,203,207],{},"The third is the rule that renames columns. A name typed in SQL without double\nquotes is folded to lower case, so ",[21,183,184],{},"create function get_orders(userId uuid)","\nstores the argument as ",[21,187,188],{},"userid",". A\n",[66,191,194],{"href":192,"rel":193},"https:\u002F\u002Fcommunity.flutterflow.io\u002Fask-the-community\u002Fpost\u002Fcustom-action-calling-a-supabase-function---fails-with-a-postgres-IsfG19NQeLRmfRP",[70],"FlutterFlow user","\nmet exactly this: the call sent ",[21,197,41],{},", and the hint answered ",[21,200,201],{},"(userid)",".\n",[66,204,206],{"href":205},"\u002Fblog\u002Fsupabase-schema-cache-column-error","The column version of this error"," has\na table of what each spelling creates.",[10,209,210],{},"To see the names the database stored, run this in the SQL Editor:",[14,212,217],{"className":213,"code":215,"language":216,"meta":23},[214],"language-sql","select p.proname, pg_get_function_arguments(p.oid)\nfrom pg_proc p\njoin pg_namespace n on n.oid = p.pronamespace\nwhere n.nspname = 'public' and p.proname = 'get_orders';\n","sql",[21,218,215],{"__ignoreMap":23},[10,220,221,224],{},[21,222,223],{},"pg_get_function_arguments"," prints the arguments as they were declared, with their\ndefault values, so it also shows which ones you may leave out.",[10,226,227,228,231,232,234,235,238,239,242,243,248,249,252],{},"The safer fix is in the app, because it changes nothing in the database. Ask your\nbuilder to call the function by its stored names: \"",[21,229,230],{},"get_orders"," takes ",[21,233,45],{},";\npass ",[21,236,237],{},"{ user_id: … }"," in every ",[21,240,241],{},".rpc()"," call to it\". Renaming the argument is\nharder than it looks. Postgres's\n",[66,244,247],{"href":245,"rel":246},"https:\u002F\u002Fwww.postgresql.org\u002Fdocs\u002Fcurrent\u002Fsql-createfunction.html",[70],"documentation","\nsays of ",[21,250,251],{},"CREATE OR REPLACE FUNCTION",": \"You cannot change the name already assigned\nto any input parameter\". The function has to be dropped and created again, and\nevery other screen that calls it by the old name then fails the same way.",[48,254,256],{"id":255},"cause-2-the-value-was-undefined-so-the-name-was-never-sent","Cause 2: the value was undefined, so the name was never sent",[10,258,259,260,263],{},"An argument whose value is ",[21,261,262],{},"undefined"," never reaches PostgREST, and the function\nis then looked up without it.",[10,265,266,267,269,270,278],{},"supabase-js sends your arguments as JSON, and JSON has no ",[21,268,262],{},". MDN's\n",[66,271,274,275],{"href":272,"rel":273},"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FJavaScript\u002FReference\u002FGlobal_Objects\u002FJSON\u002Fstringify",[70],"reference for ",[21,276,277],{},"JSON.stringify","\nsays such values \"are either omitted (when found in an object) or changed to null\n(when found in an array)\". So this call, made before the signed-in user has\nloaded:",[14,280,283],{"className":281,"code":282,"language":19},[17],"await supabase.rpc('get_orders', { user_id: user?.id })\n",[21,284,282],{"__ignoreMap":23},[10,286,287,288,291,292,295],{},"sends ",[21,289,290],{},"{}",", and the answer is\n",[21,293,294],{},"Could not find the function public.get_orders without parameters in the schema cache",".\nWith two arguments and one of them undefined, the brackets list only the one that\narrived.",[10,297,298],{},"The name in your code is right, which is why reading the code does not find it.\nThe message does: the brackets are empty, or one name short of what the code\npasses.",[10,300,301,302,305],{},"The fix is to make the call once the value exists. When the function is written to\nhandle a missing value, pass ",[21,303,304],{},"null"," on purpose, which JSON keeps.",[10,307,308,309,312,313,315,316,143],{},"A filter does the opposite with the same value. ",[21,310,311],{},".eq('user_id', user?.id)"," puts it\ninto the request as the word ",[21,314,262],{},", and a uuid column answers\n",[66,317,319],{"href":318},"\u002Fblog\u002Finvalid-input-syntax-for-type-uuid","invalid input syntax for type uuid",[104,321],{"alt":322,"caption":323,"src":324},"A filled-in get_orders copy with user_id holding undefined in amber and limit holding 10. An arrow marked JSON.stringify leads to the copy that is sent, where the user_id box is a dashed empty slot and only limit 10 remains. A second arrow leads to a plate reading PGRST202 and 404.","JSON leaves out a value that is undefined, so the argument disappears on the way and PostgREST looks for a function without it.","\u002Fblog\u002Fsupabase-function-not-found\u002Fundefined-is-never-sent-1600x560.png",[48,326,328],{"id":327},"cause-3-the-function-is-in-another-schema","Cause 3: the function is in another schema",[10,330,331,333,334,337,338,343],{},[21,332,29],{}," looks in the ",[21,335,336],{},"public"," schema, the one the message names, unless\nyou tell it otherwise. A function created anywhere else is not on PostgREST's list\nat all:\n",[66,339,342],{"href":340,"rel":341},"https:\u002F\u002Fgithub.com\u002FPostgREST\u002Fpostgrest\u002Fblob\u002Fmain\u002Fsrc\u002Flibrary\u002FPostgREST\u002FSchemaCache.hs",[70],"it loads functions","\nonly from the schemas your project exposes through its API.",[10,345,346],{},"This shows up in two shapes:",[74,348,349,363],{},[77,350,351,352,355,356,359,360],{},"the function was created in a schema of its own, such as ",[21,353,354],{},"private"," or ",[21,357,358],{},"billing",",\nand is called with a plain ",[21,361,362],{},".rpc('get_orders')",[77,364,365,366,369,370,372,373],{},"the schema is written into the name, as ",[21,367,368],{},".rpc('billing.get_orders')",". PostgREST\nreads the whole string as one name and searches ",[21,371,336],{}," for it, so the message\nsays ",[21,374,375],{},"public.billing.get_orders",[10,377,378,379,382,383,388,389,167,392,395],{},"A function in another schema is called with\n",[21,380,381],{},".schema('billing').rpc('get_orders', …)",", and that schema has to be listed under\nExposed schemas in the project's API settings, as\n",[66,384,387],{"href":385,"rel":386},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fapi\u002Fusing-custom-schemas",[70],"Supabase's guide to custom schemas","\nshows. Until it is, the answer changes to ",[21,390,391],{},"PGRST106",[21,393,394],{},"Invalid schema: billing",",\nwith a hint that lists the schemas that are exposed.",[10,397,398,399,402,403,406,407,411,412,416,417,421],{},"Exposing a schema the way that guide does it opens every table in it. The guide\ngrants ",[21,400,401],{},"anon"," and ",[21,404,405],{},"authenticated"," access to every table in the new schema, and\nfrom then on your\n",[66,408,410],{"href":409},"\u002Fblog\u002Fenable-rls-on-every-supabase-table","Row Level Security"," rules alone decide\nwhat a visitor can read there.\n",[66,413,415],{"href":414},"\u002Fblog\u002Fsupabase-relation-does-not-exist","The table version of this error"," has the\nquery that lists which tables in a schema have those rules switched off, to run\nbefore you expose it. Some functions are kept in a private schema so that\nnobody can call them from outside: our\n",[66,418,420],{"href":419},"\u002Fblog\u002Finfinite-recursion-in-policy-for-relation","guide to infinite recursion in a policy","\nputs one there for that reason. A call to a function like that from the browser\ngets PGRST202 by design, and its schema should stay unexposed.",[48,423,425],{"id":424},"cause-4-the-functions-own-name-or-no-function-at-all","Cause 4: the function's own name, or no function at all",[10,427,428],{},"PostgREST looks up the name exactly, letter for letter and case for case.",[74,430,431,441,451],{},[77,432,433,434,437,438,440],{},"a typo, or ",[21,435,436],{},"getOrders"," in the call against ",[21,439,230],{}," in the database",[77,442,443,444,446,447,450],{},"a function created as ",[21,445,436],{}," without double quotes, which is stored as\n",[21,448,449],{},"getorders"," by the same rule that folds its arguments",[77,452,453,454,457,458,460,461,464],{},"a procedure. PostgREST lists functions only, so ",[21,455,456],{},"create procedure"," makes\nsomething ",[21,459,241],{}," cannot reach, and so does a function that ",[21,462,463],{},"returns trigger",",\nwhich runs from a trigger and never from your app",[10,466,467],{},"The hint helps here too. When no function of that name exists, PostgREST suggests\nthe nearest name it has, if one is close enough.",[10,469,470,471,476,477,481],{},"Or the function was never created in the database your app calls. If you build\nwith Lovable, look back through the chat for SQL you were asked to approve.\nLovable's ",[66,472,475],{"href":473,"rel":474},"https:\u002F\u002Fdocs.lovable.dev\u002Fintegrations\u002Fsupabase",[70],"Supabase documentation","\nsays it \"writes the SQL, shows it to you, and asks for your approval in the project\nchat before running it\". Until you approve it, the function exists only in the\ncode that calls it. If someone created it by hand, check that it went into the\nproject your app talks to:\n",[66,478,480],{"href":479},"\u002Fblog\u002Fsupabase-branching-is-not-a-backup","a branch is a separate project"," with its\nown database.",[48,483,485],{"id":484},"cause-5-the-cache-really-is-out-of-date","Cause 5: the cache really is out of date",[10,487,488,489,492,493,496,497,402,500,503,504,507,508,143],{},"This is the rare one on Supabase. Every Supabase database has an event trigger,\n",[21,490,491],{},"pgrst_ddl_watch",", that sends ",[21,494,495],{},"NOTIFY pgrst, 'reload schema'"," after each\n",[21,498,499],{},"CREATE FUNCTION",[21,501,502],{},"ALTER FUNCTION",", and a second one, ",[21,505,506],{},"pgrst_drop_watch",", sends\nit after a function is dropped. Both are in\n",[66,509,512],{"href":510,"rel":511},"https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fpostgres\u002Fblob\u002Fdevelop\u002Fmigrations\u002Fschema-17.sql",[70],"Supabase's database setup",[10,514,515],{},"When that message does not arrive, reload the list by hand in the SQL Editor:",[14,517,520],{"className":518,"code":519,"language":216,"meta":23},[214],"NOTIFY pgrst, 'reload schema';\n",[21,521,519],{"__ignoreMap":23},[10,523,524,525,528],{},"If nothing changes,\n",[66,526,527],{"href":205},"the column version of this error"," covers\nthe next two steps, the stuck notification queue and the project restart. Both work\nthe same way for functions.",[48,530,532],{"id":531},"when-two-functions-share-one-name","When two functions share one name",[10,534,535,536,539],{},"PostgREST will not guess between them. When two functions have the same name and\nboth accept the arguments your app sent, the call fails with ",[21,537,538],{},"PGRST203"," and HTTP\n300:",[14,541,544],{"className":542,"code":543,"language":19},[17],"Could not choose the best candidate function between: public.get_orders(user_id => uuid), public.get_orders(user_id => text)\n",[21,545,543],{"__ignoreMap":23},[10,547,548,549,551,552,555],{},"A fix for PGRST202 is one way to end up here. Your builder changes an argument's\ntype with ",[21,550,251],{},", and Postgres replaces nothing. Its\n",[66,553,247],{"href":245,"rel":554},[70],"\nsays the argument types cannot be changed that way: \"if you tried, you would\nactually be creating a new, distinct function\". Both versions now exist side by\nside.",[10,557,558],{},"PostgREST's hint for this one reads \"Try renaming the parameters or the function\nitself in the database so function overloading can be resolved\". The plainer fix\nis to drop the version you do not want, naming its argument type so Postgres knows\nwhich one you mean:",[14,560,563],{"className":561,"code":562,"language":216,"meta":23},[214],"drop function public.get_orders(text);\n",[21,564,562],{"__ignoreMap":23},[10,566,567],{},"Check which version your app calls before you drop either of them.",[104,569],{"alt":570,"caption":571,"src":572},"One filled-in get_orders copy carrying user_id, and two pinned get_orders forms on the wall, one whose user_id box takes uuid and one whose box takes text. Dashed amber lines run from the copy to both forms, and the copy drops to a plate reading PGRST203 and 300.","Changing an argument's type with CREATE OR REPLACE adds a second function with the same name. A call that fits both is refused.","\u002Fblog\u002Fsupabase-function-not-found\u002Ftwo-functions-one-name-1600x700.png",[48,574,576],{"id":575},"calling-a-supabase-function-the-right-way","Calling a Supabase function the right way",[10,578,579,580,585,586,589,590,143],{},"Pass one object whose keys are the function's argument names, spelled the way the\ndatabase stored them. In\n",[66,581,584],{"href":582,"rel":583},"https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Ffunctions",[70],"Supabase's guide to database functions",",\na function declared as ",[21,587,588],{},"add_planet(name text)"," is called with\n",[21,591,592],{},"supabase.rpc('add_planet', { name: 'Jakku' })",[10,594,595,596,598],{},"Once your app can call the function, so can anyone else. The same guide says it\nplainly: \"By default, any role can run a database function.\" That includes\n",[21,597,401],{},", the role behind every request from a visitor who is not signed in. A\nfunction your app calls from the browser can be called by anybody who has your\npublic key, with whatever arguments they choose.",[10,600,601,602,605,606,402,608,610,611,143],{},"For a function only signed-in users should run, follow the guide: take ",[21,603,604],{},"execute","\naway from ",[21,607,336],{},[21,609,401],{},", and give it back to ",[21,612,405],{},[14,614,617],{"className":615,"code":616,"language":216,"meta":23},[214],"revoke execute on function public.get_orders from public, anon;\ngrant execute on function public.get_orders to authenticated;\n",[21,618,616],{"__ignoreMap":23},[10,620,621,622,626],{},"Your tables are the other half of what that public key reaches. Our\n",[66,623,625],{"href":624},"\u002Fsecurity-scanner","free scan"," checks from outside whether they hand rows to\nanyone who holds it, and it needs no account.",[48,628,630],{"id":629},"changing-a-function-your-app-depends-on","Changing a function your app depends on",[10,632,633],{},"Keep a copy of the database from before the change, and hear about it when\nsomething your app exposes changes.",[10,635,636],{},[35,637,638,642],{},[66,639,641],{"href":640},"\u002Fsupabase-backups","Reeve Care"," keeps a copy of your Supabase database:",[74,644,645,648,651,654,657,660],{},[77,646,647],{},"an encrypted copy on a schedule, on Reeve's own storage in the EU, outside your Supabase account",[77,649,650],{},"the copy from before your change holds your functions as they were defined then, beside your tables and rows",[77,652,653],{},"each copy verified before it counts, by counting the rows in every table",[77,655,656],{},"your uploaded files as well, once you connect a Storage credential",[77,658,659],{},"a one-click restore, with a safety copy of the current state taken first",[77,661,662],{},"everything Monitor does",[10,664,665],{},[35,666,667,671],{},[66,668,670],{"href":669},"\u002Fwebsite-monitoring","Reeve Monitor"," keeps checking from outside:",[74,673,674,677,680,687],{},[77,675,676],{},"whether your app is up, checked every minute",[77,678,679],{},"the full security check every hour, on up to three apps",[77,681,682,683,686],{},"a message when a result ",[35,684,685],{},"changes",", so a deploy that changes what your app exposes reaches you without you going to look",[77,688,689],{},"a monthly report, in plain language, of what it saw",[48,691,693],{"id":692},"what-to-do-now","What to do now",[695,696,697],"key-takeaways",{},[74,698,699,702,708,714,721,724,731],{},[77,700,701],{},"Read the message: the names in brackets are what your app sent, and the hint names what the database has.",[77,703,704,705,707],{},"Compare the argument names letter for letter, including any ",[21,706,156],{}," prefix. A name typed in SQL without quotes is stored in lower case.",[77,709,710,711,713],{},"If the brackets are empty or one name short, look for a value that was ",[21,712,262],{}," when the call was made.",[77,715,716,717,720],{},"Check the schema in the message. A function in another schema needs ",[21,718,719],{},".schema('name').rpc(…)"," and an exposed schema, and exposing one makes its tables reachable too.",[77,722,723],{},"If two functions share the name, drop the version your app does not call.",[77,725,726,727,730],{},"Run ",[21,728,729],{},"NOTIFY pgrst, 'reload schema';"," only once the names match.",[77,732,733,734,736,737,739],{},"Take ",[21,735,604],{}," away from ",[21,738,401],{}," on any function a visitor who is not signed in should never run.",[10,741,742,743,746],{},"Start with the brackets, because they hold exactly what your app sent. Before you\ndrop or replace a function your app depends on,\n",[66,744,745],{"href":640},"keep a copy of the database"," from before the change.",{"title":23,"searchDepth":748,"depth":748,"links":749},3,[750,752,753,754,755,756,757,758,759,760],{"id":50,"depth":751,"text":51},2,{"id":111,"depth":751,"text":112},{"id":255,"depth":751,"text":256},{"id":327,"depth":751,"text":328},{"id":424,"depth":751,"text":425},{"id":484,"depth":751,"text":485},{"id":531,"depth":751,"text":532},{"id":575,"depth":751,"text":576},{"id":629,"depth":751,"text":630},{"id":692,"depth":751,"text":693},"Security basics","\u002Fblog\u002Fsupabase-function-not-found\u002Fcover-1200x630.png","A printed form pinned to a wall with a row of labelled boxes, and a filled-in copy held in front of it with one box lit in amber.","Supabase \"Could not find the function in the schema cache\" lists the argument names your app sent. Compare them with the function first.",false,"md",[768,771,774,777,780],{"q":769,"a":770},"What does PGRST202 mean?","PGRST202 is the code PostgREST, the part of Supabase that answers supabase.rpc() calls, gives when no function matches a call. It comes back with HTTP 404 and the message \"Could not find the function public.name(arguments) in the schema cache\". The names in brackets are the arguments your app sent, and public is the schema it searched.",{"q":772,"a":773},"The function exists. Why does my RPC call say it is missing?","PostgREST matches a function by its name and its argument names together. Send every argument that has no default value, under exactly the name the database stored, and nothing the function does not declare. A name written in SQL without double quotes is stored in lower case, so userId in a create function statement becomes userid.",{"q":775,"a":776},"Why does the error say \"without parameters\"?","Your app sent no arguments at all. With supabase-js the usual reason is a value that was undefined when the call was made: the arguments travel as JSON, which leaves undefined values out, so { user_id: undefined } arrives as {}. Make the call once the value exists, or pass null if the function is written to handle a missing value.",{"q":778,"a":779},"Does the function have to be in the public schema?","supabase.rpc() looks in public unless you pick another schema with .schema('name'), and that schema must be listed under Exposed schemas in the project's API settings. Exposing a schema makes what is in it reachable through the API, so it is worth deciding on purpose.",{"q":781,"a":782},"How do I reload the Supabase schema cache?","Run NOTIFY pgrst, 'reload schema'; in the SQL Editor. Supabase already sends that message by itself whenever a function is created, changed or dropped, so a reload helps only when the message did not arrive. Check the names first.","\u002Fblog\u002Fsupabase-function-not-found\u002Fcard-800x500.png",[785,786,787,788,789,790,791,792],"could not find the function in the schema cache","pgrst202","supabase rpc function not found","supabase rpc 404","supabase function parameter mismatch","could not find the function without parameters in the schema cache","pgrst203","could not choose the best candidate function",{},true,"\u002Fblog\u002Fsupabase-function-not-found","2026-10-22",{"title":5,"description":764},"blog\u002Fsupabase-function-not-found",[800,801,802],"Supabase \"Could not find the function in the schema cache\" (PGRST202) means no function has that name and accepts exactly the argument names your app sent. The names in brackets in the message are the ones your app sent.","Check the argument names first: userId sent to a function that declares user_id, a missing p_ prefix, or a value that was undefined and so was never sent.","Supabase updates its list of functions by itself whenever one is created, changed or dropped, so check the names and the schema before you reload anything.","L50WQxnk4eLPlvmr_8O3LQ3gFU89hXlnv0msJ1pvrRQ",[805,811,817,823,829,835,841,847,853,859,865,872,878,884,890,896,901,907,912,913,918,924,930,936,942,948,954,960,966,972,978,984,990,995,1001,1007,1013,1019,1025,1031,1037,1043,1049,1055,1061,1067,1072,1078,1084,1090,1096,1102,1108,1114,1120,1126,1132,1138,1144,1150,1156,1162,1167,1173,1179,1185,1191,1197,1203,1209,1215,1221,1227,1233,1239,1245,1251,1257,1262,1268,1274,1280,1286,1292,1297,1303,1309,1315,1320,1326],{"path":806,"title":807,"description":808,"published":809,"category":761,"image":810,"draft":765},"\u002Fblog\u002Fmax-client-connections-reached","Supabase \"max client connections reached\", explained","Supabase \"max client connections reached\" means the pooler has no room for one more client. The port in your connection string decides the limit.","2026-11-09","\u002Fblog\u002Fmax-client-connections-reached\u002Fcard-800x500.png",{"path":812,"title":813,"description":814,"published":815,"category":761,"image":816,"draft":765},"\u002Fblog\u002Funsupported-provider-provider-is-not-enabled","\"Unsupported provider: provider is not enabled\" in Supabase","\"Unsupported provider: provider is not enabled\" means Google sign-in is off in your Supabase project. How to turn it on, and fix redirect_uri_mismatch.","2026-11-08","\u002Fblog\u002Funsupported-provider-provider-is-not-enabled\u002Fcard-800x500.png",{"path":818,"title":819,"description":820,"published":821,"category":761,"image":822,"draft":765},"\u002Fblog\u002Fviolates-foreign-key-constraint","\"violates foreign key constraint\" on insert in Supabase","Supabase \"insert or update on table violates foreign key constraint\": your row points at a row that is not there. Which one, why, and the fix.","2026-11-07","\u002Fblog\u002Fviolates-foreign-key-constraint\u002Fcard-800x500.png",{"path":824,"title":825,"description":826,"published":827,"category":761,"image":828,"draft":765},"\u002Fblog\u002Fnull-value-violates-not-null-constraint","\"null value in column violates not-null constraint\" in Supabase","Supabase \"null value in column violates not-null constraint\": a required column arrived empty. Where the null came from, and the fix.","2026-11-06","\u002Fblog\u002Fnull-value-violates-not-null-constraint\u002Fcard-800x500.png",{"path":830,"title":831,"description":832,"published":833,"category":761,"image":834,"draft":765},"\u002Fblog\u002Fauth-session-missing","Supabase \"Auth session missing!\": where the session went","\"Auth session missing!\" is supabase-js finding no signed-in session and stopping before it asks Supabase. Where the session went, and the fix for each.","2026-11-05","\u002Fblog\u002Fauth-session-missing\u002Fcard-800x500.png",{"path":836,"title":837,"description":838,"published":839,"category":761,"image":840,"draft":765},"\u002Fblog\u002Finvalid-claim-missing-sub-claim","Supabase \"invalid claim: missing sub claim\": nobody is signed in","\"invalid claim: missing sub claim\" means Supabase Auth got a genuine token that names no user: your project key, sent where a session belongs.","2026-11-04","\u002Fblog\u002Finvalid-claim-missing-sub-claim\u002Fcard-800x500.png",{"path":842,"title":843,"description":844,"published":845,"category":761,"image":846,"draft":765},"\u002Fblog\u002Ffailed-to-send-a-request-to-the-edge-function","\"Failed to send a request to the Edge Function\" in Supabase","\"Failed to send a request to the Edge Function\" means the browser got no reply it could read. Its console says why, and whether your function ran.","2026-11-03","\u002Fblog\u002Ffailed-to-send-a-request-to-the-edge-function\u002Fcard-800x500.png",{"path":848,"title":849,"description":850,"published":851,"category":761,"image":852,"draft":765},"\u002Fblog\u002Fsupabase-auth-redirects-to-localhost","Why Supabase email links redirect to localhost:3000","A Supabase redirect to localhost:3000 means the Site URL was never changed, or your address is missing from Redirect URLs. The fix, and the wildcard to avoid.","2026-11-02","\u002Fblog\u002Fsupabase-auth-redirects-to-localhost\u002Fcard-800x500.png",{"path":854,"title":855,"description":856,"published":857,"category":761,"image":858,"draft":765},"\u002Fblog\u002Femail-link-is-invalid-or-has-expired","Supabase \"Email link is invalid or has expired\" on a fresh link","On a link sent a minute ago, Supabase's \"Email link is invalid or has expired\" usually means a mail filter used it first. How to check and fix it.","2026-11-01","\u002Fblog\u002Femail-link-is-invalid-or-has-expired\u002Fcard-800x500.png",{"path":860,"title":861,"description":862,"published":863,"category":761,"image":864,"draft":765},"\u002Fblog\u002Fcanceling-statement-due-to-statement-timeout","Supabase \"canceling statement due to statement timeout\", explained","Supabase \"canceling statement due to statement timeout\" means a query outran its role's limit, 3 seconds for a visitor. Check the RLS policy first.","2026-10-31","\u002Fblog\u002Fcanceling-statement-due-to-statement-timeout\u002Fcard-800x500.png",{"path":866,"title":867,"description":868,"published":869,"category":870,"image":871,"draft":765},"\u002Fblog\u002Fdatabase-error-deleting-user","\"Database error deleting user\" in Supabase, and what goes with it","\"Database error deleting user\" in Supabase means your database refused the delete. The reason is in your logs, and the fix decides what else is deleted.","2026-10-30","Backups","\u002Fblog\u002Fdatabase-error-deleting-user\u002Fcard-800x500.png",{"path":873,"title":874,"description":875,"published":876,"category":761,"image":877,"draft":765},"\u002Fblog\u002Fstripe-webhook-no-signatures-found","\"No signatures found matching the expected signature\" in Supabase","A Stripe webhook in a Supabase Edge Function that says \"No signatures found matching the expected signature\" has one of two causes. Never stop checking.","2026-10-29","\u002Fblog\u002Fstripe-webhook-no-signatures-found\u002Fcard-800x500.png",{"path":879,"title":880,"description":881,"published":882,"category":761,"image":883,"draft":765},"\u002Fblog\u002Fsupabase-invalid-login","\"Invalid login credentials\" in Supabase: the three causes","Supabase says \"Invalid login credentials\" for a wrong password, an unknown email and a Google account. How to tell which, and why it is vague.","2026-10-28","\u002Fblog\u002Fsupabase-invalid-login\u002Fcard-800x500.png",{"path":885,"title":886,"description":887,"published":888,"category":761,"image":889,"draft":765},"\u002Fblog\u002Fedge-function-returned-a-non-2xx-status-code","\"Edge Function returned a non-2xx status code\" in Supabase","\"Edge Function returned a non-2xx status code\" means your Supabase function answered with an error. Here is where to read the real one.","2026-10-27","\u002Fblog\u002Fedge-function-returned-a-non-2xx-status-code\u002Fcard-800x500.png",{"path":891,"title":892,"description":893,"published":894,"category":761,"image":895,"draft":765},"\u002Fblog\u002Fcertificate-not-trusted","Certificate not trusted: the three causes besides expiry","Certificate not trusted, and the date is fine? It names another address, it signed itself, or its chain is missing a link. How to tell which.","2026-10-26","\u002Fblog\u002Fcertificate-not-trusted\u002Fcard-800x500.png",{"path":318,"title":897,"description":898,"published":899,"category":761,"image":900,"draft":765},"Supabase \"invalid input syntax for type uuid\": read the quotes","Supabase \"invalid input syntax for type uuid\" means your app sent something that is not an id. Read the quotes, hold the query, keep the column.","2026-10-25","\u002Fblog\u002Finvalid-input-syntax-for-type-uuid\u002Fcard-800x500.png",{"path":902,"title":903,"description":904,"published":905,"category":761,"image":906,"draft":765},"\u002Fblog\u002Fduplicate-key-value-violates-unique-constraint","Supabase \"duplicate key value violates unique constraint\", explained","Supabase \"duplicate key value violates unique constraint\" means the value is already taken. Find the column, pick a fix, and keep the value off screen.","2026-10-24","\u002Fblog\u002Fduplicate-key-value-violates-unique-constraint\u002Fcard-800x500.png",{"path":414,"title":908,"description":909,"published":910,"category":761,"image":911,"draft":765},"Supabase \"relation does not exist\" when the table is right there","Supabase \"relation does not exist\" or PGRST205 means no table matches the name and schema your query used. Four checks, and what exposing a schema opens.","2026-10-23","\u002Fblog\u002Fsupabase-relation-does-not-exist\u002Fcard-800x500.png",{"path":795,"title":5,"description":764,"published":796,"category":761,"image":783,"draft":765},{"path":205,"title":914,"description":915,"published":916,"category":761,"image":917,"draft":765},"Supabase PGRST204: \"Could not find the column in the schema cache\"","Supabase \"Could not find the column in the schema cache\" usually means a name mismatch. Four checks in order, and the one-line reload.","2026-10-21","\u002Fblog\u002Fsupabase-schema-cache-column-error\u002Fcard-800x500.png",{"path":919,"title":920,"description":921,"published":922,"category":761,"image":923,"draft":765},"\u002Fblog\u002Fsupabase-email-rate-limit-exceeded","Supabase \"Email Rate Limit Exceeded\": two limits, one error code","Supabase \"Email Rate Limit Exceeded\" caps every email your project sends: 2 an hour on the built-in sender. What it counts and how to lift it.","2026-10-20","\u002Fblog\u002Fsupabase-email-rate-limit-exceeded\u002Fcard-800x500.png",{"path":925,"title":926,"description":927,"published":928,"category":761,"image":929,"draft":765},"\u002Fblog\u002Fsupabase-users-logged-out","Supabase \"Invalid Refresh Token: Refresh Token Not Found\": 3 causes","Supabase \"Invalid Refresh Token: Refresh Token Not Found\" logs your users out. Three causes, and how the auth log tells them apart.","2026-10-19","\u002Fblog\u002Fsupabase-users-logged-out\u002Fcard-800x500.png",{"path":931,"title":932,"description":933,"published":934,"category":761,"image":935,"draft":765},"\u002Fblog\u002Fpermission-denied-for-schema-public","Supabase \"permission denied for schema public\": three causes","Supabase \"permission denied for schema public\" means a missing schema grant. What removed it, and the line that puts it back.","2026-10-18","\u002Fblog\u002Fpermission-denied-for-schema-public\u002Fcard-800x500.png",{"path":937,"title":938,"description":939,"published":940,"category":761,"image":941,"draft":765},"\u002Fblog\u002Fsupabase-bucket-not-found","Supabase \"Bucket not found\": the three things it means","Supabase \"Bucket not found\" is one of three things: a public link to a private bucket, a name that is not an exact match, or the wrong project.","2026-10-17","\u002Fblog\u002Fsupabase-bucket-not-found\u002Fcard-800x500.png",{"path":943,"title":944,"description":945,"published":946,"category":761,"image":947,"draft":765},"\u002Fblog\u002Fsupabase-invalid-jwt","Supabase invalid JWT: which key stopped working?","A Supabase invalid JWT error is PGRST301, and it means a signed token failed verification. On a newer project that token is your user, not your API key.","2026-10-16","\u002Fblog\u002Fsupabase-invalid-jwt\u002Fcard-800x500.png",{"path":949,"title":950,"description":951,"published":952,"category":761,"image":953,"draft":765},"\u002Fblog\u002Fsupabase-single-row-error","Supabase \"multiple (or no) rows returned\" usually means no rows","Supabase returns PGRST116, \"JSON object requested, multiple (or no) rows returned\", when your query found none. A row your rules hide looks missing.","2026-10-15","\u002Fblog\u002Fsupabase-single-row-error\u002Fcard-800x500.png",{"path":955,"title":956,"description":957,"published":958,"category":761,"image":959,"draft":765},"\u002Fblog\u002Fdatabase-error-saving-new-user","\"Database error saving new user\" in Supabase, and where to look","\"Database error saving new user\" means something attached to your Supabase signup failed and it was all rolled back. The real error is in your logs.","2026-10-14","\u002Fblog\u002Fdatabase-error-saving-new-user\u002Fcard-800x500.png",{"path":961,"title":962,"description":963,"published":964,"category":761,"image":965,"draft":765},"\u002Fblog\u002Fwhat-is-supabase","What is Supabase? The database your builder picked for you","What is Supabase: the database, login and file storage behind your app. Supabase runs the servers; the rules about who reads your rows are yours.","2026-10-13","\u002Fblog\u002Fwhat-is-supabase\u002Fcard-800x500.png",{"path":967,"title":968,"description":969,"published":970,"category":761,"image":971,"draft":765},"\u002Fblog\u002Faws-access-key-exposed-in-frontend","An AWS access key exposed in your frontend is not like an OpenAI key","An AWS access key exposed in your frontend reads and writes your storage. The fix is usually a presigned URL rather than a new key.","2026-10-12","\u002Fblog\u002Faws-access-key-exposed-in-frontend\u002Fcard-800x500.png",{"path":973,"title":974,"description":975,"published":976,"category":761,"image":977,"draft":765},"\u002Fblog\u002Fstorage-upload-violates-row-level-security","\"Row-level security policy for table objects\" on upload","\"New row violates row-level security policy for table objects\" means your upload has no insert rule. Making the bucket public does not add one.","2026-10-11","\u002Fblog\u002Fstorage-upload-violates-row-level-security\u002Fcard-800x500.png",{"path":979,"title":980,"description":981,"published":982,"category":761,"image":983,"draft":765},"\u002Fblog\u002Fbase44-security-scan","Base44 security scan: the one thing only it can see","The Base44 security scan checks seven kinds of problem from inside your app. Here is the half it reads that nothing outside can, and the half it never looks at.","2026-10-10","\u002Fblog\u002Fbase44-security-scan\u002Fcard-800x500.png",{"path":985,"title":986,"description":987,"published":988,"category":761,"image":989,"draft":765},"\u002Fblog\u002Fapi-key-leaked-what-to-do","Your API key leaked. Here is the order to do things in","An API key leaked and you want to know what to do first. Not every key in your frontend is one, and the order matters more than the speed.","2026-10-09","\u002Fblog\u002Fapi-key-leaked-what-to-do\u002Fcard-800x500.png",{"path":419,"title":991,"description":992,"published":993,"category":761,"image":994,"draft":765},"\"Infinite recursion detected in policy\" without disabling RLS","\"Infinite recursion detected in policy for relation\" means your Supabase policy asked the table it protects. Here is how to break the circle.","2026-10-08","\u002Fblog\u002Finfinite-recursion-in-policy-for-relation\u002Fcard-800x500.png",{"path":996,"title":997,"description":998,"published":999,"category":761,"image":1000,"draft":765},"\u002Fblog\u002Fno-api-key-found-in-request","\"No API key found in request\" in Supabase, and the wrong fix","\"No API key found in request\" means your Supabase request arrived without a key. Most answers you find point at your database rules instead.","2026-10-07","\u002Fblog\u002Fno-api-key-found-in-request\u002Fcard-800x500.png",{"path":1002,"title":1003,"description":1004,"published":1005,"category":761,"image":1006,"draft":765},"\u002Fblog\u002Fis-base44-safe","Is Base44 safe? What 5,442 live Base44 apps showed","Is Base44 safe? We ran nine checks on 5,442 live Base44 apps. Almost all scored B for reasons the owner never chose, and one question nobody can answer.","2026-10-06","\u002Fblog\u002Fis-base44-safe\u002Fcard-800x500.png",{"path":1008,"title":1009,"description":1010,"published":1011,"category":761,"image":1012,"draft":765},"\u002Fblog\u002Fmove-a-secret-to-an-edge-function","Hide an API key: move it to a Supabase Edge Function","Hiding an API key means moving it off the browser, and a Supabase Edge Function is the smallest place to put it. Two steps around the move matter more.","2026-10-05","\u002Fblog\u002Fmove-a-secret-to-an-edge-function\u002Fcard-800x500.png",{"path":1014,"title":1015,"description":1016,"published":1017,"category":761,"image":1018,"draft":765},"\u002Fblog\u002Fenv-file-exposed-on-your-server","Is your .env file exposed? The twelve paths to check","Is your .env file exposed on your own web server? Twelve addresses tell you in a minute, and a hit means everything in the file is already public.","2026-10-04","\u002Fblog\u002Fenv-file-exposed-on-your-server\u002Fcard-800x500.png",{"path":1020,"title":1021,"description":1022,"published":1023,"category":761,"image":1024,"draft":765},"\u002Fblog\u002Fis-v0-safe","v0 security: all 1,790 v0 apps we scanned got an A","v0 security, measured on 1,790 live v0 apps: every one graded A. Only 17 named a database, and that is most of what the A is measuring.","2026-10-03","\u002Fblog\u002Fis-v0-safe\u002Fcard-800x500.png",{"path":1026,"title":1027,"description":1028,"published":1029,"category":761,"image":1030,"draft":765},"\u002Fblog\u002Fis-bolt-safe","Is Bolt safe? What 1,123 live Bolt apps showed","Is Bolt safe? We ran nine checks on 1,123 live Bolt apps. The hosting came back clean. The findings were API keys and open tables inside the apps.","2026-10-02","\u002Fblog\u002Fis-bolt-safe\u002Fcard-800x500.png",{"path":1032,"title":1033,"description":1034,"published":1035,"category":761,"image":1036,"draft":765},"\u002Fblog\u002Fis-supabase-down-or-your-app","Is Supabase down, or is it your app? How to tell","Is Supabase down, or is it your app? A paused project, a full database and a bug of your own all look like an outage. Four checks tell them apart.","2026-10-01","\u002Fblog\u002Fis-supabase-down-or-your-app\u002Fcard-800x500.png",{"path":1038,"title":1039,"description":1040,"published":1041,"category":761,"image":1042,"draft":765},"\u002Fblog\u002Fdoes-supabase-encrypt-my-data","Does Supabase encrypt my data? Yes. Here is what it stops","Does Supabase encrypt data? Yes: AES-256 at rest, TLS in transit, SOC 2 and ISO 27001 audited. What each one covers, and the leak none of them stops.","2026-09-30","\u002Fblog\u002Fdoes-supabase-encrypt-my-data\u002Fcard-800x500.png",{"path":1044,"title":1045,"description":1046,"published":1047,"category":761,"image":1048,"draft":765},"\u002Fblog\u002Fsupabase-free-plan-limits","Supabase free plan limits, and what happens at each one","The Supabase free plan limits you to 500 MB of database and 5 GB of egress, with no backups. What happens as you cross each line, and what $25 changes.","2026-09-29","\u002Fblog\u002Fsupabase-free-plan-limits\u002Fcard-800x500.png",{"path":1050,"title":1051,"description":1052,"published":1053,"category":870,"image":1054,"draft":765},"\u002Fblog\u002Ftest-your-supabase-backup","Test your Supabase backup before the day you need it","How to test your Supabase backup: restore it into a spare project, compare the row counts, sign in, and check for the line a cut-off file is missing.","2026-09-28","\u002Fblog\u002Ftest-your-supabase-backup\u002Fcard-800x500.png",{"path":1056,"title":1057,"description":1058,"published":1059,"category":870,"image":1060,"draft":765},"\u002Fblog\u002Fsupabase-backup-github-action","Free Supabase backup with a GitHub Action, and the catch","A Supabase backup GitHub Action costs nothing and suits a lot of apps. The workflow, the connection string that works on GitHub, and the egress each run uses.","2026-09-27","\u002Fblog\u002Fsupabase-backup-github-action\u002Fcard-800x500.png",{"path":1062,"title":1063,"description":1064,"published":1065,"category":870,"image":1066,"draft":765},"\u002Fblog\u002Fdownload-your-supabase-backup","Why you can't download your Supabase backup","You can't download your Supabase backup on a current project, because the daily copy is a physical snapshot. How to tell, and how to hold a copy of your own.","2026-09-26","\u002Fblog\u002Fdownload-your-supabase-backup\u002Fcard-800x500.png",{"path":1068,"title":1069,"description":1070,"published":1065,"category":761,"image":1071,"draft":765},"\u002Fblog\u002Fsupabase-permission-denied-for-table","Supabase \"permission denied for table\": the missing grant","From October 30, a new Supabase table answers \"permission denied for table\" until you grant access. The grant the email shows is half the fix.","\u002Fblog\u002Fsupabase-permission-denied-for-table\u002Fcard-800x500.png",{"path":1073,"title":1074,"description":1075,"published":1076,"category":761,"image":1077,"draft":765},"\u002Fblog\u002Fopen-api-endpoint-exposed","Is an open API endpoint a security problem? Look at the JSON","Your scan flagged an open API endpoint. Whether it matters depends on what came back, and most of the ones we found were the platform's own.","2026-09-25","\u002Fblog\u002Fopen-api-endpoint-exposed\u002Fcard-800x500.png",{"path":1079,"title":1080,"description":1081,"published":1082,"category":761,"image":1083,"draft":765},"\u002Fblog\u002Flovable-security-scan","Lovable security scan: the one thing it cannot prove","Lovable security scan: what the Quick and Deep scans check, when each one runs, and the one thing no scan from inside your project can prove.","2026-09-24","\u002Fblog\u002Flovable-security-scan\u002Fcard-800x500.png",{"path":1085,"title":1086,"description":1087,"published":1088,"category":870,"image":1089,"draft":765},"\u002Fblog\u002Fsupabase-backup-auth-users","Why your Supabase dump has no users in it","Run supabase db dump on its own and you get the shape of your database and none of its rows, with the auth schema your users live in left out entirely.","2026-09-23","\u002Fblog\u002Fsupabase-backup-auth-users\u002Fcard-800x500.png",{"path":1091,"title":1092,"description":1093,"published":1094,"category":761,"image":1095,"draft":765},"\u002Fblog\u002Fdomain-and-certificate-expiry","Domain expired, website down: what actually happens next","Your domain expired and your website is down. Here is the clock you are on, why a lapsed certificate is the easier of the two, and how to check both.","2026-09-22","\u002Fblog\u002Fdomain-and-certificate-expiry\u002Fcard-800x500.png",{"path":1097,"title":1098,"description":1099,"published":1100,"category":761,"image":1101,"draft":765},"\u002Fblog\u002Fis-lovable-safe","Is Lovable safe? What 18,554 live Lovable apps showed","Is Lovable safe? We ran nine checks on 18,554 live Lovable apps. The platform was the cleanest of five builders. Every finding was inside the app itself.","2026-09-21","\u002Fblog\u002Fis-lovable-safe\u002Fcard-800x500.png",{"path":1103,"title":1104,"description":1105,"published":1106,"category":761,"image":1107,"draft":765},"\u002Fblog\u002Fvibe-coded-app-security-checklist","The vibe coding security checklist, in nine checks","A vibe coding security checklist with nine items, each one something anyone can verify about your live app from outside, and each with a one-line test.","2026-09-20","\u002Fblog\u002Fvibe-coded-app-security-checklist\u002Fcard-800x500.png",{"path":1109,"title":1110,"description":1111,"published":1112,"category":761,"image":1113,"draft":765},"\u002Fblog\u002Fstripe-secret-key-in-frontend","A Stripe secret key exposed in your frontend can move money","A Stripe secret key exposed in your frontend can refund, charge and read every customer record you hold. Your pk_live_ key is meant to be there.","2026-09-19","\u002Fblog\u002Fstripe-secret-key-in-frontend\u002Fcard-800x500.png",{"path":1115,"title":1116,"description":1117,"published":1118,"category":761,"image":1119,"draft":765},"\u002Fblog\u002Fvite-and-next-public-env-vars","Vite env variables exposed: VITE_ and NEXT_PUBLIC_ mean publish this","Vite env variables exposed in your app did what the prefix asked. VITE_ and NEXT_PUBLIC_ mean publish this, and the AI that added one never knew the cost.","2026-09-18","\u002Fblog\u002Fvite-and-next-public-env-vars\u002Fcard-800x500.png",{"path":1121,"title":1122,"description":1123,"published":1124,"category":761,"image":1125,"draft":765},"\u002Fblog\u002Fbase44-source-maps","Base44 security: what a scan flags, and what is yours to fix","Base44 security on 5,438 scanned apps: three findings on nearly every one are the platform's, the source map is Base44's badge, and what is yours is short.","2026-09-17","\u002Fblog\u002Fbase44-source-maps\u002Fcard-800x500.png",{"path":1127,"title":1128,"description":1129,"published":1130,"category":761,"image":1131,"draft":765},"\u002Fblog\u002Fis-cursor-ai-safe","Is Cursor AI safe? The editor, the code, and the app you shipped","Is Cursor AI safe? Three questions in one search: what Cursor keeps, what the code it writes gets wrong, and whether the app you shipped is open.","2026-09-16","\u002Fblog\u002Fis-cursor-ai-safe\u002Fcard-800x500.png",{"path":1133,"title":1134,"description":1135,"published":1136,"category":761,"image":1137,"draft":765},"\u002Fblog\u002Fis-replit-safe","Is Replit safe? What we found in 3,042 live Replit apps","Is Replit safe? We ran nine external checks on 3,042 live Replit apps. The host was not where the findings were. The app each owner published was.","2026-09-15","\u002Fblog\u002Fis-replit-safe\u002Fcard-800x500.png",{"path":1139,"title":1140,"description":1141,"published":1142,"category":870,"image":1143,"draft":765},"\u002Fblog\u002Fsupabase-storage-backup","Supabase storage backup: why your database copy has no files","A Supabase storage backup is a separate job. Database backups keep the list of your files and none of the files, so a restore leaves every upload broken.","2026-09-14","\u002Fblog\u002Fsupabase-storage-backup\u002Fcard-800x500.png",{"path":1145,"title":1146,"description":1147,"published":1148,"category":870,"image":1149,"draft":765},"\u002Fblog\u002Fsupabase-point-in-time-recovery","Supabase point-in-time recovery: what it costs, what it misses","Supabase point-in-time recovery rewinds your database to any second in the last week. It costs $100 a month on top of Pro, and it covers your database only.","2026-09-13","\u002Fblog\u002Fsupabase-point-in-time-recovery\u002Fcard-800x500.png",{"path":1151,"title":1152,"description":1153,"published":1154,"category":870,"image":1155,"draft":765},"\u002Fblog\u002Fsupabase-project-paused-recover","Supabase project paused? Your data is still there","Supabase paused your project after a week of inactivity. Nothing is deleted, Restore sits beside the project name, and you have a year before that changes.","2026-09-12","\u002Fblog\u002Fsupabase-project-paused-recover\u002Fcard-800x500.png",{"path":1157,"title":1158,"description":1159,"published":1160,"category":761,"image":1161,"draft":765},"\u002Fblog\u002Fsafest-ai-app-builder","Which AI app builder is safest? We scanned 30,998 apps","Which AI app builder is safest? We scanned 30,998 live apps from Lovable, Base44, Replit, v0 and Bolt. The builder is not what decides your grade.","2026-09-11","\u002Fblog\u002Fsafest-ai-app-builder\u002Fcard-800x500.png",{"path":409,"title":1163,"description":1164,"published":1165,"category":761,"image":1166,"draft":765},"Enable Row Level Security on every Supabase table, then prove it","Enabling Row Level Security in Supabase with no policy locks a table completely. A policy without the setting does nothing. Here is the SQL, and the test.","2026-09-10","\u002Fblog\u002Fenable-rls-on-every-supabase-table\u002Fcard-800x500.png",{"path":1168,"title":1169,"description":1170,"published":1171,"category":761,"image":1172,"draft":765},"\u002Fblog\u002Fsupabase-rls-disabled-in-public","Supabase \"RLS disabled in public\": what the warning misses","Supabase reports \"RLS disabled in public\" as an error. It says nothing about the read policy that leaves your table just as open to strangers.","2026-09-09","\u002Fblog\u002Fsupabase-rls-disabled-in-public\u002Fcard-800x500.png",{"path":1174,"title":1175,"description":1176,"published":1177,"category":761,"image":1178,"draft":765},"\u002Fblog\u002Frotate-supabase-service-role-key","How to rotate a leaked Supabase service_role key","Supabase says fix the leak first. Other guides say rotate now. Which is right depends on where your service_role key leaked.","2026-09-08","\u002Fblog\u002Frotate-supabase-service-role-key\u002Fcard-800x500.png",{"path":1180,"title":1181,"description":1182,"published":1183,"category":761,"image":1184,"draft":765},"\u002Fblog\u002Fvibe-coding-security-scanners-compared","Vibe coding security scanners compared, including ours","The best vibe coding security scanner comes down to three questions no feature list answers. Eight tools compared, with prices, and the jobs Reeve does not do.","2026-09-07","\u002Fblog\u002Fvibe-coding-security-scanners-compared\u002Fcard-800x500.png",{"path":1186,"title":1187,"description":1188,"published":1189,"category":761,"image":1190,"draft":765},"\u002Fblog\u002Fsupabase-security-checker","Supabase security checker: run the five checks yourself","A Supabase security checker reads your published app instead of your project settings. Here are the five checks it runs, and how to run each one yourself.","2026-09-06","\u002Fblog\u002Fsupabase-security-checker\u002Fcard-800x500.png",{"path":1192,"title":1193,"description":1194,"published":1195,"category":761,"image":1196,"draft":765},"\u002Fblog\u002Fvibe-coding-security-scanner","Vibe coding security scanner: what a URL scan misses","A vibe coding security scanner reads your live app from outside. Here is what that covers, the four things it cannot see, and how to read the result.","2026-09-05","\u002Fblog\u002Fvibe-coding-security-scanner\u002Fcard-800x500.png",{"path":1198,"title":1199,"description":1200,"published":1201,"category":761,"image":1202,"draft":765},"\u002Fblog\u002Fmissing-security-headers","Missing security headers: when it actually matters","Missing security headers is the finding our scanner prints most. Here is what it protects against, and when it is the least urgent line on your report.","2026-09-04","\u002Fblog\u002Fmissing-security-headers\u002Fcard-800x500.png",{"path":1204,"title":1205,"description":1206,"published":1207,"category":761,"image":1208,"draft":765},"\u002Fblog\u002Fopenai-api-key-exposed-in-frontend","Your OpenAI API key is exposed in your frontend. Rotate it.","An OpenAI API key exposed in your frontend cannot be locked to a domain. Rotate it today, move the call behind your own endpoint, and cap the spend.","2026-09-03","\u002Fblog\u002Fopenai-api-key-exposed-in-frontend\u002Fcard-800x500.png",{"path":1210,"title":1211,"description":1212,"published":1213,"category":761,"image":1214,"draft":765},"\u002Fblog\u002Fwhat-secrets-leak-from-vibe-coded-apps","An API key exposed in your frontend: what 30,998 apps shipped","An API key exposed in your frontend is usually a Google Maps key. We scanned 30,998 live vibe-coded apps and counted which secrets actually leak.","2026-09-02","\u002Fblog\u002Fwhat-secrets-leak-from-vibe-coded-apps\u002Fcard-800x500.png",{"path":1216,"title":1217,"description":1218,"published":1219,"category":870,"image":1220,"draft":765},"\u002Fblog\u002Fsupabase-backup-tools-compared","Supabase backup tools compared, including ours","Four kinds of Supabase backup tool, what each one actually copies, and the case where a free GitHub Action beats paying anyone, us included.","2026-09-01","\u002Fblog\u002Fsupabase-backup-tools-compared\u002Fcard-800x500.png",{"path":1222,"title":1223,"description":1224,"published":1225,"category":761,"image":1226,"draft":765},"\u002Fblog\u002Freplit-secrets-explained","How to use secrets in Replit, and what still gets published","How to use secrets in Replit: add one, read it back, and fix the two reasons it comes back undefined. Plus the keys the Secrets tool cannot keep private.","2026-08-31","\u002Fblog\u002Freplit-secrets-explained\u002Fcard-800x500.png",{"path":1228,"title":1229,"description":1230,"published":1231,"category":870,"image":1232,"draft":765},"\u002Fblog\u002Fback-up-supabase-free-tier","Supabase free tier backups: how to make one without a terminal","There are no Supabase free tier backups, so the copy has to come from you. How to make one from the dashboard, and what CSV leaves out.","2026-08-30","\u002Fblog\u002Fback-up-supabase-free-tier\u002Fcard-800x500.png",{"path":1234,"title":1235,"description":1236,"published":1237,"category":761,"image":1238,"draft":765},"\u002Fblog\u002Fis-supabase-secure","Is Supabase secure? Yes. Your project is a separate question","Is Supabase secure? The platform is audited, encrypted and pen-tested. Their own compliance documents say where that stops and your settings begin.","2026-08-29","\u002Fblog\u002Fis-supabase-secure\u002Fcard-800x500.png",{"path":1240,"title":1241,"description":1242,"published":1243,"category":761,"image":1244,"draft":765},"\u002Fblog\u002Fwhere-to-find-supabase-api-keys","Where to find your Supabase API keys: anon, service_role and the URL","Your Supabase project URL, anon key and service_role key are on one dashboard page. Here is where that page is, and which of the four belongs in your app.","2026-08-28","\u002Fblog\u002Fwhere-to-find-supabase-api-keys\u002Fcard-800x500.png",{"path":1246,"title":1247,"description":1248,"published":1249,"category":761,"image":1250,"draft":765},"\u002Fblog\u002Fnew-row-violates-row-level-security-policy","New row violates row-level security policy in Supabase. Now what?","\"New row violates row-level security policy\" means Supabase refused a write. The fix that clears it in ten seconds also reopens the table to everyone.","2026-08-27","\u002Fblog\u002Fnew-row-violates-row-level-security-policy\u002Fcard-800x500.png",{"path":1252,"title":1253,"description":1254,"published":1255,"category":761,"image":1256,"draft":765},"\u002Fblog\u002Fcors-wildcard-security-risk","Is a CORS wildcard a security risk? Usually not.","Is a CORS wildcard a security risk? Usually it is your builder default, and it gives away nothing your server was not already handing to anyone who asked.","2026-08-26","\u002Fblog\u002Fcors-wildcard-security-risk\u002Fcard-800x500.png",{"path":479,"title":1258,"description":1259,"published":1260,"category":870,"image":1261,"draft":765},"Supabase branching is not a backup. It only goes forwards.","Supabase branching is not a backup: a branch starts with none of your data, and merging only moves schema. What it is for, and what to use instead.","2026-08-25","\u002Fblog\u002Fsupabase-branching-is-not-a-backup\u002Fcard-800x500.png",{"path":1263,"title":1264,"description":1265,"published":1266,"category":870,"image":1267,"draft":765},"\u002Fblog\u002Fhow-to-restore-a-supabase-backup","How to restore a Supabase backup, and what breaks after","How to restore a Supabase backup from the dashboard or from a dump file, what the restore replaces, and why your app can still be broken when it finishes.","2026-08-24","\u002Fblog\u002Fhow-to-restore-a-supabase-backup\u002Fcard-800x500.png",{"path":1269,"title":1270,"description":1271,"published":1272,"category":761,"image":1273,"draft":765},"\u002Fblog\u002Fsupabase-storage-bucket-public","Your Supabase storage bucket is public. Is that a problem?","A public Supabase storage bucket means anyone with a file URL can open it. It does not mean anyone can list what is in there. Two different settings.","2026-08-23","\u002Fblog\u002Fsupabase-storage-bucket-public\u002Fcard-800x500.png",{"path":1275,"title":1276,"description":1277,"published":1278,"category":761,"image":1279,"draft":765},"\u002Fblog\u002Fgoogle-api-key-exposed-in-frontend","Is a Google API key exposed in your frontend a problem?","A Google API key exposed in your frontend is the key our scanner finds most often, and usually it is fine. One free setting decides which it is.","2026-08-22","\u002Fblog\u002Fgoogle-api-key-exposed-in-frontend\u002Fcard-800x500.png",{"path":1281,"title":1282,"description":1283,"published":1284,"category":870,"image":1285,"draft":765},"\u002Fblog\u002Fai-agent-deleted-my-database","An AI agent deleted my Supabase data. What can I recover?","An AI agent deleted your database data. What you can recover was decided before it ran, and the next few minutes decide how much of it survives.","2026-08-21","\u002Fblog\u002Fai-agent-deleted-my-database\u002Fcard-800x500.png",{"path":1287,"title":1288,"description":1289,"published":1290,"category":761,"image":1291,"draft":765},"\u002Fblog\u002Fcan-anyone-read-your-supabase-database","Can anyone read your Supabase database? We checked 3,680 apps","Can anyone read your Supabase database without logging in? We scanned 30,998 live apps built with AI builders and measured how often the answer is yes.","2026-08-18","\u002Fblog\u002Fcan-anyone-read-your-supabase-database\u002Fcard-800x500.png",{"path":1293,"title":1294,"description":1295,"published":1290,"category":761,"image":1296,"draft":765},"\u002Fblog\u002Fsource-maps-exposed-in-production","Source maps exposed: your app is publishing its original code","An exposed source map lets anyone read your app's original code, comments included. The 30-second check, and what actually matters if yours are public.","\u002Fblog\u002Fsource-maps-exposed-in-production\u002Fcard-800x500.png",{"path":1298,"title":1299,"description":1300,"published":1301,"category":761,"image":1302,"draft":765},"\u002Fblog\u002Fsupabase-new-api-keys","Supabase publishable key: is it the same as the anon key?","Supabase replaced anon and service_role with publishable and secret keys. Which one belongs in your app, and which never does?","2026-08-12","\u002Fblog\u002Fsupabase-new-api-keys\u002Fcard-800x500.png",{"path":1304,"title":1305,"description":1306,"published":1307,"category":870,"image":1308,"draft":765},"\u002Fblog\u002Fdoes-supabase-back-up-my-database","Does Supabase back up my database? It depends on your plan.","Does Supabase back up your database? Daily on paid plans, and not at all on the free one. How to check which you have, and what that copy cannot survive.","2026-08-11","\u002Fblog\u002Fdoes-supabase-back-up-my-database\u002Fcard-800x500.png",{"path":1310,"title":1311,"description":1312,"published":1313,"category":761,"image":1314,"draft":765},"\u002Fblog\u002Fsupabase-rls-on-but-table-still-public","Supabase Row Level Security is on. Your table is still public.","Turning on Supabase Row Level Security does not protect a table. Your policies do, and the policy that fixed your broken app may let everyone in.","2026-08-10","\u002Fblog\u002Fsupabase-rls-on-but-table-still-public\u002Fcard-800x500.png",{"path":1316,"title":1317,"description":1318,"published":1313,"category":870,"image":1319,"draft":765},"\u002Fblog\u002Fversion-history-is-not-a-backup","Version history is not a backup. It cannot undo a deleted table.","Lovable and Bolt keep version history for your code. Your database is a separate service, so rolling back to this morning does not bring your data back.","\u002Fblog\u002Fversion-history-is-not-a-backup\u002Fcard-800x500.png",{"path":1321,"title":1322,"description":1323,"published":1324,"category":870,"image":1325,"draft":765},"\u002Fblog\u002Fthree-ways-to-back-up-a-supabase-database","Three ways to back up a Supabase database, and what each misses","The dashboard, pg_dump, and a managed service. What each one actually saves, what it quietly leaves out, and which one survives losing the account.","2026-08-09","\u002Fblog\u002Fthree-ways-to-back-up-a-supabase-database\u002Fcard-800x500.png",{"path":1327,"title":1328,"description":1329,"published":1324,"category":761,"image":1330,"draft":765},"\u002Fblog\u002Fwhich-api-keys-are-safe-in-your-frontend","Which API keys are safe in your frontend, and which aren't","Your Supabase anon key is supposed to be public. Your service_role key is not, and it ignores every rule you set. Here is how to tell them apart.","\u002Fblog\u002Fwhich-api-keys-are-safe-in-your-frontend\u002Fcard-800x500.png",1794213635058]