Files Pro - Multi File Uploader 2.122.0 Bug

[obtrectation]

I am running version 2.122.0. Rolling back to 2.119.0 fixes this issue.

I trigger a workflow based on the “Uploader uploaded” event. I am using the plugin to accept only single file uploads. When I upload a single file, the workflow fails because the Base64 property is empty. When I upload another file, the workflow moves forward but the Base64 data is from the first upload attempt.

Please look at the below and let me know what you think. My understanding is that the “uploaded” event should already have the Base64 data when triggered. In my case it does not.

Here is my plugin object configuration:

[Stephan]

Hello @obtrectation,

Thank you for reaching out to us.

Based on your message, I understand that the “File is Uploaded” event isn’t being triggered when the “base 64 is not empty” constraint is applied in it. Could you please confirm if I’ve understood this correctly?

Indeed, it appears that the “base 64” state does not always become immediately available at the “File is Uploaded” event, there might be a brief delay until the state value is available(around 0.1s). For your specific use-case, you might consider triggering the event without the “only when” constraint, as it should be ready by the time the next action in the workflow is initiated. If it’s not, you could add a brief pause at the start of the workflow.

Could you please try these suggestions and let me know if they resolve the concerns you have? Also, if you have any further questions or concerns, please let us know.

Thank you once again, and I look forward to your reply.

Best regards,
Stefan

[Stephan]

Hello @obtrectation ,

I hope this message finds you well!

I wanted to follow up on our last conversation regarding the issue you were experiencing with the “Uploader uploaded” event and the Base64 data not being immediately available.

Were you able to try out the suggestions I provided? If so, did they help resolve the issue, or are you still facing some challenges? I’m here to help, so please let me know if there’s anything else you’d like to discuss or if you need further assistance.

Looking forward to hearing from you.

Best regards,
Stefan

[obtrectation]

Hi Stephan,

Thanks so much for your kind response. It’s been awhile since I’ve been able to look into this but tonight I tried updating to the new version and it doesn’t work. Still stuck on 2.119.0. I did follow your advice and removed the condition, but am still having the same result. What I’m seeing now is my AnalyzeUploadImage Upload (Settings) function (shown below) evaluates as true in the debugger, but shows as failed in the server log and does not run (checked with the logs at the Flask endpoint that function triggers). The imageData base64 seems to be transferring just fine and I have been running it with a 1 second delay to ensure it will have time to become available.

This does not happen on 2.119.0. Would love to hear what you think about this… thanks in advance!

[Stephan]

Hello @obtrectation,

Thanks for your message.

Great to see you back! I have re-examined all the details you provided in your first message and found that the cause of the state being empty is specifically related to the “Clear after uploading” checkbox from the element, which clears the state after the file is uploaded.

Could you please uncheck it and let me know how everything works for you afterwards? Also, you won’t need a pause or an additional “Only when” constraint, you can simply save the base64 state in the “File is uploaded” event.

Thanks, and I look forward to your reply.

Best regards,
Stefan Chiciuc
Support Team
Browse all Zeroqode Plugins for Bubble

[obtrectation]

Hi Stephan,

Thank you for this reply! I updated to the latest version and unchecked the “Clear after uploading” box. Unfortunately that did not fix the issue. Reverted back to 2.119.0 and am back up and running once again.

[Stephan]

Hello @obtrectation,

Thank you for your message.

I have further reviewed your concern to identify any additional functionalities that might be preventing the event from triggering correctly, but I wasn’t able to find the cause.

To further troubleshoot, could you please add our Support Team email to the list of collaborators in your application and share the app’s link with us? This will allow us to examine your settings and replicate them on our end to pinpoint the cause.

To add our Support Team as a collaborator, please navigate to the Bubble Editor, go to Settings, then Collaboration, and add support@zeroqode.com.

Additionally, please provide instructions on how to reproduce the issue on our side, including the name of the page where the plugin element and workflow are located, a short description of the steps to follow and where to click, and user credentials to log in for troubleshooting purposes. If possible, attaching a short Loom video demonstrating the issue would be very helpful.

Thank you for your understanding and cooperation. I look forward to your reply!

Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble