i have a startup screen with a timer on that screen and my app just keeps looping when live testing it i am at a lost why is this happening i had the same screen for 4 years i have change nothing, but the app is acting differently now ??
Everything was working OK but since i checked my app recently. I found some issues with the Timer component.
If click correct answer it will have ‘Good Job!’ sound but when I click the incerrect answer just once. I found the issue is ‘Try again sound’ (It’s play up with the answer is incorrect) play all the game.
I confuse so much becase the code is used to find . I wonder how can I slove this ploblem and why I got this ploblem.
I’m facing an issue while using Thunkable and creating a Tab Navigator with tabs for “Home,” “About,” “Contact,” and “Setup.” In my project, I’ve set up a specific image to be displayed when clicking on “Home” and another for “About.” However, when I click on “About,” the image opens as intended, but after a few seconds, the navigation automatically returns to “Home.”
I would like to understand why this is happening and how I can ensure that the image remains on the “About” screen until I manually decide to return to the “Home” screen. I appreciate any help and guidance in resolving this issue!
Yes, i tried both the enable true/false button and the stop button.
When i open new screens i have added just in case the blocks for disabling the timers, but they still count (even though they are supposed to stop after few seconds automatically)
I have also tried to check if they were enabled, but using these blocks they both say they are disabled
But clearly affected from a timer if i move using the bottom tab navigator, after few seconds i am brought back to homepage with no reason
EDIT
i have also disabled all the blocks in the splash screen an home screen, with literally no actions to be taken if screens open.
Still the same issue, after few seconds if i push any button on the bottom tab navigator, it leads me back to the home screen.
Apparently in the homepage, even i no actions is taken, it refreshes itself as AdMob keeps on loading/updating
So i test it out on a third phone firstly the live
App was not updated yet and i had no issues but as soon i update the looping thing happen.
The screen in question only have a timer to move to next screen if the person did not put in a username so it also uses local storage to save that info.
With a timer or with your project navigating back to the original screen in the app when viewing this on Thunkable Live?
@maurizio.polverini89 There is a current known issue with navigation in the Thunkable Live app, this sounds similar. Users are experiencing an issue where if they complete an action to navigate to a different screen, they are sent to the next screen but then automatically sent back to the previous screen. Does this sound like the issue you are seeing?
It sounds slighly familiar but with these differencies:
doesnt matter how many screens i open or navigate, i’ll always be sent back to the home screen after the same amout of seconds (around 6), that’s why i thought it was the timer
For instance if i open another screen straight away, i’ll be in that screen for 6 seconds, if i open it after 5 seconds the homepage started, i will be in that screen for 1 second.
i disabled all the blocks while “when screen opens” so when i open the app in thunkable live it doesnt properly do any actions but still i’m brought back to the homepage (the first one of the tab navigator)
Hope it can help for your fix
Thanks again for your help
If you want to take a look yourself i can share the project link
Thanks @maurizio.polverini89 – part of the issue is that we are not always able to replicate this with our own apps. We are attempting to figure out how to consistently replicate the issue first.
I appreciate you taking the time to give this detail on your issue. I am not sure if it is specifically related to the timer yet but it is a known issue. We are currently working to replicate the issue on our end and will update you here once a fix is discovered. Thank you!
@adilsonsantana Thanks for flagging. This is a known issue that we are currently working to replicate on our end. I will update you here as we learn more. Thanks again for your patience!
