Here’s the problem… you have to think of every block as a function. Each block is in essence returning a value. So when you do this:
Then Thunkable compiles those blocks by first getting the value of app variable 1st counter (let’s say it’s 0) and then looking for an app variable with that name (in this case, app variable 0) but it doesn’t exists so it fails.
When you change an app variable, use the change app variable 1st counter block at the top of the Variables drawer rather than the dynamic block at the bottom that requires a variable name.
No. This is sorely needed and has been requested before.
I use a workaround method for stepping through the code and debugging a project. The link is below.
·····················································································································
Need help? How to Ask Great Questions 
Debugging A Project API JSON Tutorial
Want to hire a Certified Thunkable Expert? Elevate your app with Tatiang on Fiverr