This has been going on for months and it has not been resolved. Anyone else still having this issue?
This has been an issue for a while. For example, check your little indicator. If you do a workflow that updates this field, does it work right away or do you need to update the page?
This is pretty frustrating since I have had an open ticket for weeks, then all of a sudden they say it can’t be reproduced. They just ran out of test data to do the test. Seems like they haven’t been able to fix it. Seems like most of these topics are closed as well. So I can’t comment on them. Thus the need to open another topic for discussion. Anyone else facing the same issue here?
Oh, I didn’t get this, hopefully it is actually fixed.
Has anyone seen it in the last couple of days?
It’s because they couldn’t reliably reproduce it = too difficult to debug = not worth the time. I mean I get it, I know how much of a pain in the ass it is to diagnose bugs in my own app when I can’t reliably reproduce them and that only has a couple of moving parts - in Bubble’s backend it’ll be harder. But still, it’s a critical functionality…
Ah gotcha, I saw the thread moving around and saw it in my app but didnt submit a bug report it didnt really bother me that much i guess, but i can see for apps that rely on the real-time updates it being an issue
You know it already but do file a bug report, and send a screen recording to Bubble that is undeniable evidence of it still happening.
Yep. This seems likely, as they’re like ‘users stopped reporting’ → no longer occurring, when actually we’ve all reported it, and our tickets are still open…
Thanks for bringing this up again. It just happened to me and I spent 30 min troubleshooting an item not showing up in the database dashboard. After a browser refresh the darn thing showed up. Frustrating.
I pity the devs who have to maintain a high-traffic app that relies / expects data to be updated the normal Bubble way.
@J805@rico.trevisan@georgecollier perhaps an idea to share how we al can easily reproduce this, ideal would be if one of you guys can setup a simple test app. If you share it here we can all file a bug report and include that simple app url/app name. This way we can work together to get this fixed asap without taking it too much time setting it all ready for bubble. And let’s share progress in this thread as well (communication from Bubble) so we can see progress in a transparant way
That is a good idea but not something that works in practice. There are times a bug in Bubble can be app specific, meaning only that single app experiences it, other times it can be system wide, meaning all apps experience. The majority of the time it is something in-between. I doubt Bubble support would entertain bug reports from multiple users based on the same app.
I think we are speaking about a bug that all apps have. In that case I see no reason why Bubble will not accept a reproducible bug report. I still believe that Bubble does not purposefully stop working on bugs. I think that lots of people are screaming to deliver. Perhaps even more so internally. Therefore it is good to work together and make very clear what matters to us as users. What bugs need a fix.
Should Bubble say, it is a bug but we will not fix it. That’s fine, at least we know we cannot build with those features.
If multiple users are reporting a bug from the same app, and those multiple users are not all collaborators on the same app, that may not be the best approach to incentivize them.
Instead, best approach, any user that has an app with this reproducible issue, should submit their bug report about their app so that Bubble engineers have more examples to use as a way of more confidently resolving the issue, as underlying causes between different apps may be slightly different and could lead to engineers uncover the root cause.
Just generally not a good idea to call for people to submit bug reports about the same app.
I’m happy to use a test app and make a bug report.
In the meantime, there’s some unusual activity going on behind the scenes. I’ve had multiple issues with both the dev and live apps in th last two hours and have even had the dev app stating that it has been updated while I am testing it, having made no changes! … a twin peaks soundtrack plays in the background…
Yeah. I did the big report, did a screen recording, walk through steps. Then after a few weeks they just said that it wasn’t reproducible because they ran out of test data examples. Very frustrating. I have two apps with this issue and one is extremely important. Very sad about this. Trying to get their attention so they actually do something about it.
it didnt really bother me that much i guess, but i can see for apps that rely on the real-time updates it being an issue
