I am using a third party storage to upload files. Everything works and then I get the error “Response was too large – aborted after 50001144 bytes” I’m confused because I thought Bubble got rid of the 50mb limit. The third party storage I’m using does not have a file limit. Any ideas on how to bypass the limit or maybe I need to go about this a different way.
Thank y’all!
I’m having the same difficulty. I believe that Bubble limits the transfer of data in API requests and unfortunately there is no possibility to change this limit.
running into this as well, does anyone know if there is a way to integrate to API’s without API connector to circumvent this limit?
Good day! did anyone on this thread find a solution to the 50MB API limit?
Reviving this topic:
Has anyone found a workaround to send 50mb+ files from Bubble to an external service through API?
This is essential for the app I’m building, and only found out now after building the largest part of the MVP of my app . This could be a serious threat to continuing here.
What is the service you are trying and what is the process?
For example, I’ve created a fileuploader to upload file from user directly to the third party service. Often, this is the best solution (and cost less WU)
Hi @Jici , I’m using Bubble’s API connector to send a post request to SoundCloud to upload .wav audio files.
And from where the track is coming? Is it an upload from user?
Yea, user uploads
Soyou could create a fileuploader plugin that will directly upload the file to soundcloud instead of using API Connector.
What exactly do you mean by ‘creating a file uploader’ myself? My knowledge is a bit lacking, and setting up API requests is about as far as I’ve gone.
Creating a custom plugin. This plugin will have a fileuploader that will do the request to upload file to soundclound. This is more complex for sure. And if you are using oauth2 authorization code for soundclound… this add a layer of complexity.