It’s been a while since I reported a bug about a month ago. We had extensive discussions with the support team, and I appreciate their responsiveness.
We managed to handle the issue by wrapping mutated data into JSON, converting it to CSV, and then using the CSV upload action. Now, as we’re deploying the second feature, we’re facing the same issue, but we don’t want to use the same approach due to security concerns, as it all happens on the front end.
Is there any other solution while keeping the native features?
What is the progress of the engineering team on this?
As the app grows, it’s slowly falling apart, and we’re starting to consider other tools like Xano, AWS, or a custom Node.js app( we already did that).
However, we’d generally like to avoid that, as it impacts our timelines.
If I remember correctly, the app/company you’re working for is fairly tech debted (I’ve audited it before) which would explain that. It’s unlikely that it’s changes in Bubble that have triggered bugs, but rather new features (or old features with bugs that were never caught).
Limited, they thought they deployed a fix, but then the issue still occurs so it’s being reinvestigated. I say limited in terms of results - they might’ve put a ton of work in behind the scenes but just not been able to identify the problem.
I don’t know the specifics of what you’re trying to do, but Create a list of things via API connector is powerful, and if not, as you note, a little serverless function or Xano function can do heavy data processing for cheap, and do it quicker than Bubble would do it.
