View Single Post
Old 08-20-2013, 08:34 AM   #9
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,680
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Hitch View Post
Well....this is in passing, at a glance, but I suspect it might be the tmp file that got included in the build. Now...I could be completely blowing smoke, but I don't think that .tmp is a valid media file type, and I think that could be corrupting the build.
Admittedly, I've never built a Kindlebook with a "media" file, so I don't know what that looks like in a successful build. Perhaps the tmp file (and path) is a normal part of the build process? It does seem odd that THAT file is the only one found at a different location than the rest of the resources.

Quote:
ETA: We build out of dropboxes all the time, without trouble, but something in your directory structure seems odd to me, so you should look into that as well. FWIW, as stated.

Hitch
The Dropbox thing was just a WAG on my part.
DiapDealer is offline   Reply With Quote