I set up several downloads, it finds the episodes but I get a com error message or just the gear whith the red x when I try to download them. Any suggestions?
The CommErr is typical when there is no network connectivity. The red X can be caused by no network activity or a bug that we are currently working on fixing that can occur when the phone goes to sleep. It seems to drop the network connection at that time. We are going to see if we can suppress the sleep when a download is in progress.
So watch for an update during the next couple of days and see if that resolves the issue for you.
If not, let us know and we'll keep working to resolve it.
I'm getting a very similar issue to this one. I added the feed, and it loading the episode list just fine, but when I try to download, it tries to download like 3 times, then I get a red X over the download gear, and it says "Download failed", then "partial" over the episode gear. The rss url is:
We store the audio files on the SD card based on the filename provided in the RSS feed. This RSS feed has some characters in the filename that are not allowed by the phone operating system, so when we go to save it, the save fails.
I added this to the bug list. We'll get it fixed for you.
Is the manual up to date with all the features? I am reading about features in the manual that you mentioned working on in the forums, but not sure if you were writing ahead of release... (I just picked this app up today).
The manual was updated just prior to the current release, so the manual matches version 1.0.205. Good point about the version number of the manual, I just added a note in the manual to reflect which version number it applies to.
Regarding the podandgo podcast, I am seeing the same error in my emulator. I'll let you know what I discover, thanks for bringing it to our attention.
It turns out that the host of the podcast is doing something invalid in the response coming from their web server, but it's easy to detect and work around. I've got it fixed, will go out in the next release.
The CommErr is typical when there is no network connectivity. The red X can be caused by no network activity or a bug that we are currently working on fixing that can occur when the phone goes to sleep. It seems to drop the network connection at that time. We are going to see if we can suppress the sleep when a download is in progress.
So watch for an update during the next couple of days and see if that resolves the issue for you.
If not, let us know and we'll keep working to resolve it.
I'm getting a very similar issue to this one. I added the feed, and it loading the episode list just fine, but when I try to download, it tries to download like 3 times, then I get a red X over the download gear, and it says "Download failed", then "partial" over the episode gear. The rss url is:
http://www.wtks.com/podcast/tuddleoldskool.xml#
All my other feeds work, but this is my favorite!
We store the audio files on the SD card based on the filename provided in the RSS feed. This RSS feed has some characters in the filename that are not allowed by the phone operating system, so when we go to save it, the save fails.
I added this to the bug list. We'll get it fixed for you.
is there a place were we can view the status of bugs and such - i think i am getting this same issue with the podcast at http://www.podango.com/feeds/feed.php?pid=2874&amid=1&returnType=all
Is the manual up to date with all the features? I am reading about features in the manual that you mentioned working on in the forums, but not sure if you were writing ahead of release... (I just picked this app up today).
To see the current known bugs, look here - http://www.snoggdoggler.com/?q=node/26
To see which versions were released and what was fixed in each one , look here - http://www.snoggdoggler.com/?q=taxonomy/term/4
The manual was updated just prior to the current release, so the manual matches version 1.0.205. Good point about the version number of the manual, I just added a note in the manual to reflect which version number it applies to.
Regarding the podandgo podcast, I am seeing the same error in my emulator. I'll let you know what I discover, thanks for bringing it to our attention.
It turns out that the host of the podcast is doing something invalid in the response coming from their web server, but it's easy to detect and work around. I've got it fixed, will go out in the next release.
Sorry for the trouble.