Wrong Content-Type return parsing for application/pdf on edge function

[PhilippS93]

Bug report

When returning a buffer in an edge function with type application/pdf, the supabase JS client does not parse the result correctly. It is parsed as a string, but not as a blob.

It is stated here, that the return parsing depends on the content-type of the result, so the application/pdf should be parsed as blob. Instead, it is parsed as a string.
When changing the type to e.g. application/octet-stream, it is correctly parsed as a blob.

So, when using the JS supabase library (await this.supabase.functions.invoke()), it parsed the result incorrectly.

Also, when using e.g. Postman and testing the same function with type application/pdf, the correct pdf is shown, so the result is correct.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Create an edge function with return type application/pdf
2. Return a pdf file as Uint8Array
3. Invoke the function using the JS supabase library
4. The result data is a string instead of a blob

Expected behavior

The result should be parsed correctly

System information

• "@supabase/supabase-js": "2.38.1"

[flogy]

Having the same issue with content type application/vnd.openxmlformats-officedocument.wordprocessingml.document (DOCX).