Edge Function Deployment Issue - Code Not Updating

[galileoprotocol]

Dear community

I am experiencing a persistent issue deploying an Edge Function named summarize-conversation for my project

Problem Description:

When I deploy the function using the Supabase CLI (v2.20.5, manually installed), the CLI reports a successful deployment (e.g., "Deployed Functions on project uvcpojhvvmtpotzaahli: summarize-conversation").

However, the code running on the Supabase platform does not seem to update. When the function is invoked (even by the preflight OPTIONS request from the browser), the function logs in the Supabase dashboard consistently show logs from an initial template ("Hello from Functions!") and an error: SyntaxError: Unexpected end of JSON input.

This indicates that the deployed code bundle is not being correctly activated or served, and the function remains stuck on a corrupted or initial template version.

Troubleshooting Steps Taken:

I have already tried the following steps without success:

1. Ensured Correct CLI Version: I am using CLI v2.20.5, manually installed from the GitHub release binary, bypassing potential issues with an older Homebrew installation.
2. Tried a Different Function Name: The issue initially occurred with a function named summarize-chat. We created a new function summarize-conversation, but the same deployment problem persists.
3. Deleted and Recreated Function: I deleted the problematic function via the Supabase dashboard and redeployed it using the CLI.
4. Deployed Minimal Code: I replaced the function's code with a very basic version (handling OPTIONS and returning a simple success message for POST) and deployed it. The logs still showed the old "Hello from Functions!" and SyntaxError.

Conclusion:

Based on these tests, the issue does not seem related to my local code, CLI version, or configuration. It strongly points towards a platform-side problem specific to this function or potentially my project, where the deployment process completes according to the CLI but fails to update the running function code on the server.

Could you please investigate the state of the summarize-conversation function for project uvcpojhvvmtpotzaahli and help resolve this deployment issue?

Thank you for your time and assistance.

Sincerely,
Pierre

[BBQMOONRIVER]

I got the same issue!!!
I tried to use "interface" then never update again...

[nyannyacha]

Hello @galileoprotocol

Thank you for the detailed explanation of the issue!

I took a look at the summarize-conversation function, and as you mentioned, it appears to be an initial template. But I also checked the deployment logs for the period between April 7th and 10th, and everything seems to have been processed correctly during that time.

Since the release of v2.20.5, there have been some changes related to function deployments in the CLI. I recommend downloading the latest version of the Supabase CLI and trying the deployment again.

Please let me know if the issue persists, and I'll be happy to assist further.

[pfeddy91]

I have the same problem and I have gone to full length to try and sort it out without any success.

This is insane and incredibly frustrating. Not to mention, it renders my full pipeline unusable as I can't update a key component.

Should I just switch to another provider?

[galileoprotocol]

What I did is to create a new supabase project and everything was working fine Le mer. 14 mai 2025 à 13:24, pfeddy91 ***@***.***> a écrit :

…

I have the same problem and I have gone to full length to try and sort it out without any success. This is insane and incredibly frustrating. Not to mention, it renders my full pipeline unusable as I can't update a key component. Should I just switch to another provider? — Reply to this email directly, view it on GitHub <#34817 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDMTNEXBRKWPW6OLQHYTC7L26MRYPAVCNFSM6AAAAAB2VLH7CWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJUGM3TGOA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[yipcma]

would restarting project clear this? thank you.

[yipcma]

No it did not.

[JetUni]

I'm having the same issue. Different function name. I've tried similar steps to work around the issue, but no luck. In my case, I was adding several lines for logging, but the logging never showed up. Now I know why..the function is not updating like it's supposed to

[white-paper-proj]

I just encountered this same issue. I've tried to even update via the dashboard editor, but the function does not update. Has there been any update to this issue?

[laktek]

@white-paper-proj When you say function is not updating via dashboard editor, does it mean when you make some code changes, deploy the function and reload the dashboard the code changes have not saved?

From the error in original reported issue (SyntaxError: Unexpected end of JSON input), it seems the deployed function was expecting a request body and request was made without a request body or invalid body (eg: GET request was made instead of a POST or POST request didn't have a valid JSON payload).

The easiest way to test your functions is to use the "Test" feature in the dashboard, which should make it easy to compose the right kind of payload.

[scottybo]

I'm having the same issue. When I deploy the new function code (either via the CLI or via the supabase web interface) the code never changes.

Weirdly, if I delete the function and re-deploy the old code still shows.

This is sending me bonkers

[scottybo]

Just to add, this is on the cloud version of Supabase.

I did another test, this is all via the web interface on supabase.com:

• Deleted the edge function completely
• Confirmed the warning that "this action cannot be undone"
• Created a new function (with the same name) and left the code as the boilerplate code that is shown when a new function is created
• The page refreshed, and all the files in the originally deleted edge function appeared again (index.ts and two shared utility functions)

Random findings:

• If you delete the index.ts file, some of the referenced files disappear, but in my case one remained. I then emptied that file and deployed
• I thought it had something to do with the temporary files loading incorrectly, but the integer at the end increments, e.g. /tmp/user_fn_myprojectid_0274ebcf-7c3a-4a60-8cc4-bb14efd09d3c_13 (13 would become 14 on the next deploy)

[scottybo]

Just to add, this is on the cloud version of Supabase.

I did another test, this is all via the web interface on supabase.com:

• Deleted the edge function completely
• Confirmed the warning that "this action cannot be undone"
• Created a new function (with the same name) and left the code as the boilerplate code that is shown when a new function is created
• The page refreshed, and all the files in the originally deleted edge function appeared again (index.ts and two shared utility functions)

Random findings:

• If you delete the index.ts file, some of the referenced files disappear, but in my case one remained. I then emptied that file and deployed
• I thought it had something to do with the temporary files loading incorrectly, but the integer at the end increments, e.g. /tmp/user_fn_myprojectid_0274ebcf-7c3a-4a60-8cc4-bb14efd09d3c_13 (13 would become 14 on the next deploy)

[scottybo]

I found a fix - my supabase edge functions were referencing files in a _shared folder, and this seemed to be causing things to get confused.

I also notice that during build Supabase will modify the code and it was often removing things like comments and so on. This can also confuse things if its stripping out stuff you wanted to be in there.

By inlining these shared functions, deploying seemed to work again at least. Not ideal, but at least I can crack on with getting things done

[rootiac]

This fixed it for me. Crazy you had to do this