☁️Wasabi Cloud Storage Plugin

Showcase Plugins
875

Hey @Tyler1

Thanks for reaching out! :folded_hands:

We’ve checked the older versions of the plugin, and it looks like the “Download File Name” field has always been static. That said, we totally get how dynamic text would be super useful, especially on mobile where finding downloaded files can be tricky.

I’ve passed this idea to the dev team – it’s a great suggestion, and we’ll definitely consider it for future updates!

Let us know if you need any further help or if you have any other suggestions. :blush:

Cheers,
Support Team
Browse all Zeroqode Plugins for bubble
Banner_Last3

876

Hi @Tyler1,

Thanks again for your patience! :folded_hands:

We are happy to let you know that we’ve successfully deployed a new version with the dynamic field functionality in our test environment. :tada: The live version, including this feature, is scheduled to be pushed on Monday.

We’ll keep you updated once it’s live, and feel free to reach out if you have any other questions or need further assistance.

Cheers,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

1 Like
877

Hey :wave: ,

I am building a companion mobile application for my web application , i couldn’t find Wasabi file download option for the mobile plugin. There are only two options for the mobile development.

Do you work on an update ? Do you have any time plan for mobile development ?

Thank you.

878

Hey @kuntaykunt ,

At the moment, the Wasabi plugin does not yet support a direct file download option specifically tailored for mobile applications. We’re aware that this is a valuable feature for mobile development, and we truly appreciate your feedback.

Currently, our development efforts are somewhat limited, and we don’t have a specific timeline for when mobile-focused updates—like Wasabi file download support—will be available. However, we are keeping this in mind for future improvements.

Thank you for understanding!

Best Regards,
Zeroqode Support Team

Browse all Zeroqode Plugins for Bubble
Banner_Last3

879

Is anyone else having an issue where “_1” gets added to the end of every file when downloading from wasabi?

Example: file1.wav turns into file1.wav_1

This breaks all of my downloads.

These screenshots show that this happens even when I hardcode “file.wav”

image

image
image336×364 9.7 KB

880

Hi @tkgibbs310 ,

Thanks for reaching out!

The _1 suffix is something that Bubble automatically appends when the browser detects a duplicate filename during download, or when the response headers don’t include a proper content-disposition filename.
With the Wasabi Cloud Storage plugin, this usually happens when:

  • The Pre-Signed URL being generated doesn’t include a filename in the header, so the browser “guesses” one and adds _1.
  • The file name on Wasabi and the “Download File Name” field mismatch.
  • Some browsers (especially Chrome/Edge) add _1 when the MIME type or disposition header is incomplete.

To help us pinpoint the root cause, could you please share:

  1. The exact Pre-Signed URL before download (feel free to DM if private)
  2. Your workflow screenshot where the file is uploaded and where the Pre-Signed URL is generated
  3. A test link so we can try downloading it on our side and reproduce the _1 behavior

Once we can reproduce it, we’ll check whether it’s a Wasabi API header issue or something coming from Bubble’s download handling.

Looking forward to your details. We’ll be happy to help you sort this out

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

881

Hi @tkgibbs310,

Just checking in to see if you had a chance to review my previous message.

Were you able to grab the Pre-Signed URL and the workflow screenshots?
These details will help us reproduce the _1 filename issue and investigate it properly.

If everything is clear now or the problem resolved on your side, feel free to let us know as well.

Thanks, and looking forward to your update!

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

882

Thank you for the response. Honestly, I was on a time crunch and switched to building my own method for managing the downloads. This also allowed me to expose the download progress more cleanly in the UI.

I’d be happy to contribute more information if other’s report the experience - for now, my needs are taken care of.

Thank you!

1 Like
883

Hi @tkgibbs310,

Thanks for the update - totally understand the time crunch, and we’re glad you found a solution that works well for your workflow.

If this behavior comes up again or others report the same issue, we may reach out to gather a bit more info from you.
In any case, you’re always welcome to drop by with details whenever it’s convenient.

Appreciate you letting us know, and thanks again for your time!

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

884

This plugin was working just fine for me, then suddenly stopped functioning. I haven’t changed anything. My Wasabi account and settings are the same. The element settings have not been touched, but users reported issues uploading and progress bars no longer worked.

Here’s what I’ve found…
NOTE: at the time of all of these screenshots, I had uploaded a file that did appear in the Wasabi bucket and was accessible from the Wasabi UI.

  1. Wasabi element reports an error when trying to upload. However, the error appears empty: “Failed to upload file:”

image
image540×153 2.58 KB

  1. While uploading, the element’s progress does not progress.

image
image446×226 6.49 KB

  1. The element remains in an error state, however I see the file in Wasabi and I’m able to access it successfully.

image

image
image586×187 4.49 KB

  1. The “File Upload Successful” event is never triggered, and therefore my subsequent actions never run. The UI relies on this event triggering to tell the user their upload is complete and perform several other actions.

image
image412×189 4.62 KB

  1. Due to the fact that the file is appearing in Wasabi, it seems that the “File added”, “Create Pre-signed URL”, and “Upload WasabiS3” action all work - at least semi-correctly.

image
image392×402 8.72 KB

In summary:

  1. Uploads are successful and files are stored in Wasabi
  2. However, I am unable to achieve a sensible user experience as the element’s “upload progress” field does not progress beyond 0 and the “Upload Successful” event never fires.
  3. My current work around is to schedule a workflow for several minutes out after I arbitrarily assume the user’s upload is finished to perform the actions necessary after an upload has finished. This is horrible UX and causes my users to have to wait several minutes for to access their files.

What I’ve tried:

  1. Moving back through previous versions (I tried the previous 10 versions - however I know that it at least worked on 1.131.0 when I launched the app)
  2. Uninstalled the plugin
  3. Removed all Wasabi elements and workflows
  4. Rebuilt all Wasabi related elements and workflows
  5. Tried actions in Edge and Chrome, each with incognito.

