Services Plugins FAQs

Bubble Page to PDF Converter – “uploading to AWS is finished” event not firing on desktop (works on mobile)

Plugins
#1

Hi ZeroQode team,

This afternoon (Oct 23, 2025, GMT-3) I started seeing an issue with the Bubble Page to PDF converter plugin: on desktop the element event “ConvertoPDF uploading to AWS is finished” suddenly stopped firing. On mobile, the same event still fires normally and my database is updated as expected.

What my workflow does:

  • I generate a PDF and upload to AWS via the plugin.
  • I listen for the element event “ConvertoPDF uploading to AWS is finished.”
  • In that event’s workflow, I run “Make changes to thing” to write the newly created PDF’s AWS URL into my Proposal record.

What still works

  • The PDF is created and downloaded correctly on desktop.
  • The file is uploaded to AWS (I can see it in my DB / S3).
  • The mobile flow (same page and workflow) works fine and updates the DB with the AWS URL.

What’s broken

  • On desktop, only the element event doesn’t fire anymore, so the “Make changes to thing” step never runs and the Proposal’s URL isn’t updated.
  • This behavior started suddenly today; there were no changes to this part of the workflow on my side right before it stopped working.

Environment

  • Bubble app running in production.
  • Desktop: Windows 10 + Chrome 141.0 (also reproduced in another desktop browser).
  • Mobile: (works) — tested on android and iphone browsers.
  • Timezone: America/São Paulo (GMT-3).

Could you please help me investigate whether there’s a regression or desktop-specific issue with the “uploading to AWS is finished” event in the current plugin version? If there are any recent changes to the event firing logic or recommended workarounds (e.g., listening to a different state/condition), I’d appreciate guidance.

Thanks a lot!

#2

Hi @br.felipesantanna

Thanks for the clear report and the screenshots. We’re sorry you’re seeing the element event fire on mobile but not on desktop - that’s confusing and definitely something we’ll help investigate.

Quick summary of what we checked so far

  • The plugin exposes three element events (Uploading to AWS is finished, Converting is finished, Pre-signed URL ready) - documented in the plugin docs
  • There have been occasional, similar reports in the community (historic threads where the upload/event behavior was intermittently affected). We didn’t find a recent breaking change in the public changelog that would explain a desktop-only regression.
  • We also located your forum thread describing the same desktop-only symptom (today’s post). That’s helpful - thanks for posting it.
    What to try next (ordered - please do them and share results)
  1. Reproduce on a minimal test page
  • Create a new bare page with only: the ConvertToPDF element, a button that triggers the conversion, and a single workflow that logs or writes the workflow step result (so we can see the uploaded file URL immediately). This isolates extensions/workflows. (If this reproduces the issue, share the test page link.)
  1. Browser checks (desktop only)
  • Test in Chrome Incognito with all extensions disabled (to rule out adblocker / privacy extension interference).
  • Try another desktop browser (Firefox/Edge) and capture whether the event fires. You said you tried another browser - please confirm which one and the result.
  1. Check DevTools consoles & network logs during conversion
  • Open DevTools → Console and Network, run the conversion, and copy any console errors or the network request status for the upload to AWS (200 vs 4xx/5xx). A failed JS error or blocked request often prevents the event from firing.
  1. Try the alternate element events / step result as a workaround
  • Listen for the other element events (Converting is finished / Pre-signed URL ready) or use the workflow step result (Result of step X’s file URL) immediately after the conversion action instead of relying only on the element event.

What we need from you to escalate (please attach these)

  • A link to a test editor page (or a read-only editor invite) that reproduces the issue. That’s the fastest way for us to reproduce and escalate.
  • Screenshot(s) of the workflow where you listen for the element event (include the workflow step list, element instance selected, and the plugin element inspector on the page).
  • DevTools console logs and the Network request entry for the S3 upload attempt (copy/paste or a short Loom).

If we can reproduce it on a test page we’ll escalate to devs and ask for a desktop-focused debug pass (we’ll reference the forum threads and changelog while doing so). If you prefer, share the test editor access and we’ll run the minimal reproduction ourselves and report back.

Thanks again - this looks actionable and we’ll move to escalate it as soon as we can reproduce reliably on desktop.
Looking forward to the test page + logs so we can take the next step.

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

#3

Hi @br.felipesantanna,

Just checking in - did you have a chance to try the steps from our last message (minimal test page, browser checks, DevTools/network capture, or the alternate element events)?
We want to reproduce the desktop-only issue and escalate it to devs as soon as we can after confirmation.

To move forward, please share any of the following:

• A link to a test editor page or a read-only editor invite that reproduces the issue.
• Screenshots of the workflow where you listen for the element event (include the workflow step list and the plugin element inspector).
• DevTools console logs and the Network request entry for the S3 upload attempt (copy/paste or a short Loom).

Thanks - once we can reproduce it on a test page, we’ll escalate to devs right away.

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