Services Plugins FAQs

AWS Uploader hangs when the Current User's email is used for the folder name

I’m not sure if something has changed but the below configuration worked a couple weeks ago and now does not. If I remove the folder name or make it anything but an email address, it works, otherwise it stays stuck in an uploading state. Perhaps there’s a new issue with using an ampersand in the folder name? I’ve also tried upgrading to the newest plugin but that didn’t solve the issue.
image

Thanks in advance!

Hi @dalbrecht,

Thanks a lot for reaching out to us and happy 2025 :star2:

I was able to reproduce this behavior on our end. From what I’ve found, it seems to be related to the “.com” at the end of the email. You can try adding a random string like ajskdhaksj.com as the folder name, and you’ll experience the same issue.

I’m not sure where this is coming from, but an investigation task has been created to delve deeper into this behavior and provide a fix. I’ll get back to you with more information as soon as it’s available! Thank you for reporting this to us!

Please let me know if you have any questions or concerns in the meantime, or if you need any assistance :hugs:

Best regards :sunflower:

Browse all Zeroqode Plugins for Bubble Banner_Last3

Hi @dorel, great to hear from you again and Happy New Year! Thanks for looking into this. I wonder whether it’s a special character issue in general - I haven’t confirmed that though. It’s so weird because I’m certain it was working a couple weeks ago.

I’m not sure if it helps the developers prioritize this, but being able to pass the user’s email in the file name is critical to my application. If I can’t resolve it soon I’ll have to go and build out my own functionality for it.

Hi @dalbrecht,

Thanks a lot and apologies for the delayed reply over the weekend :pray:

I’m not sure why this behavior started happening, and I don’t think it’s because of any special characters. As mentioned earlier, after my testing, I noticed that adding “.com” to the end of folder name completely breaks the uploading process.

The issue seems to have appeared suddenly. I am aware of usecases that also use the email as part of the folder in older versions, and it worked as expected. Also, I have tested with previous version where I knew that the email as folder name has to work, however, it still did not. My guess is that Bubble made some changes that affected how the folder name is processed.

Unfortunately, due to the holiday season and increased workload for the developers, I’m not sure they’ll be able to prioritize this issue. However, I’ll still send a message to the developers to try and update it as soon as possible. I’ll let you know as soon as I have some more information!

Please let me know if there’s anything else I can help you with :hugs:

Best regards :hibiscus:

Browse all Zeroqode Plugins for Bubble Banner_Last3

Oh wow, you’re right, it’s literally the string .com that causes the error. In the meantime I have found a workaround by using Bubble’s string replacement functions on the current user’s email, and then re-encoding the email on the backend. It’s inconvenient but at least it works.

I appreciate anything you can do to help! Thanks @dorel!