Methodical debugging?

Hello,
I built a relatively complex event planning app which i realised i don’t know how to effectively and efficiently debug. There are so many API workflows, roles, actions and scenarios which are intertwined. There is no way I can the gain confidence to launch by just playing around with its version-test.

What are your experiences with debugging complex apps? Is there a template / visualizing method for debugging which is standard practice?

Thanks

Ahh yes, debugging can get very tedious as apps get more complex.

With internal features (built within Bubble), using the debugger is very helpful and can help you diagnose and fix almost all issues.

With API calls, it gets tougher. Using the logs is helpful to find error messages when a call fails, but in the end, it’s a lot of trial and error.

1 Like

Thanks, glad to hear i’m not alone!
Yeah ive realised just how useful the debugger and server logs can be.
I’m not particularly worried of fixing the bugs once the’re found, I’m actually more worried about finding them in the first place. Ive found some really weird, rare, but catastrophic bugs while playing around with the app and I’m worried that i wont found all of these bugs by just looking around.

1 Like

Ya heard that! As much as we want to test as we go, sometimes it falls back in terms of priority.

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