A quick and dirty way around that is to use some other generic utility to access the ePub (such as DeskConnect or Documents by Readdle) and then "Open in iBooks", which cross-loads the content to the iBooks library on the device.
I may not agree with this , but at least its just a policy implementation (which stands a chance of overturn if you flag it). My serious issue is that my iOS devices (particularly my iPad) are serious work devices on which I load ~600 documents (both PDFs and ePub) necessary for my job, reference materials, reports, courses, etc. Since migrating my library to iCloud I've effectively lost use of my iBooks app unless I cripple iCloud access and hence 550+ entries access.
A cursory investigation (via logs and crash reports) shows that an internal service (thumbnail generation for the iCloud located book covers) is the culprit, crashing and taking out the calling iBooks process, why is Apple still not resolving this widespread issue?
I may not agree with this , but at least its just a policy implementation (which stands a chance of overturn if you flag it). My serious issue is that my iOS devices (particularly my iPad) are serious work devices on which I load ~600 documents (both PDFs and ePub) necessary for my job, reference materials, reports, courses, etc. Since migrating my library to iCloud I've effectively lost use of my iBooks app unless I cripple iCloud access and hence 550+ entries access.
A cursory investigation (via logs and crash reports) shows that an internal service (thumbnail generation for the iCloud located book covers) is the culprit, crashing and taking out the calling iBooks process, why is Apple still not resolving this widespread issue?