[SOLVED]Sound blocks - the wrong sound file is being played

I am trying to create a basic drum machine style app.

Here are the blocks

Here is the layout

If I click ‘rim’ > ‘kick’ > ‘rim’ it will play ‘rim’ > ‘kick’ > ‘kick’
If I click ‘kick’ > ‘rim’ > ‘kick’ it will play ‘kick’ > ‘rim’ > ‘rim’

I am waiting over 2 seconds before pressing the next button just to make sure the file has finished playing.

What is the purpose of the wait blocks? What happens if you remove those?

Can you share a link to the project?

The wait blocks are just a left over from trying to troubleshoot. I had any potential error appear after 2 seconds so I knew when the file would have finished playing.


Seems like a pretty clear bug to me. Your blocks are really simply and there’s nothing else I can see that might contribute to an issue such as a special character in the filenames.

It’s highjacking the sound file after the second click:

  • If I click ‘rim’ > ‘kick’ then every click of either button after that will be ‘kick’
  • If I click ‘kick’ > ‘rim’ then every click of either button after that will be ‘rim’
1 Like


I have the same bug.
It started only in December (or maybe November, not earlier).
Project (it has worked for 2 years without any bugs):

1 Like

This issue still exists. Please, fix it!

This is still an issue.

Hi @classlessteacher, thanks for your patience.

There are a lot of issues to sort out with our sound component and I do apologize. The engineering team is currently working on getting these all sorted and once they do, we’ll update our documentation and give a notice here as to the intended implementation and behavior using the sound blocks.

1 Like

Hello @classlessteacher @schoolcodeclass2mgk1 @liyuoplbsd @tatiang
Thank you again for your patience. I would like to let you know that we have now officially released a fix for this bug.

Please keep in mind that you may need to do a hard refresh of your browser for the changes to take effect in your project. If this issue is present on the Thunkable Live app, you will want to update that through the App Store and/or Google Play Store before any changes will occur. 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.

Good morning,
Thank you for the update, unfortunately it still has not fixed the issue.

Hello @classlessteacher
It seems that the issue is only on the advanced blocks.
Could you please try regular sound blocks?

1 Like

Thank you, this resolves the issue.

1 Like