Yesterday I updated our Xoom to Android 4.1.1 and updated the Adobe Content Viewer to v22. Both we and a client have had issues with not seeing the "Update Available" message for folios that are been updated. The "Updating Library..." message flashes briefly at the top of the viewer in library mode, however nothing changes. It's only after killing the app and restarting that it takes its time while checking the library for updates and finds them. Has anyone else had this issue? The iPad rendition of the same folio has been showing update messages in the usual, almost instantaneous, way.
Has anyone else had difficulty with updating folios in the Android v22 Adobe Content Viewer? In the past couple of versions I've noticed some strangeness with the Sign In/ Sign Out part of the library where it seems like the text tells you you're signed in, but sometimes you have to sign out and sign back in to get updates. Sometimes you could go back to the home screen and then go back into the app and it would trigger a check for updates as well, however that trick doesn't seem to be working anymore.
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.
I updated Bob's DPS Tips app (v22) today and it does the same thing. After showing the splash screen for a few seconds the app crashes and gives the error message "Unfortunately, DPS Tips has stopped."
I called Adobe Gold support earlier and the support rep said that this problem was fixed with the v22 update and that all I need to do is update my apps to v22, however if DPS Tips is still crashing then I'm sure mine will too. I don't want to tell people there's an update and then have it still crash. Is anyone else having problems loading the DPS Tips app on an Android device? Is it working on your Android devices Bob?
The Adobe Content Viewer doesn't crash after the splash screen, it just seems to have the updating library problem.
My app works fine on Froyo and Honeycomb devices, but I just borrowed a Jelly Bean (4.1) device and experienced the same crash. I reported this issue to the Android tester. Let's hope for a hot fix soon.
We are experiencing this same problem - we had a Motorola XOOM w/ Android 4.0 that could run the v22 Content Viewer fine, but then after upgrade to Android 4.1.1, v22 Content Viewer crashes on start.
Viewer Builder-built apps exhibit the same issue:
v22 apps crash on startup
v21 apps DO NOT crash on startup
(However, the v21 apps are exhibiting strange behaviour with full-screen video, but that's a different thread altogether).
We have issue with ALL Android viewers on Ainol Novo7 AuroraII device with 4.0.4 (stock Adobe Viewer from Google Play, different custom viewers from Google Play, back to v18, new customer viewer v22). So far don't know if this is device-related, or software-related. Any idea? don't have any other device with 4.0.4 .
I am having this issue on the iPad as well. I just updated to v22 and none of my previously created folios will open.
I am sending out messages to clients this evening to hold off updating their Content Viewer apps until I find some resolution.
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...
"I second your frustration. How something like this could make it out the door is a mystery."
From Bob, just above:
"My app works fine on Froyo and Honeycomb devices, but I just borrowed a Jelly Bean (4.1) device and experienced the same crash."
That's how it gets out the door.
Neil, thank you for the status update.
When I wrote the first post of this discussion I was able to see updated folios in the Android viewer by "killing" the Adobe Content Viewer and restarting it. Now the same folio that was letting me see updates after restarting the app isn't showing the "Update Available" message no matter what I do. Was there a change on Adobe's side that would cause this folio to no longer receive updates in the Adobe Content Viewer? My concern is that even after the fix I'm still going to have to tell my customers to archive and redownload the entire folio. Will the "Update Available" message start working again after the fix, ideally without having to restart the app?
Just to clarify: we know there is a crashing problem with both custom apps and the Adobe Content Viewer on Jellybean when produced via Viewer Builder. We'll be releasing a fix for that, and it will require a rebuild of your application/viewer and then re-distribution.
We are unaware of crashes in the published Adobe Content Viewer available via Google Play. I just sat with an engineer and we succesfully installed that viewer, logged in, viewed a library, and downloaded a folio.
If you are seeing something different please let me know.
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 grabbed a colleague's Jellybean device and gave this a try with the released Adobe Content Viewer and had no issues updating a folio and getting the update library message.
Are you positive you are updating the correct rendition for your folios?
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.
We have pushed out the hotfix to Viewer Builder that resolves the Jellybean crash. You should be able to re-build your viewer and successfully see the library and updated issues now.
this is very important for me: will be with new build included new Adobe AIR, released on 21th of August? And btw how i can say which version of AIR s included with particular build of viewer? I've just today found that this latest version of Adobe AIR solves stability issue (or better to say crasher), which occured on some strange Android devices with 4.0.4 with ANY version of Viewer (i've tested 18, 19, 22, maybe even older). This crasher was reported by users of our Android apps - application never started, just black screen and back to launcher. Your support told me, that i should contant device manufacturer, but seems that it was something what Adobe could fix. Case #0183544776.
So i need to have v22 with newest Air...
Thanks for reply!
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?
i've just downloaded new viewer builder and i've created new builder, which includes AIR runtime. Unfortunately, it crashes in same way like with old viewer with old Adobe AIR. I need to have new AIR included with viewer, because i need that is solves this crasher. Is there any way how to push this issue?
we've just tested it on Asus Transformer with 4.1.1 and it's NOT FIXED. App starts, shows splashscreen and there stuck. We will try to test on another Android 4.1 devices, but this is NOT GOOD.
Bob updates the list of fixes at http://helpx.adobe.com/digital-publishing-suite/release-note/dps-bug-f ix-release-notes.html shortly after each release.
Martin - You might want to create a new viewer from scratch in Viewer Builder. That worked for me when I experienced the splash image freeze on my app. Unfortunately, it appears that the hot fixes rolled out yesterday did not resolve all the bugs with Android viewers.
The Viewer Builder update solved it for me. I just updated one of the problem apps via Google Play and it is no longer crashing after the splash screen. I didn't have to rebuild it from scratch thankfully, I just clicked on edit and made a v22 app. Thank you for fixing this, talk about a heartstopper when it was first discovered...
I downloaded it from digitalpublishing.acrobat.com. There's a link in the lower left hand corner for Viewer Builder that should download the Viewer-Builder-184.108.40.206.57686-RC.dmg file.