Problem with Audio Radio Player

AlonsoC · July 10, 2020, 6:04am

Hi team:

I just purchased the Audio Radio Player and I’m running into an issue while trying to use it. Here’s what’s going on:

I added a Track element to a page in my app and entered the below address in the Dynamic Link field of the element. The link is from an MP3 file I uploaded to my database.

_ https://s3.amazonaws.com/appforest_uf/f1594358076713x641830067050555600/Funk%201.mp3 _

I then created a play and stop button on my page. Then I created these workflows to start and stop the audio:

Play button workflow:

Stop button workflow:

But then when I preview my page to test the audio player, the debugger already shows 2 errors

These are the errors the plugin is throwing:

I appreciate your help in solving this issue. Thanks!

alexandru · July 10, 2020, 10:52am

Hi @AlonsoC,

Thanks for reaching out. Unfortunately, this issues are not reproducing on our side. Could you please make sure that everything is configured properly. You can check our demo here and its editor here to preview all settings and understand how plugin works. Perhaps you can try to replicate on your side, or at least see how links are set. Then give it a try again.

However, if you still experience the same or other issues, please share more details like workflow action settings, the exact steps to reproduce this errors, console logs of your browser, browser version and OS you’re using for developing your app. This way, we can get a better troubleshooting and provide a feedback asap.

Best,
Alex

AlonsoC · July 10, 2020, 3:01pm

Hi Alexandru:

I’m still having issues with this. Here’s a little more information.

OS and Browsers
Windows 10.0.18362 Build 18362
Firefox 78.0.2 (64-bit)
Chrome 83.0.4103.116 (Official Build) (64-bit)

My Bubble app is a fresh install and the only plugin I have installed is Audio Radio Player.
If I create a new page, with no elements and simply drop a Track element, I see errors in the debugger both in Firefox and Chrome, like so:

Firefox:

Element Track A
The plugin Audio Radio Player / element Track threw the following error: anonymous@PLUGIN_Audio-Radio-Player-update-----Track-.js:3:1
q/c.initialize/</</</<@https://dhtiece9044ep.cloudfront.net/package/run_debug_js/5a0d7b7ebef9941342bea49c5ed7d780c1d1250dce64333db0560968631f227b/xfalse/x7:18:469575
L@https://dhtiece9044ep.cloudfront.net/package/run_debug_js/5a0d7b7ebef9941342bea49c5ed7d780c1d1250dce64333db0560968631f227b/xfalse/x7:18:458232 (please report this to the plugin author)

Chrome:

Element Track A
The plugin Audio Radio Player / element Track threw the following error: TypeError: Cannot read property ‘setTrack’ of undefined
at eval (PLUGIN_Audio-Radio-Player-update-----Track-.js:3:14)
at https://dhtiece9044ep.cloudfront.net/package/run_debug_js/5a0d7b7ebef9941342bea49c5ed7d780c1d1250dce64333db0560968631f227b/xfalse/x7:18:469575 (please report this to the plugin author)

As you can see, I get errors both in Chrome and Firefox, however they’re not exactly the same. Before I go through the process of configuring my page just like on your example, can you please confirm if you get the same errors as me when simply dropping the Track element on a fresh page?

Can I uninstall and reinstall the plugin to see if this helps? Will I have to pay for the app again if I do this?

Thanks!

alexandru · July 10, 2020, 3:40pm

Hi @AlonsoC,

Thank you very much for provided feedback. Let us investigate and I’ll notify you back on this matter ASAP.

This is something we shall test as well. As for this one:

You can easily re-install the plugin in the same app and you’ll not be charged again. You’ll have to pay only when creating a brand new project, but you don’t have to.

Also, could you please go to Settings - Collaboration tab within your editor. Add our support@zeroqode.com account to your collaborator’s list. Also, please tell us your app name and page name where this problem occurs on test.

Note: avoid the warning message regarding plan, as we are an agency and you can easily add us to your collaborators.

We’ll investigate it inside your app as well and get back to you with a feedback asap.

AlonsoC · July 10, 2020, 4:15pm

Hi Alexandru:

I’ve gone ahead and added support@zeroqode.com as an admin to the app. Below is the info you requested.

App name: Music-loops
Page name: audio_test

On that page I’ve created 2 use cases and neither of them work.

1. Group Static: here I simply uploaded a track directly to the Track element, and then created play and stop buttons and added workflows to play or stop the Track element.

2. Group Data: here I set the source of the Track element to do a search of the data type “Track” which is where I’ve stored mp3 files in my Bubble database and selected the first item file on the results. Then I created dedicated play and stop buttons with workflows.

Thanks for your help!

AlonsoC · July 10, 2020, 9:50pm

Hi Alexandru:

I think I found where the problem is but not how to solve it. When I go the demo page for Audio Radio
https://zeroqode-demo-19.bubbleapps.io/version-test/audio_radio?debug_mode=true
.
and use the debugger to inspect the Track element, I see that it shows a link in the Playing Source

.

However on my page, the Track element shows an empty Playing Source.
.

No matter what I do I can’t seem to find how to to set the Playing Source to my Track elements, maybe it’s a plugin bug that it’s not using the file set within the element properties as the Playing Source. In case it’s helpful, I’ve created another page in my app mimicking the use of a repeating group like on your demo. The page is “audio_test2”.

Hope you can find an answer to this soon. Thanks!

alexandru · July 13, 2020, 10:21am

Hi @AlonsoC,

Thanks a lot for provided feedback. We’ve tested your application and it is throwing 2 errors on page load without involving any actions to reproduce it. This ‘Playing Source’ hint might speed things up. I’m afraid it is a plugin related bug, but please let us investigate and I’ll notify you back as soon as possible.

Thanks in advance for your patience.

alexandru · July 14, 2020, 8:01am

Hi @AlonsoC,

We’ve pushed another plugin update with some minor fixes. Please upgrade to the latest version, refresh your app and give it a try.

Thanks!

AlonsoC · July 15, 2020, 4:47am

I updated the plugin and tested again and it now works. I’ll let you know if I run into any other issues. Thanks!

alexandru · July 15, 2020, 6:48am

Hi @AlonsoC,

Thanks for feedback, I’m glad it worked. If you like our plugin so far, could you please rate it by going to Plugins tab in Bubble editor. You can find the plugin by name and give it as many stars as it deserves. The more feedback we get, the more motivated we are to build great plugins!

Thanks