# Thunkable Live app crashing

**URL:** <https://community.thunkable.com/t/thunkable-live-app-crashing/2517045>\
**Category:** Issues / Bugs\
**Created:** [July 24, 2023, 2:54am UTC](https://community.thunkable.com/t/thunkable-live-app-crashing/2517045 "2023-07-24T02:54:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tatiang](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/tatiang/32/55482_2.png) [@tatiang](https://community.thunkable.com/u/tatiang)\
**Post date:** [July 24, 2023, 3:01am UTC](https://community.thunkable.com/t/thunkable-live-app-crashing/2517045/2 "2023-07-24T03:01:38Z")

</div>

That usually means you have chosen blocks that crash your project. I use this method to find the cause:

> [@Debugging in Thunkable X (Video)](https://community.thunkable.com/t/debugging-in-thunkable-x-video/849471):
>
> I thought I’d share a process I use for debugging my projects. It involves creating a function that can be used over and over throughout the code blocks in order to help determine where things are going wrong, whether or not certain blocks are ever triggering, and what the values of several variables are. Here’s a screenshot of what I’ve set up: The real power comes from being able to quickly change the delay (and even set it to 0 seconds) or just remo…

---

_[View the full topic](https://community.thunkable.com/t/thunkable-live-app-crashing/2517045)._
