+2
Fixed

shortcuts don't work after phone factory reset

Fred Rosenberg 5 years ago • updated by Jona (Lead Developer) 4 years ago 3
Good Day,
XiiaLive and favorites and favorite station shortcuts all working properly, did a save, factory reset the phone, downloaded xiiaLive, restored from XML.  Most favorites work, no created shortcuts work.  Read the online help database, played each favorite to make sure it worked, created new shortcuts...and get INVALID URL.

Can you help please?

Thank you for your time and consideration,
Fred

Answer

Answer
Fixed
UPDATE 12/08/13
I was able to find the issue and I have resolved it. The fix will be part of the next release v3.1.1. Thanks everyone for all the details provided.
Under review

Thanks for the detailed info. Could you provide the device name and what version of Android is running?


Also, it might be helpful if you don't mind sending us the xml backup. It might help us reproduce the issue quickly. If you can then mention which station you made a shortcut should speed up the process. Please send it to xiialive@visualblasters.com.

Good Morning,

Thank you for your quick reply!

System Version on my phone is 5.7.906.XT862.Verizon.en.US.  

Android Version is Android 2.3.4

Model Number is DROID3


The following stations (these are the most important to me.  No comments on my taste please!)  all work from XiiaLivePro and shortcuts:


Sonic Universe Nu Jazz

Swiss Internet Radio

WORM Boston


The following work in XiiaLivePro but do not work in shortcuts:

WAMC

WFCR-MP3

WGBH Boston

WBUR


I just tested to make sure this data is accurate.  First I played each station via XiiaLivePro directly, then I created a shortcut.  While playing WAMC via XiiaLivePro directly, I noticed "INVALID URL" briefly flash on the top status bar just before it started buffering and then playing.  It was a very brief flash, and it only happened once in several tries.  I thought I saw a possible pattern (stations with an intro redirect don't work as a shortcut, and those without a redirect work)...


I then tested to see how the stations were streaming on line.  I used the m3u option for each stream.  I am running WIndows 7 64 in Virtual Box hosted on an Ubuntu 12.04 host:


WAMC http://wamc.org/listen-live-wamc (has a redirect)

WGBH http://www.wgbh.org/AUDIOPlayers/WGBH.cfm (has no redirect)

WFCR http://www.publicbroadcasting.net/wfcr/ppr/index.shtml (has a redirect, but we never get to the live stream)

WBUR http://www.wbur.org/listen/live (no redirect) Using the M3u option under General (Windows, Linux).


My theory is wrong.  I now leave it in your hands.  I will send the xml as requested soon.


Thank you for your time and consideration,


Fred


I



Good Morning,

Any progress on this?   I really miss this previously working feature.

Are you waiting for anything from me?

Thank you for your time and consideration,

Fred


I just sent you an email. Thanks for the details. I will be looking into this issue.
Under review
UPDATE 12/08/13
I was able to find the issue and I have resolved it. The fix will be part of the next release. Thanks everyone for all the details provided.

Thanks for the detailed info. Could you provide the device name and what version of Android is running?

Also, it might be helpful if you don't mind sending us the xml backup. It might help us reproduce the issue quickly. If you can then mention which station you made a shortcut should speed up the process. Please send it to xiialive@visualblasters.com.

Fixed
UPDATE 12/08/13
I was able to find the issue and I have resolved it. The fix will be part of the next release v3.1.1. Thanks everyone for all the details provided.

Thanks for the detailed info. Could you provide the device name and what version of Android is running?

Also, it might be helpful if you don't mind sending us the xml backup. It might help us reproduce the issue quickly. If you can then mention which station you made a shortcut should speed up the process. Please send it to xiialive@visualblasters.com.

Answer
Fixed
UPDATE 12/08/13
I was able to find the issue and I have resolved it. The fix will be part of the next release v3.1.1. Thanks everyone for all the details provided.