"Cant Parse Feed"

Im trying to submit my feed to itunes but it keeps giving me the Cant Parse error: http://w3gmspodcast.000webhostapp.com/feed.xml there is my feed

Posted on May 3, 2018 4:41 PM

Reply
Question marked as Top-ranking reply

Posted on May 3, 2018 11:43 PM

Your first URL isn't a properly constructed feed at all. The second is nearer to it, having the 'iTunes declaration' at the top. However there are numerous errors: please see this FeedValidator report. Looking at the line numbers there:


Line 14: this tag should contain an 'itunes:email' tag with your contact address. You may be able to omit this.


Lines 17 and 19: You must stick to the categories listed here.


Line 20: this is OK, FeedValidator doesn't know about this new tag.


Line 26: the 'length' attribute must be the file size in bytes. The media file URL is OK (FeedValidator doesn't like https but it's in fact recommended). Your filename has spaces in it, and though the feed has correctly handled this by substituting the code %20 it's better not to have them in the first place: however it isn't actually a problem. Incidentally your file starts with an 8 second pause and this isn't a good idea.


Line 33: you can ignore this the 'atom' link, but you should have an 'itunes:explicit' tag set to 'no' unless you have strong or sexual language in which case it must be set to 'yes' for each affected episode and the whole podcast.

4 replies
Question marked as Top-ranking reply

May 3, 2018 11:43 PM in response to Technogizguy

Your first URL isn't a properly constructed feed at all. The second is nearer to it, having the 'iTunes declaration' at the top. However there are numerous errors: please see this FeedValidator report. Looking at the line numbers there:


Line 14: this tag should contain an 'itunes:email' tag with your contact address. You may be able to omit this.


Lines 17 and 19: You must stick to the categories listed here.


Line 20: this is OK, FeedValidator doesn't know about this new tag.


Line 26: the 'length' attribute must be the file size in bytes. The media file URL is OK (FeedValidator doesn't like https but it's in fact recommended). Your filename has spaces in it, and though the feed has correctly handled this by substituting the code %20 it's better not to have them in the first place: however it isn't actually a problem. Incidentally your file starts with an 8 second pause and this isn't a good idea.


Line 33: you can ignore this the 'atom' link, but you should have an 'itunes:explicit' tag set to 'no' unless you have strong or sexual language in which case it must be set to 'yes' for each affected episode and the whole podcast.

May 5, 2018 11:45 PM in response to Technogizguy

Although a couple of validators pass the feed, examining it in PageSpinner shows that in some cases you have an odd character in place of the normal line return:

User uploaded file

This operates as a line return in most readers including TextEdit, but it's an invisible character which shouldn't be there. In two cases in this extract it's inside a tag. I don't know exactly how this has arisen, but it's likely to be the problem. This sort of thing can happen if you construct your feed in a word processor - these can insert invisible characters.


Incidentally Podbase reports that your image is 1024 x 1024 px - this will get you rejected: the minimum is 1400 x 1400.


Your media file filenames have spaces in them: the feed correctly substitutes the code %20 for each space, so it's not a problem, but it's not good practice as spaces aren't allowed in a URL.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

"Cant Parse Feed"

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.