If you’re having issues with custom components, I figured it out. Custom components aren’t always initializing component variables when they are not located on the first page. The workaround I did was to create a function that sets all variables to their initial state.
Do you mind giving an example of this?
Hello @tthompson41231 
The issue is that on the variable name, you are using a question mark.
As it is mentioned in our docs “Variable names can only contain alphanumeric characters and underscore. Invalid characters may cause your app to crash.”
Interesting, I use question marks all the time and have never had an issue. I removed the question marks but this bug still exists. Variables are not being initialized on second page and on.
Can you test out this example component on screen 1 and 2? Maybe its just on my end.
Set up as shown below
https://x.thunkable.com/component/65805471e7fa09ebbabfcb8b/
These are the components blocks
Hi @tthompson41231, our apologies that this message got lost in the shuffle. Yes, I can see where I get the null conditional if this CC is added on any screen other than the first. We’ll take a look and see if this needs to be fixed or what is going on here. Appreciate your patience!