# Debugging Crashes in live view

**URL:** <https://community.thunkable.com/t/debugging-crashes-in-live-view/1253058>\
**Category:** Questions about Thunkable X\
**Created:** [April 29, 2021, 2:08pm UTC](https://community.thunkable.com/t/debugging-crashes-in-live-view/1253058 "2021-04-29T14:08:55Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)\
**Post date:** [April 29, 2021, 2:34pm UTC](https://community.thunkable.com/t/debugging-crashes-in-live-view/1253058/8 "2021-04-29T14:34:33Z")

</div>

Yes,  
Thunkable does not know what to do when it encounters `null`. This is the reason you get the crash.

So unless you do not deliberately want a `null`, you should avoid it in the code.

---

_[View the full topic](https://community.thunkable.com/t/debugging-crashes-in-live-view/1253058)._