# How to asign properties to objects correctly

**URL:** <https://community.thunkable.com/t/how-to-asign-properties-to-objects-correctly/1848090>\
**Category:** Questions about Thunkable X\
**Tags:** firebase, i\_need\_your\_help\
**Created:** [April 25, 2022, 6:45pm UTC](https://community.thunkable.com/t/how-to-asign-properties-to-objects-correctly/1848090 "2022-04-25T18:45:49Z")\
**Posts on this page:** 1\
**Showing post:** 11

<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:** [April 25, 2022, 10:04pm UTC](https://community.thunkable.com/t/how-to-asign-properties-to-objects-correctly/1848090/11 "2022-04-25T22:04:20Z")

</div>

There must be something else deleting those nodes from Firebase. Check to see that you don’t have any stray blocks assigning values to Firebase paths. Is anyone else you know using the project or a copy of the project that can access Firebase?

If you can’t figure out the cause, start to slow things down. Add wait blocks so that you can watch the Firebase values to see when they change. It helps to do something visual on the screen like change a label’s value right before the wait block so you connect that to what is happening in Firebase. This is the method I use for debugging blocks: [Debugging in Thunkable X (Video)](https://community.thunkable.com/t/debugging-in-thunkable-x-video/849471).

---

_[View the full topic](https://community.thunkable.com/t/how-to-asign-properties-to-objects-correctly/1848090)._