File rejected by Apple

awp · 07-31-2010, 06:12 PM

One of our users submitted an EPUB book for inclusion into the iBookstore. The file passed the epubcheck validation test. But this file was rejected by Apple with the following error message:

Apple ERROR ITMS-4000: Line 89 column 63: bad character content for element at XPath/package/book/assets/asset[2]/data_file/file_name.

I googled for this error. The only site page where it is mentioned is a bug report page of Calibre:
http://bugs.calibre-ebook.com/ticket/5773

I do not have the "guilty" EPUB file (there are privacy concerns I guess).

Can anyone say what this error could mean?

Thanks.

Jellby · 08-01-2010, 04:33 AM

Could some file(s) inside the ePUB have a name with non-ascii characters?

charleski · 08-01-2010, 07:58 AM

It's very difficult to say without seeing the actual epub. Since it's coming from a Word file there shouldn't be any encoding issues in the file names, since they're all generated by AWP. Maybe ask if they can extract just the .opf file and send it to you.

GeoffC · 08-01-2010, 08:40 AM

From experience passing epubcheck is no guarantee of anything .... Pity the error message was not more expressive .... !

awp · 08-01-2010, 06:14 PM

Quote:

Originally Posted by charleski

Since it's coming from a Word file there shouldn't be any encoding issues in the file names, since they're all generated by AWP.

Exactly. The EPUB file contains multiple HTML files. Their names are 1.html, 2.html, and so on.

Quote:

Originally Posted by charleski

It's very difficult to say without seeing the actual epub. Since it's coming from a Word file there shouldn't be any encoding issues in the file names, since they're all generated by AWP.

The user agreed to send me the EPUB file. It is copyrighted. I will have to remove it from my computer after examining it. So regrettably I cannot post it to the forum.

It contains 31 HTMLs (chapters). All use a very basic formatting. I have checked all the files from the EPUB package. There is nothing suspicious in any of them at "line 89 column 63". Only plain English text.

Quote:

Originally Posted by charleski

Maybe ask if they can extract just the .opf file and send it to you.

I suppose that posting the .opf file is not a problem since it is rather a "technical file" (please see attachment). But it is unlikely that the .opf file could be the problem.

charleski · 08-01-2010, 07:51 PM

It looks perfectly fine, they haven't added anything else to the package after it was generated, which is why I suggested looking at the opf.

Right now I think the primary suspicion must be some bug in Apple's system.

GeoffC · 08-02-2010, 11:40 AM

and there is no line "89" in the .opf

kovidgoyal · 08-02-2010, 11:42 AM

Your problem is that the NCX specification does not allow filenames to start with numbers. Valid identifiers have to start with a letter and use only letters, numbers and underscores.

As far as I know Apple is the only organization simple minded enough to impose this restriction.

charleski · 08-02-2010, 01:40 PM

Quote:

Originally Posted by kovidgoyal

Your problem is that the NCX specification does not allow filenames to start with numbers.

Are you sure about that? Section 3.3.1 doesn't mention anything special about the first character of a filename. You might be thinking of ids.

kovidgoyal · 08-02-2010, 03:06 PM

I've had people open tickets about it and changing the filename got the epub accepted by Apple. You're probably right in that the spec doesn't specify that convention for the filename, but I'm fairly certain Apple does.

Of course, as with any closed system, no way to be sure, so I could be wrong, but given that the original error message points to a file_name...

awp · 08-02-2010, 04:35 PM

I have just sent a test version of Atlantis Word Processor to that user. It generates HTML filenames starting with a letter. I will let you know if it worked.

Thanks.

st_albert · 08-02-2010, 07:03 PM

Quote:

Originally Posted by awp

I have just sent a test version of Atlantis Word Processor to that user. It generates HTML filenames starting with a letter. I will let you know if it worked.

Thanks.

Hmm, I am looking forward to the answer to this. We have submitted several epubs to Apple that were initially created from .rtf via Atlantis, and -- I just checked -- they have filenames starting with numbers (1.html, etc.). So far they have been accepted by Apple, and AFIK are offered for sale on iBooks.

eping · 08-02-2010, 10:59 PM

Quote:

Originally Posted by kovidgoyal

As far as I know Apple is the only organization simple minded enough to impose this restriction.

I agree. I found Apple is also silly enough to report error if there's additional characters after </html>

awp · 08-03-2010, 06:21 PM

I have a reply from the user (she is a production manager at a publishing company). Filenames starting with numbers are not a problem, even to Apple (to iPad and iTunes Producer). She said that they have 102 titles currently active at Apple and 136 that have been submitted and are awaiting acceptance, and all were created with Atlantis Word Processor. They always submit Atlantis EPUBs "as is", without "tweaking" them. That "faulty" eBook is the only file that keeps rejecting. By the way, that eBook contains adult material. Maybe this is why iTunes Producer does not want it to get through.

