In Drag & Drop projects on Android, audio playback stops completely after exactly 39 sound plays. After this point, no further sounds will play until the app is restarted.
Platform: Android
Affected: Thunkable Live app (Android), exported Android builds (APK/AAB)
Expected Result:
Audio should continue playing indefinitely on each button press.
Actual Result:
After 39 plays, audio stops entirely
No further sounds will play
App remains otherwise functional
Only restarting the app restores audio
Impact:
High. Prevents use of sound effects/music in any moderately interactive app (e.g. games/music apps), severely limiting functionality.
Workarounds Tried:
Rebuilding in Snap to Place (works, but not viable for existing DnD projects)
No known workaround within Drag & Drop
Additional Context:
This issue has persisted for a considerable time. The suggested workaround (rebuilding in STP) is not practical for existing projects, and there is currently no way to convert DnD → STP.
Thanks for the bug report and the MVP project. I’ve made a bug report to our engineering team. I’ll update this thread when there is new information on this.
This bug is still reproducible on Android and it’s a pretty big blocker for any app using repeated sound playback. Has there been any progress or updates from the engineering team?
Hi @grant.mccallum,
I checked on the bug ticket, and it is still working its way through the queue. I have a meeting with the engineers this Friday and plan to bring it up. Thank you for your patience in the meantime.
@grant.mccallum
While I wasn’t able to move the bug to the top of the queue, I was able to expedite it a bit, and it was looked at last week. I checked in on the progress, and it appears the investigation uncovered a broader issue with sound that is impacting more than just X. The team is currently working on identifying the root cause for that broader issue. We will be sure to keep you updated as we learn more. Thank you for continuing to report issues.
@grant.mccallum
Brief update. The engineers have a fix, and it is set to release at the start of next month, provided there aren’t any delays from Apple. Thank you for your patience and reporting the issue.