Thank you for the reply Himanshu.  Evidently the problem is much worse than I thought because previously created apps don't even open anymore!

None of the apps we have published to the Android app store are getting past the splash screen.  The library flashes briefly on some of them before the app crashes.  The error message it gives is "Unfortunately, ____ has stopped."  This is a big problem!!  Will updating the apps to v22 solve this issue?  When will Adobe have this major problem fixed?

I'm flashing back to June of last year when reliability of basic functionality (like apps opening and folios being downloadable/viewable) was still unpredictable.  You Adobe guys and gals have got to figure out how to make the DPS system dependable.  I understand this is an operating system conflict, but surely you knew this update was coming and could test how well your software would hold up to the changes.  This isn't a barely used minor feature that isn't working, this is something that makes users uninstall the app and lessens their opinion of the company that released it.  Please make this your top priority and get it fixed today.  We and our customers are paying for a much higher level of service than this.

Any update on this issue Neil?  We're trying to update a folio/app today but I don't want to give people an update alert for something that will still crash.  Thanks.

Andrew

Well, now I'm not able to see updates on our Xoom even after killing the Adobe Content Viewer app and restarting it.  What a horrible storm of lost basic functionalities (for both the iOS and Android viewers) that is really making our life painful and hurting the business of one of our biggest customers.

I honestly don't see how we can possibly recommend Adobe's system in the future since we're having to apologize yet again in the present.  We're supposed to be helping people solve problems not create new ones.  We cannot roll out the updated folios for our customer's product launch today.  They are not happy and I am sick to my stomach...

The published Adobe Content Viewer is displaying the library without crashing.  The problem is that when I update a folio that was already downloaded the app is not giving me the "Update Available" message under that folio.  I started this discussion because after updating my device and the Adobe Content Viewer it wasn't giving the "Update Available" message except when I killed the Adobe Content Viewer and then restarted it.  It seemed like it was only doing a 2 second cursory check before the app restart.  After restarting it would do a longer "Updating Library..." check and find the updated content.  Now it isn't even doing that, I've updated the same folio and now I'm not seeing the "Update Available" message under that folio even after restarting the Adobe Content Viewer.  It seems like it may be related to the problem with the age of folios and the iPad Adobe Content Viewer where tapping on the "View" button doesn't do anything.  My concern is that I will have to tell my customers (and all the people in their salesforce) to archive and re-download entire large folio files (without any prompting from the Adobe Content Viewer) when I've only changed a few articles.  I'm hoping that makes sense, if not I will gladly try to clarify.  Thanks Neil.

I confirmed that I am trying to modify the correct folio/rendition.  This folio is one that was originally created in May/June of last year and has been updated every month or so since.  I wasn't able to view/update the iPad rendition of the same content (originally created in March/April of this year) until I archived it and redownloaded the entire folio.  My best guess is that the creation date is what's causing things to be a bit wacky, but it could also be the date it was downloaded to the device.  I think I'll just wait until the fix rolls out and hope that resolves it.  Thanks for trying to help address the issue.

Andrew

Neil,

I just rebuilt one of our apps as a v22 app and submitted it to Google Play.  It's now available, I updated the app on our Xoom, it showed the splashscreen and then a gray outline of a folio in the library view, and then it crashed with the same message as before.  It doesn't appear that Bob has updated DPS Tips yet, but my guess is that the same thing will happen to his app.  Any ideas?

I've got over 20GB of free space, I have very few apps on our Xoom, and the device settings are pretty much stock.  Is it possible the fix hasn't rippled through the system yet?  Are we supposed to use a new version of the Viewer Builder?

Andrew

The newest Viewer Builder .dmg I found was created on August 22nd.  This is the one I'm using.  Is there a newer one available?

At the top of Viewer Builder it says 2.2.0.29.55824.