Si je comprends bien la doc de lâAPI (et de sa surcouche), le malformed sound file error veut dire que ce quâon essaie de lui envoyer nâest pas perçu comme un fichier son.
Peux tu poster toute ta configuration dans postman? Je crois que tu devrais ĂȘtre en form data et pas en raw. Mais avec la configuration postman, ça aidera
the sample at jsfiddle is intended for developers , using legacy code as an explainer for how to inject clips of legacy code into the esoteric bubble feature that allows for legacy code (js, html ) to be bound to bubble elements in the design dashboard .
There exist aspects of legacy code that in some edge cases may be useful to devs who just need a very specific use case in the genl context of bubble appâŠ
one such case is interacting with legacy apis expecting binarys in the body of a fetch.POST operation.
If you are not comfortable working at the function level with native Javascript in the functional context of a web app, then this solution is not for you.
here is the postman Request, in cURL format (but i saw i can have it in many others, like http)
Please note that it works in Postman using the âBinaryâ option
:
short answer is that if it works in Postman ,it will work using the native html / js implementation in bubble. Assuming a long lease period on value of cookie.AWS⊠you can add to the native html fetch, appropriate headers for content-type, Cookie, Authorization and it will work. Note that the content-type should be a function of the file type and corresponding file extension
from the UI file selector . ie if you choose media type video the content-type in the header sets dynamically . if you only upload wav types then you can hard code it.
find someone to help you who knows a bit more about native development and about the way webapps natively move files around. ie CURL & javascript Fetch
fwiw⊠bubble is ages behind in the general area of nodes streaming io and pipes.
Im not suggesting that bubble is obligated to master features for remoting streams and for remoting any object that can be buffered .
when you have a local binary
when u have a URI to a streamable binary
you should not even have to think about binding the stream readible local object to any service anywhere expecting an input stream in the form of a fetch.Post.body or a piped.readableStream
API Connector - Post Body above was not attempt to hijack this thread or to go off on a teck-tangent. Rather, some more tech toolkits contain powerful tools for remoting any bufferable binary and anyone using Postman/ Curl tools is operating in that more tech sphere.
at min. bubble needs to at least know whats going on out there among users and among people posting faqâs like " if i can do this with a binary using ( curl , wget, fetch, postman ) and its so easy there, then why isnât it easier to do in bubble?"