File Uploader bug (test + live): upload progress oscillates; “value changed” event never fires; autobinding doesn’t save. Also “Report a bug” link on bubble.io/contact is dead

Hi everyone — I’m blocked on a client deliverable and can’t submit via the usual channels.

1) Native File Uploader broken (both version-test and live)

What I see

  • Upload progress keeps progressing and regressing repeatedly (looks like it’s looping).

  • The file does appear in File Manager, so the upload seems to complete server-side.

  • But anything relying on the uploader value updating does not work:

    • Workflow event “When FileUploader’s value is changed” never triggers (no actions run).

    • Autobinding the uploader to a Thing’s file field also does not populate/save.

Repro (minimal)

  1. Add a native File Uploader element to a page (not a plugin uploader).

  2. Create a workflow:

    • Event: When FileUploader’s value is changed

    • Action: show alert / set custom state / make changes to a thing (anything obvious).

  3. (Optional) Bind the uploader value to a Thing’s file field (autobinding) and save.

  4. Run the app in version-test and live.

  5. Upload any file.

Expected

  • Upload completes normally.

  • Uploader’s value changes → workflow triggers.

  • Autobound file field updates/saves.

Actual

  • Progress oscillates.

  • File is visible in File Manager.

  • Workflow never triggers; autobinding doesn’t write.

Scope

  • Happens in both version-test and live.

  • Repro is 100% on my side.

Environment

  • Chrome on macOS

URLs (if you want to test)

  • Version-test: [version-test URL]

  • Live: [live URL]
    (If login is required, I can DM a test account / steps.)

2) “Report a bug” link seems dead

On https://bubble.io/contact, under “Other resources”, clicking Report a bug doesn’t open anything (no form / no navigation).


Questions

  1. Is anyone else seeing this File Uploader behavior recently (value-change not firing even though file appears in File Manager)?

  2. Any known workaround? (e.g., different element, forcing a save action, alternate upload approach)

  3. Is the “Report a bug” link issue known / is there a different official submission path right now?

Thanks in advance — this is blocking production for a client.

This topic was automatically closed after 14 days. New replies are no longer allowed.