Live Testing on device not starting at the initial screen

Hi Thunkable folks,
I’m seeing some evidence of what I’m experiencing in other forum posts here:

When doing live testing on the phone, my Thunkable app is not starting with the first screen of the app. This is a problem for testing because I’m using a navigator for most screens - but not the initial screens of the app, which are log in screens. So, by not starting on the first screen, live testing is bypassing my log in process and there’s no way for me to go back because I don’t want these screens to be part of my navigator.

Is this a known issue? Are there any good work arounds to make Thunkable begin testing on a specific screen, but not provide full navigational control to the user?

Hello @john_shelbyhtmq
I understand your frustration.
As I understand you are trying to test the login page but the app goes directly into the screens that are inside the navigator.
I think that if you have this screen first and you can’t see it maybe is because you are logged in, so adding a button to log out that will navigate you to the login screen will fix the issue.
Could you please try it and let me know if it worked?

On further testing, I think this is working for me. The confusion is maybe just due to how the Thunkable app syncs with website data.

To get the app to begin from the initial screen, I need to:

  • Exit the project if I’m currently looking at it on the device (go to my menu of projects).
  • Do something that causes the project to “refresh” while the Thunkable app is running on the device and device is awake - for example, change project design/blocks in some way while the Thunkable app is currently running on the device.
  • Wait a bit to make sure the refresh actually happened (there’s not a definite way to know if the sync went from website to device)
  • Reopen the project from the menu

Though this is working alright for me, a thing that would be nice in general is if there was a way on the device to know that the current version of a Thunkable project matched the website version (a timestamp when it last updated, maybe?)

1 Like

1000 times yes! I’ve mentioned this a few times before and it’s really hard to program and test projects without this.

See this related topic: Can Thunkable Live be fixed so it updates properly?

I’m sure you have all kinds of solutions for this, but -

On my end (and I recommend this to my students as well), I often just throw a “version number” label on to every screen I’m actively editing. When I need it to push changes to the device, I just add +1 to the version number while the app’s open. Changing visible text tends to force a sync - and in my past experience, changing blocks does not always (but it’s way harder to detect the update).

An “update timestamp” that appears in the bottom bar of the Thunkable app would be a nice way of automating what we’re doing as a work-around. Or an on-website button that gives feedback of a successful sync. Though the live update concept is flashy cool looking, I’d take a sync button that I have to press but with accurate feedback on success any day of the week.

Or maybe there’s a better way than what I’m doing that I don’t know about!

1 Like

I would agree that I’d much rather have control over when the project syncs then to have live syncing. Even if it worked perfectly – and it doesn’t currently – it’s just not a feature I really require. I’m much more interested in knowing without a doubt that the change I just spent five minutes working on actually exists in what I’m seeing on my phone.

@john_shelbyhtmq @tatiang Thank you for sharing your experience using the live app and for sharing some good suggestions!
I’ll pass them on to the team.