I read a thread about this issue earlier today that dates back to January in which an Adobe employee said that this issue has been fixed, but unfortunately I've been experiencing it right now. I have multiple articles that include videos and another article with many large photos. When I try navigating from one article to the other the Content Viewer crashes and goes back to the home screen. According to the thread this is known as memory issue and I followed the suggestions to reinstall the Viewer and restart the iPad but it didn't help. Right now the only way to use the app is to navigate to the Cover and continue from there which is defeating the point of having a navigation all throughout the app. I can't just take out the videos or the photos to reduce the file size. Any advice? Thanks!
Sometimes the Adobe Viewer, or a custom Viewer, appears to crash. However, the iOS is in fact shutting it down because of a low memory state. You can confirm whether you have this issue by syncing an affected iPad to a Mac. Then retrieve the logs to see if there are LowMemory-[time stamp].log files. Here is where such log files, as well as crash log files, is found:
Users/[user name]/Library/Logs/CrashReporter/MobileDevice/[device name]
Look for a LowMemory log file with a time stamp that corresponds to the application's exit. Open it in a text editor and look for a line like the following:
viewer <42d0b24207f7d625b2fefef7549afce3> 33490 (jettisoned) (active)
The numbers can vary. However, if the line indicates that the "viewer" process was "jettisoned" while "active," the OS closed the process because of a low memory state. The most likely reason for this is that your viewer is reading into memory images that are larger than 1024 x 1024. Apple recommends against applications loading any image larger than this size as it contributes to a low memory state on the device. It can result in what appear to be application crashes. Review your folio source files and ensure that no images of greater size are used. If they are, simply resample them, and republish your content.
The low memory state can also be the result of having too many applications running at once. Shut down applications you are not actively using to free up more memory.
How to free up memory on your iPad
1. From the home screen, double-click the Home button to display recently used applications.
2. Tap and hold one of the applications until a red minus appears above it.
3. Tap the red minus for all apps that are not currently needed.
4. Tap anywhere above the list of recently used apps, to return to the home screen.
Hi - I and others have been having the same problem with Audio - see other post http://forums.adobe.com/message/4587457#4587457
Are you using an iPad 1, 2 or 3?
I got the same response from tech support and the file location mentioned did in fact reveal low memory errors and crashes due to both my custom app or adobe convtent viewer running on the original iPad. The apps we developed last winter were running perfectly until we updated to the newer viewers in spring. The very helpful staff person tested my app and it worked fine on his later iPad model. He looked at my InDesign files, suggested some changes which I did all last night, and I took all the steps above, however the apps with audio still crash. (We have identical apps without audio and they do not crash)
It would appear there are issues with the newer viewers running on older iPads. Either they are just using to much memory that is needed by media, or memory is not being managed correctly. The media/audio files I am running on each page of our application are only 300k-400k mp3 audio narration.
I ask that the Adobe Staff look in to this matter as soon as possible. There are to many iPad 1's out there to write them off, particularly at schools where we market our publications.
Thanks for your input, I’m using iPad 3 and downloaded the latest version of Content Viewer. I’m also using the proper resolution so I think at this point I just need to reduce file size as much as possible. My problem is that I can’t reference the videos as Adobe suggests, I need to embed them so you don’t need internet connection to view them. At this point I’ve accepted the fact that nothing is perfect and there will always be bugs in a software that require a workaround. Just got to make the best of it!
Adobe DPS Technical Support called ME about this, made it a priority one case and sent it to engineering with my sample files. I almost passed out from shock!
They said it is a problem in recent versions (20/21) and that it goes away in version 22.