I wanted to report a performance issue that started immediately after updating to the latest Thunkable Live app (v530).
Since the update, all of my apps have experienced a noticeable slowdown - particularly with screen transitions. Previously, transitions were almost instant, but now its not uncommon for transitions to take 1-2 seconds to load. This happens across multiple projects, including ones that were running smoothly before the update.
I’ve tested this on the same device, with no other changes besides the Thunkable Live version. The slowdown appears to be directly tied to v530.
Could the team please look into this? Smooth screen transitions are critical to the user experience, and this regression is pretty significant.
Happy to provide more details or run tests if needed.
Thanks!
I can now confirm that this slowdown is not limited to the Thunkable Live preview. It is also affecting exported APK builds. I have a recorded video showing the exact same project, with zero code or design changes, loading in one second in an APK exported two weeks ago and taking roughly ten seconds in an APK exported today. I can share this privately if needed, as the app belongs to a client and I cannot post the footage publicly due to NDA restrictions.
Short version:
Previous APK load time: 1 second
Current APK load time: 10 seconds
No changes were made to the project between these two builds.
This strongly suggests that something in the recent runtime or build pipeline has caused a performance regression. Please escalate this to engineering as an urgent issue, because it directly affects production apps and client deliveries.
Happy to provide any additional information you need.
We need answers please. It’s been almost 24 hours since this problem occurred and it has completely stopped us from being able to work. This is urgent.
Just checking in again as there’s been no update yet. This slowdown issue has now been affecting multiple developers and clients for over 72 hours, and it’s completely halted active projects for us.
I have been unable to test, publish updates, or deliver builds to clients until this is resolved, so it would be really helpful to get a status update from engineering, even if it’s just confirmation that the cause has been identified or an ETA on the fix.
We’re now on Day 5 of this slowdown issue, and we still haven’t received an update from engineering. This regression continues to block active client work, testing, and publishing. At this point I’m having to delay paid project deadlines, which isn’t sustainable.
Can we please get a clear status update, whether the issue has been identified, what the current fix progress is, and whether you have an estimated timeframe? Even a brief technical summary from engineering would go a long way.
This is a critical production-impacting issue for several of us, and I need visibility so I can plan client work accordingly.
Hi @martint , thanks for confirming, that lines up with what I’m seeing too. It seems to hit apps with local storage tables particularly hard, but the slowdown is noticeable across all devices, especially anything that isn’t high-end.
@ioannis we’re now on Day 10 of this issue, and the last update was that engineering were “looking into the root cause.” Ten days should be more than enough time to at least establish what the underlying problem is, even if a full fix isn’t ready yet.
You mentioned you would follow up with an update, so could you please let us know where things currently stand? Since then, v531 of the Live app was released, which unfortunately didn’t resolve the slowdown and has introduced some other smaller regressions. (I’ll make a separate thread on this.) Once again, there were no patch notes or communication about the changes.
We really do need transparency here. This is affecting production apps and client work, and without any clear information it’s almost impossible for us to plan around it.
Hello everyone,
The engineers have found a solution and will release it soon so you can test it.
I will provide an update as soon as possible.
Thank you for your time and patience in this matter.
Hi @ioannis, thanks for the update, that’s good to hear.
When you say the engineers will release the solution “soon,” could you give us a rough sense of the timeframe? I understand you won’t have an exact date, but even knowing whether we’re talking hours, days, or weeks would help me plan client work and manage expectations.
I would like to let you know that we have now officially released a fix for this bug.
If your downloaded or published app is affected by this bug, you will need to re-download or re-publish your app for these changes to take effect.
Please be aware that the Thunkable Live app is not updated yet.
Let us know if you have any other questions or feedback for us.
Android but after testing further it does appear better on some other screens.
My original issue may be that now the screens are performing a slide transition it is showing up an issue where the app is continuing to run an ‘else’ command after it has received the instruction to go to next screen and the delay is due to it waiting til the blocks in the else command have completed.