She also said that she will start the file over from scratch and rebuild it to see if that will fix it.

JSWolf · 08-07-2010, 02:32 AM

Given that it's Apple, chances are the book is fine and that it's the content that gets it rejected.

07-31-2010, 06:12 PM	#1
awp Addict Posts: 228 Karma: 16000 Join Date: Jun 2009 Device: Sony PRS-T1	File rejected by Apple One of our users submitted an EPUB book for inclusion into the iBookstore. The file passed the epubcheck validation test. But this file was rejected by Apple with the following error message: Apple ERROR ITMS-4000: Line 89 column 63: bad character content for element at XPath/package/book/assets/asset[2]/data_file/file_name. I googled for this error. The only site page where it is mentioned is a bug report page of Calibre: http://bugs.calibre-ebook.com/ticket/5773 I do not have the "guilty" EPUB file (there are privacy concerns I guess). Can anyone say what this error could mean? Thanks.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
apple rejected/then rates a dictionary as 17+ do to bad words	ahammer	News	23	08-07-2009 11:51 AM
WIRED: E-Reader iPhone App Rejected Because Users Can Download Kama Sutra	Kris777	News	26	05-28-2009 08:23 AM

08-01-2010, 04:33 AM	#2
Jellby frumious Bandersnatch Posts: 7,516 Karma: 18512745 Join Date: Jan 2008 Location: Spaniard in Sweden Device: Cybook Orizon, Kobo Aura	Could some file(s) inside the ePUB have a name with non-ascii characters?

08-01-2010, 07:58 AM	#3
charleski Wizard Posts: 1,196 Karma: 1281258 Join Date: Sep 2009 Device: PRS-505	It's very difficult to say without seeing the actual epub. Since it's coming from a Word file there shouldn't be any encoding issues in the file names, since they're all generated by AWP. Maybe ask if they can extract just the .opf file and send it to you.

08-01-2010, 08:40 AM	#4
GeoffC Chocolate Grasshopper ... Posts: 27,600 Karma: 20821184 Join Date: Mar 2008 Location: Scotland Device: Muse HD , Cybook Gen3 , Pocketbook 302 (Black) , Nexus 10: wife has PW	From experience passing epubcheck is no guarantee of anything .... Pity the error message was not more expressive .... !

08-01-2010, 07:51 PM	#6
charleski Wizard Posts: 1,196 Karma: 1281258 Join Date: Sep 2009 Device: PRS-505	It looks perfectly fine, they haven't added anything else to the package after it was generated, which is why I suggested looking at the opf. Right now I think the primary suspicion must be some bug in Apple's system.

08-02-2010, 11:40 AM	#7
GeoffC Chocolate Grasshopper ... Posts: 27,600 Karma: 20821184 Join Date: Mar 2008 Location: Scotland Device: Muse HD , Cybook Gen3 , Pocketbook 302 (Black) , Nexus 10: wife has PW	and there is no line "89" in the .opf

08-02-2010, 11:42 AM	#8
kovidgoyal creator of calibre Posts: 43,850 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	Your problem is that the NCX specification does not allow filenames to start with numbers. Valid identifiers have to start with a letter and use only letters, numbers and underscores. As far as I know Apple is the only organization simple minded enough to impose this restriction.

08-02-2010, 03:06 PM	#10
kovidgoyal creator of calibre Posts: 43,850 Karma: 22666666 Join Date: Oct 2006 Location: Mumbai, India Device: Various	I've had people open tickets about it and changing the filename got the epub accepted by Apple. You're probably right in that the spec doesn't specify that convention for the filename, but I'm fairly certain Apple does. Of course, as with any closed system, no way to be sure, so I could be wrong, but given that the original error message points to a file_name...

08-02-2010, 04:35 PM	#11
awp Addict Posts: 228 Karma: 16000 Join Date: Jun 2009 Device: Sony PRS-T1	I have just sent a test version of Atlantis Word Processor to that user. It generates HTML filenames starting with a letter. I will let you know if it worked. Thanks.

08-03-2010, 06:21 PM	#14
awp Addict Posts: 228 Karma: 16000 Join Date: Jun 2009 Device: Sony PRS-T1	I have a reply from the user (she is a production manager at a publishing company). Filenames starting with numbers are not a problem, even to Apple (to iPad and iTunes Producer). She said that they have 102 titles currently active at Apple and 136 that have been submitted and are awaiting acceptance, and all were created with Atlantis Word Processor. They always submit Atlantis EPUBs "as is", without "tweaking" them. That "faulty" eBook is the only file that keeps rejecting. By the way, that eBook contains adult material. Maybe this is why iTunes Producer does not want it to get through. She also said that she will start the file over from scratch and rebuild it to see if that will fix it.

08-07-2010, 02:32 AM	#15
JSWolf Resident Curmudgeon Posts: 73,931 Karma: 128903250 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Given that it's Apple, chances are the book is fine and that it's the content that gets it rejected.