Please help! I shipped this app to a client last week and this is looking really bad.

885

Hi @tkgibbs310,

Thanks again for the detailed report and for your patience while we looked into this.

We’ve done thorough testing on our side (including uploads with and without Auto-submit) and, so far, we haven’t been able to reproduce the behavior you’re seeing. The upload flow, progress updates, and the “File Upload Successful” event all trigger as expected in our tests.

To be able to investigate this further and see what might be specific to your setup, we’ll need a bit more visibility.

Could you please share:

  • Collaborator access to your app (support@zeroqode.com),
  • A dedicated test page where we can freely inspect and adjust the Wasabi element, workflows, and states without risking your production logic

In the meantime, we’d also recommend re-checking our demo editor workflows here:

And the plugin documentation for reference:

If there’s any subtle difference between your setup and the demo (event usage, states, multiple uploads, scheduling, etc.), it may help narrow things down quickly.

Once we have access to a test setup, we’ll be happy to dig deeper and see what’s causing this on your side.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

886

I’ve added the support email as a collaborator.

Here’s the test page supplied: https://salisbury.aprative.com/version-test/wasabi-test2

I’ve replicated the elements exactly as they are in production on my app and still experience the same issue on the test page.

I’ve also made sure that the settings and workflow work exactly as shown in your demo editor.

There are no other plugins on the test page.

Thank you for the support.

1 Like
887

Hi @tkgibbs310,

Thank you for sharing the access and the test page — much appreciated.

We’ll now review the setup directly in the editor and test the upload flow there to see if we can reproduce the same behavior in that environment. If we spot anything unusual or need additional clarification, we’ll get back to you with specific questions.

Thanks again for setting this up so clearly — it really helps speed things up.
We’ll keep you posted as soon as we have updates.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

888

Hi @tkgibbs310,

Thanks for your patience while we dug deeper into this and for giving us access to the editor — that really helped.

We’ve reviewed your test page and logs together with our dev team. While we still can’t reproduce the issue on our demo or internal setups, we did notice a clear CORS-related error in the browser console on your app side. This would explain all the symptoms you’re seeing: upload reaches Wasabi, but progress stays at 0, the element goes into an error state, and the “File Upload Successful” event never fires.

Specifically, the browser is blocking the request due to a missing or restrictive CORS configuration on the Wasabi bucket.

What we recommend checking on your Wasabi side

  1. Bucket CORS configuration
    Please make sure your bucket has CORS enabled. For testing purposes, you can try a permissive setup like this:
[
  {
    "AllowedOrigins": ["*"],
    "AllowedMethods": ["GET", "PUT", "POST", "DELETE", "HEAD"],
    "AllowedHeaders": ["*"],
    "ExposeHeaders": [
      "ETag",
      "x-amz-server-side-encryption",
      "x-amz-request-id"
    ],
    "MaxAgeSeconds": 3000
  }
]

image
image2521×837 144 KB

After saving, give it a few minutes and then retry the upload.
2. Wasabi account type
Please confirm that the bucket is not on a Trial account. Public access and some request types are restricted on trial plans and can cause uploads to partially succeed but fail client-side callbacks.
3. Bucket Policy
Double-check the bucket policy to ensure there’s nothing blocking PUT or HEAD requests from the browser. Even if the file uploads, blocked response headers can break progress tracking and success events.

Why this matches what you’re seeing

  • The file does upload → PUT request succeeds
  • Browser blocks the response due to CORS → plugin never receives completion signal
  • Progress stays at 0 and the success event never fires → broken UX despite successful upload

Once CORS and bucket policies are aligned, the progress indicator and File Upload Successful event should start behaving normally again.

Please let us know once you’ve had a chance to review these settings, or feel free to share screenshots of your CORS + bucket policy if you’d like us to double-check them with you.

Regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

889

Hi @tkgibbs310,

Just checking in to see if you had a chance to review the CORS and bucket settings on your Wasabi side. Were you able to test the upload again after applying the suggested configuration?

If you’ve already made changes or are seeing different behavior now, feel free to share an update or screenshots — we’re happy to take another look.

Thanks, and looking forward to hearing from you.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

890

Thank you for following up. Yes, adjusting the CORS settings in Wasabi was the issue. I very much appreciate your support, I would not have found that otherwise.

Thank you!

1 Like
891

Hi @tkgibbs310,

That’s great to hear - thanks for the confirmation!
We’re really glad the CORS adjustment resolved the issue and that we could help point you in the right direction.

If you run into anything else or have questions down the road, feel free to reach out anytime. Thanks again, and happy building! :raising_hands:

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3

892

Hey Guys, please, could you make it available to mobile native? I am a paying user of WebVersion, but it doesn’t work on native mobile and I really need to use it on my app (native mobile).

1 Like
893

Hi Sergio,

Thank you for your message and for being a paying user of the Web version — we truly appreciate your support :raising_hands:

We’ve created a suggestion ticket for our dev and management team, and the idea of a native mobile version of this plugin is currently being explored. At the moment, I can’t provide an exact timeline for when (or if) it will be released, but if there are any updates, I’ll make sure to circle back to you right away and keep you informed.

We completely understand your frustration, especially if you’re building a native mobile app and need this functionality there as well.

If possible, we’d really appreciate it if you could reconsider and update your review for the Web version of the Wasabi Cloud Storage plugin. It helps us a lot, especially when the feedback reflects the current functionality of the product itself, since the current limitation isn’t related to an issue with the Web version itself, but rather a request for a new native product.

Thank you again for your understanding and for taking the time to share your thoughts.

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Banner_Last3