I’ve seen occasional crashes but nothing like that. Try removing it and then download it again.
We have experienced a similar problem (on two iPads) but also with the previous Viewer. For us it is when swiping from article to article sometimes it crashes back to the Content Viewer Home screen. There are no videos on these pages. Are these issues likely to persist after the folio has gone through the Viewer Builder process as a multi issue app?
Crashing of the Adobe Content Viewer (or branded viewer) is caused most of the times by memory starvation.
General items to look at
* large files for covers (resolution > 1024x768)
* large images used in folios / MSO / Scroll Pan - especially in articles next to each other
With kind regards,
Thanks Klaasjan, helpful advice!
We do have many 1024x768 images on a the first page of adjacent articles (its a photography magazine) and in one instance an MSO comprising 10 1024x768 images so I guess we should look again at this. In the previous issue we quite an number of articles starting with videos but this worked fine.
Ive had a lot of crashing as well. Images are at the start of every chapter - size= 1232x242.
Is that big enough to crash the app?
I'm facing the same problem !
What I find strange about this issue though is that I'm working with the same folio files that I was before I upgraded to the latest Content Viewer. I have only made minor text edits and have not added images or video. The previous Content Viewer never crashed for me.
My experience (and that of my colleagues) is repeated crashing at different times.
Download of an updated folio complete? Crash.
Open said folio after restarting app? Crash.
Flick too quickly between pages? Crash.
Im trying to eliminate some variables. I think I'll start with a completely vanilla folio and see what happens...
Try removing the viewer from both the iPad and iTunes. Then sync, and download the viewer again. You might also want to restart your iPad to clear the memory cache. Then try again. Let us know if you still experience crashing.
Thanks Bob, we'll give that a try.
Though I do have to ask - is this a common behavior of the Viewer? Are there any specific actions that I can take to avoid this?
There are two possible issues here. The first issue is that an app's memory can get messed up on the device. That can happen with any app. My guess is that that's causing the crash when you flick too quickly between pages. That sounds like a memory glitch and a reinstall/restart would fix.
The second issue is something that I've run into and the team is looking at. Certain articles in a folio are causing the viewer app to crash when the folio is updated. When you agree to update the folio and tap the View button, the viewer crashes. The workaround is to archive the folio and download it from scratch. It happens only with some folios, and we haven't pinned down the cause of this.
Glad to know this is on the radar. Thanks for the 'Archive first' workaround!
Hi Klaasjan, this is really helpful information, since we have actually the problem that the reader is crashing a lot. Not really surprising since we use a MSO (57 states) in a scrollable area, exactly what you wrote to avoid.
But one question remains, which effects our testing. You said that the articles shouldn't be arranged next to each other, does that mean that the viewer is loading the previous and next article into the memory to speed up the loading time when the user jumps to the next article? Because that would effect our testing, since we have all different versions to test the crashing in one dedicated folio in a row, so we would need to insert a dummy page between all variations, or to you have more specific info on that?
I've been experiencing a similar problem. I have a layout with a bunch of 1024x768 images and movies that worked perfectly. All of a sudden the client reported the Viewer crashing on horizontal view. After a day of experimenting, I narrowed it down to a list of possible causes. As long as all MSO and movies are not connected to any buttons the folio loads alright (albeit, it's not functional). The moment I add the buttons to change the MSOs, the folio crashes. The movies and MSOs alone work all right.
Any clues? Thanks in advance!
I've done everything you mentioned... delete both apps and reinstalled, restarted iPad, and still crashing.
This time I only have 1 article published and it still crashes the app. It has only one slideshow in it and it's definitely not a big file.
The most I could get it to work is vertical, when turned horizontal, it still crashes the app.
Yes, this folio blows up the viewer on my iPad. It's not the viewer. There is a problem with something in the folio.
Yea... I suspect it's the slideshows with buttons. It also happens when I put a swipe slideshow in.
You can view the folio vertically, but not horizontally.
How do I find out what went wrong?
I've been doing the same thing the past 20 issues and it was fine, till now.
Can I send you the indesign files for you to help investigate?
make sure your MSOs and buttons dont have same name
Is it logical to hope this is only a problem when using the Content Viewer, and that once the folio is published as an app the memory issues will no longer be a problem? Or is this instability going to carry through? (Any way to test that?)