Android Viewer crashing

Hi,
the Android Content Viewer in Version 2.9.0.0.63198 is crashing as soon as you try to open a publication. After the first crash, it crashes again directly after starting the app. You have to make a reinstall, even if it won't help much as it crashes again trying to open a publication.
I can confirm this on Nexus 7 with Android 4.2 and an Acer A510 with Android 4.1.2.
Look also at the english comments on Google Play. There are much more users with different tablet types, where the content viewer has the same problem.
Thanks,
Yves

Reading an earlier article while trying to find a solution, it seems v25 only addressed some bug fixes on ios devices. I have a galaxy tab 10.1 and a Galaxy Nexus both running versions of jellybean that both experience the same issue of force closing when you go to open a folio. Reinstall is the only way out. As for the issue, i've been waiting for them to resolve it for months now. Its very frustrating. I tried just a plain text folio produced to the latest version 25, with png selected instead of pdf or automatic (another article stated that android doesnt support pdf, whether thats true or not i cant say) on both devices and still es no bueno.

Similar Messages

Thumbnail view crashing FCP -- Kona3 the problem?

For larger projects, running bins in thumbnail view crashes FCP.
Most of the time, I'm editing 6 to 8 min. stories for a news magazine format show. We shoot on Sony XDCAM, so usually 2 or 3 disks per project (roughly 44 mins of HD viddy per disk, with anywhere from 20 to 120 individual clips on the disk).
However, for our documentaries (either 26 mins or 56mins) we shoot between 30 to 45 disks full of content. When importing the disks into FCP7, we use a bin per disc, translating into an average of 80 clips per bin. Whenever a project is this big, I can only open 3 or so bins in thumbnail view. After that, the system crashes. Even if I only keep one bin open at a time, by that fourth bin, the system crashes.
We are using a KONA3 card configuration.
Anyone else seen this?

PROBLEM IDENTIFIED (NOT SOLVED):
I've had this problem with thumbnail images crashing FCP after opening bins for over a year now and when going back using footage from old projects it happens more frequently. I can open 2-4 bins before it will crash FCP completely.
TROUBLESHOOTING IN THE PAST:
- Dumped Prefs
- Re-installed FCP
- Formatted & Re-installed EVERYTHING (OSX included)
- Increased thumbnail cache size
- Created new projects & bins, etc.
CONCLUSION:
None of the above troubleshooting strategies worked. Increasing the thumbnail cache size may appear to work a little but problem persists with little improvement.
HOW I IDENTIFIED THE PROBLEM:
Only recently have I been working with other formats aside from XDCAM. I've recently incorporated more ProRes files into my most recent project of T2i footage from the Canon DSLR camera. If I open a bin and display thumbnails of the ProRes video clips everything works without a problem. Loading thumbnail bins with the raw .mp4 files also works fine. Only loading XDCAM files will cause FCP to crash. The problem has nothing to do with the Kona card. If you read the posts carefully here and elsewhere you will see the common denominator is the XDCAM encoded video files being displayed as thumbnail icons.
I am using XDCAM EX files at 1080p 30fps. To further isolate this problem as something having to do with the XDCAM files, another user posted on another thread:
*"I am having similar issues with two separate projects. The only commonality between them is XDCam.*
*To possibly isolate it I reinstalled FCP on one system, and installed latest Blackmagic driver on the the same. Both systems are up to date visa vi OS, FCP, and QT.*
*Both still crash with the same regularity as described here."*
Apple, this problem has persisted for more than two years and is a major problem. Just search the forums including this one. Any further upgrades of Final Cut Studio or OS X are worthless until this problem is fixed. A brand new body and interior won't fix a car with a broken engine. Please help!! Please solve this issue with the XDCAM footage in FCP!
If anyone has any solutions or work arounds please notify me. I need it!
[email protected]
/\/\ichael
Message was edited by: MichaelRev1412
Message was edited by: MichaelRev1412

Gnome 3 log file viewer crashes on file open

Hi everyone,
I'm experiencing an annoying issue in which the system log file viewer crashes when I load certain log files. For example, if I go to file>open>crond.log, the viewer will crash. The same occurs with errors.log, kernel.log, pm-suspend.log, and others on a somewhat inconsistent basis. When I relaunch the program, crond.log (or any of the other files in question) is open and can be viewed without a problem.
After I initially set up the system, I ran into permissions problems when trying to open a number of log files. I added my user to the "log" group and then had to manually chmod the /var/log/ directory to resolve those issues. The crash seems to occur on the log files that were originally restricted. It does appear that some of the log files are still in the "root" group as opposed to the "log" group.
I'm running Arch 64-bit with Gnome 3.0 (native install, not upgrade). Has anyone else experienced this problem? I'm somewhat of a novice with permissions so perhaps that's to blame. Still, it doesn't seem like the viewer should crash but then be able to open the file.
Output of ls -l /var/log:
total 34244
-rw-r----- 1 root log 12691 May 15 20:44 auth.log
-rw-r----- 1 root log 15189 May 15 10:31 auth.log.1
-rw-r----- 1 root log 44949 May 8 09:01 auth.log.2
-rw-r----- 1 root log 70857 May 6 18:01 auth.log.3
-rw-r--r-- 1 root root 11577 May 15 20:44 boot
-rw------- 1 root root 0 Apr 22 21:09 btmp
drwxr-x--- 2 root root 4096 May 15 14:50 ConsoleKit
-rw-r----- 1 root log 362 May 15 15:01 crond.log
-rw-r----- 1 root log 1796 May 15 14:50 crond.log.1
-rw-r----- 1 root log 1440 May 8 09:32 crond.log.2
-rw-r----- 1 root log 4441 May 6 18:10 crond.log.3
drwxr-xr-x 2 root root 4096 May 15 14:50 cups
-rw-r----- 1 root log 44287 May 15 20:44 daemon.log
-rw-r----- 1 root log 96821 May 15 14:41 daemon.log.1
-rw-r----- 1 root log 128416 May 8 08:27 daemon.log.2
-rw-r----- 1 root log 445951 May 6 17:14 daemon.log.3
-rw-r--r-- 1 root root 48494 May 15 20:44 dmesg.log
-rw-r----- 1 root log 6334 May 15 20:57 errors.log
-rw-r----- 1 root log 10912 May 15 10:30 errors.log.1
-rw-r----- 1 root log 4098198 May 7 18:36 errors.log.2
-rw-r----- 1 root log 28279 May 6 17:23 errors.log.3
-rw-r----- 1 root log 292780 May 15 20:57 everything.log
-rw-r----- 1 root log 352142 May 15 14:50 everything.log.1
-rw-r----- 1 root log 8504549 May 8 09:32 everything.log.2
-rw-r----- 1 root log 2329358 May 6 18:10 everything.log.3
-rw------- 1 root root 32064 May 8 08:28 faillog
drwxrwx--T 2 root gdm 4096 May 15 20:44 gdm
-rw-r----- 1 root log 237511 May 15 20:45 kernel.log
-rw-r----- 1 root log 244356 May 15 14:41 kernel.log.1
-rw-r----- 1 root log 8366407 May 8 08:09 kernel.log.2
-rw-r----- 1 root log 1781951 May 6 17:23 kernel.log.3
-rw-r--r-- 1 root root 292584 May 8 08:28 lastlog
-rw-r----- 1 root log 195079 May 15 20:57 messages.log
-rw-r----- 1 root log 247865 May 15 14:41 messages.log.1
-rw-r----- 1 root log 4231866 May 8 09:29 messages.log.2
-rw-r----- 1 root log 1620382 May 6 17:54 messages.log.3
-rw-r--r-- 1 root root 12448 May 15 20:45 ntp.log
drwxr-x--- 2 root root 4096 Apr 8 06:08 old
-rw-r--r-- 1 root root 0 May 13 23:47 PackageKit
-rw-r--r-- 1 root root 113304 May 15 17:09 pacman.log
-rw-r--r-- 1 root root 203599 May 15 20:44 pm-powersave.log
-rw-r--r-- 1 root root 289619 May 15 20:36 pm-suspend.log
-rw-r----- 1 root log 701 May 15 20:44 syslog.log
-rw-r----- 1 root log 619 May 15 10:00 syslog.log.1
-rw-r----- 1 root log 1387 May 7 18:18 syslog.log.2
-rw-r----- 1 root log 5309 May 6 17:14 syslog.log.3
-rw-r----- 1 root log 9697 May 15 20:57 user.log
-rw-r----- 1 root log 7773 May 15 10:31 user.log.1
-rw-r----- 1 root log 6344 May 8 08:27 user.log.2
-rw-r----- 1 root log 90189 May 6 17:14 user.log.3
-rw-r----- 1 root log 0 May 15 14:50 uucp.log
-rw-r----- 1 root log 0 May 8 09:32 uucp.log.1
-rw-r----- 1 root log 0 May 6 18:10 uucp.log.2
-rw-r----- 1 root log 0 Apr 25 01:11 uucp.log.3
-rw-rw-r-- 1 root root 167424 May 15 20:57 wtmp
-rw-r--r-- 1 root root 348288 May 6 17:14 wtmp.1
-rw-r--r-- 1 root root 38995 May 15 20:44 Xorg.0.log
-rw-r--r-- 1 root root 40721 May 15 20:36 Xorg.0.log.old

w201 wrote:Dconf editor has completly vanished from my activities overview, well at least the GUI frontend, pacman shows that it's installed. Another function that seems to be gone in 3.16 is the ability to search for files from the activities overview!! I really hope that gets fixed soon :-(
reinstalling dconf-editor fixed that issue for me

Content Viewer Crashes When Viewing Web Content

Hi,
I'm having issues with the folio Content Viewer crashing before web pages fully load my hyperlinks. I need to proof the folio with the client before we can publish, so I need everything to be working and know that the final app will not have the same issue.
I've set up buttons that link to coordinates on Google Maps. When a button link is clicked, the web viewer begins to load then immediately disappears (sliding to the bottom of the screen before the web content finishes loading) or crashes the Content Viewer completely.
I searched the forums and did not really find any solutions, other than when using a lot of images, they need to be sized/sampled down to use less memory. My folio does have a few articles that use quite a few images, so I've sampled everything down to 72dpi and noticed a slight increase in loading speed when loading each article. At first I thought this fixed the issue as the maps were loading for me, but after switching articles, it's crashing again.
If anyone has come across this and has a solution, please help me out!
Thanks,
S

Found a solution.
https://blogs.adobe.com/indesigndocs/2013/06/memory.html
Hopefully this helps someone else.
Cheers!
S

Viewer crashes if any data exists in field

Hi there,
Wonder if you would be able to help me out. We are doing a very simple query onto the database using a Data Template (see below).
We've set the 3 parameters and Auto Generated a Layout.
When viewing this report (clicking View) all is fine when (any of the fields) COMPANY_BACKGROUND or FOCUS are empty. As soon as we enter any value - doesn't matter how long, or which characters - we get the error ("The report cannot be rendered because of an error, please contact the administrator.") when viewing the template in any, but Data output format. When outputting to Data, we do see the data in the database represented in the xml.
The columns have the following specs:
- S_ORG_EXT.DIRECTIONS is a long of type Data (Public).
- S_ORG_EXT.FOCUS is a Varchar 700 of type Extension.
Can anyone help us finding out why filling any of the fields with data makes the viewer crash?
Thanks in advance for the support.
h6.
<dataTemplate name="Company_Overview_Report" Version="0.1">
     <parameters>
          <parameter name="c_rowid" dataType="character" defaultValue="1-GFQ"/>
          <parameter name="c_division" dataType="character" defaultValue="National Accounts"/>
          <parameter name="c_officeType" dataType="character" defaultValue="Home Office"/>
     </parameters>
     <dataQuery>
          <sqlStatement name="Q1_Company_Overview">
               <![CDATA[
SELECT
SOE.ROW_ID AS COMPANY_ID
,SOE.NAME AS COMPANY_NAME
,SOE.DIRECTIONS AS COMPANY_BACKGROUND
,SOE.X_FOCUS AS FOCUS
FROM
SIEBELT.S_ORG_EXT SOE
WHERE
SOE.ROW_ID = :c_rowid
AND SOE.DIVISION = :c_division
AND SOE.X_OFFICE_TYPE_CD = :c_officeType
]]>
          </sqlStatement>
     </dataQuery>
     <dataStructure>
          <group name="G_Company_Overview" source="Q1_Company_Overview">
               <element name="COMPANY_ID" value="COMPANY_ID"/>
               <element name="COMPANY_NAME" value="COMPANY_NAME"/>
               <element name="COMPANY_BACKGROUND" value="COMPANY_BACKGROUND"/>
               <element name="COMPANY_FOCUS" value="FOCUS"/>
          </group>
     </dataStructure>
</dataTemplate>

Hi there,
It seems that our question can be narrowed down to the following one:
Large Varchar
Does the viewer have a max length size for bringing in data from fields/columns > (f.e.) 300 characters?
Thanks if you know the answer to this one!

Content viewer crashes after loading google map

Greetings! I am making progress, finally on my first Edge Animate CC 2014 / InDesign CC 2014 DPS edition.
I have finally gotten to the pplace where I need to display a Google Map for two different locations, each map will be loaded with a different button on click and replace the previous map. It works fine in the browser, but when I upload my folio through InDesign and load it into the Adobe Content Viewer on an iPad (Air) after clicking the MAP button (either one), the map loads and appears to be fine, then after about 10 seconds, the Viewer crashes. I have tried it repeatedly and by clicking both map buttons, the produce the same results.
What should upload for someone to look at, or has anyone else ran into this issue?
Below is the code for the Action(s):
downtownMapButton:
// insert code for mouse click here
var mapFrame = sym.$("mapContainer");
var map ='<iframe width="'+mapFrame.width()+'" height="'+mapFrame.height()+'" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="https://mapsengine.google.com/map/embed?mid=zE2zuZhUFeMU.kVkOwZos-Fiw" ></iframe>';
mapFrame.html(map);
// Show an element
sym.$("mapBox").show();
// Show an element
sym.$("downtownPointerSym").show();
// Show an element
sym.$("mapContainer").show();
sym.$("closeButtonSym").show();
sym.$("prestonPointerSym").hide();

Found a solution.
https://blogs.adobe.com/indesigndocs/2013/06/memory.html
Hopefully this helps someone else.
Cheers!
S

Adobe Content Viewer Crashing

Is anyone else having a problem with the newest version of Adobe Content Viewer crashing constantly? It crashes all the time for me. Sometimes after I download a folio update and go to view the folio, sometimes when I tap to download the upadte for a folio. I try restarting the app, I try restarting my ipad, nothing seems to make it crash less often. I was just wondering if anyone else is experiencing this and if you've found a solution?
Thanks!

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?
Thanks, Norbert

Adobe Viewer Crashes

I have installed the latest version of the adobe viewer. I downloaded a folio - 685MB but when it finishes the Adobe Viewer crashes and the IPAD screen returns to the screen with all the icons of my apps, then I open again the adobe viewer and it shows that I have to download again the Folio. Please help I have to get the approval of my app with my customer and I dont know what to do. Thanks

My folio still does not work. I've isolated the problem to one particular layout. When this article is in landscape layout, it causes the Content Viewer to crash. I have no MSO with the same name, and I've checked all the interactive objects and overlays to see what's causing this problem. It worked perfectly before the update to the new Content Viewer and before I updated the tools. The article also works fine in portrait view, and it has the exact same objects and interactivity. This is extremely frustrating, and I could be looking for hours to find what the problem is. Any help would be greatly appreciated.

Downloading froze and Adobe Content Viewer crashed.

I tried downloading folio data with content viewer on iPad.
(InDesign Plugin: V18, Content Viewer V2.3)
But the downloading froze and the content viewer crashed very often.
I checked the folio data on DPS Dashboard and I think the folio data is OK.
And the status of Acrobut.com is "The service is available. No issues repoeted." on Acrobat.com Health.
What's going on?

Which verison Mac OS are you using? What is the verison of InDesign is being used ? Have you donwloaded all the most recent updates to Folio Producer Tools, Folio Builder, and have the new Viewer Builder since this Monday-Jan 30?
PRODUCT UPDATES
Folio Builder panel for InDesign CS5.5
January 26, 2012
Windows | Macintosh
Folio Builder panel for InDesign CS5.0
January 26, 2012
Windows | Macintosh
Folio Producer tools for InDesign CS5.5
January 17, 2012
Windows | Macintosh
Folio Producer tools for InDesign CS5.0
January 17, 2012
Windows | Macintosh

DPS viewer crashes on subscribe

When I perform an iTunes subscription in iOS 7, the Adobe DPS viewer crashes and fully exits.
Console log of the iPad shows:
Oct 9 21:23:39 Jasons-iPad com.apple.launchd[1] (UIKitApplication:com.example[0xb7a7][4303]) <Warning>:
                (UIKitApplication:com.example[0xb7a7]) Job appears to have crashed: Segmentation fault: 11
Oct 9 21:23:39 Jasons-iPad backboardd[29] <Warning>:
                Application 'UIKitApplication:com.example[0xb7a7]' exited abnormally with signal 11: Segmentation fault: 11
Oct 9 21:23:39 Jasons-iPad SpringBoard[33] <Warning>: -[SBFolderController pushFolder:animated:completion:]
                Folder icon <SBNewsstandIcon: 0x17c5a920; nodeID: "com.apple.newsstand">
                Folder: <SBNewsstandFolder: 0x17c0d640> cannot be opened because it does not exist on the current page.
Oct 9 21:23:39 Jasons-iPad ReportCrash[4306] <Notice>: Saved crashreport to
                /var/mobile/Library/Logs/CrashReporter/viewer_2014-10-09-212339_Jasons-iPad.ips
                using uid: 0 gid: 0, synthetic_euid: 501 egid: 0
Above, my App ID was changed to "com.example" to protected the actual ID.
Nothing much to the code - been in use for over a year:
adobeDPS.initializationComplete.addOnce(function () {
    var transaction = adobeDPS.receiptService.availableSubscriptions[productId].purchase();
    transaction.completedSignal.addOnce(function (transaction) {
        // This does not seem to be reached
    }, this);
}, this);
It displays available subscriptions, prompts for sign in, displays confirmation, and success iOS standard messaging. After the purchase was successfully, the app immediately crashes.
v31 running on iOS 7 - testing iTunes subscription using a sandbox account.
Crash log:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x00000000
Triggered by Thread: 0
Thread 0 Crashed:
0   Foundation                     0x2fe58a3a NSKVOPendingNotificationRelease + 6
1   CoreFoundation                 0x2f4baeb6 __CFArrayReleaseValues + 190
2   CoreFoundation                 0x2f44318a _CFArrayReplaceValues + 290
3   CoreFoundation                 0x2f446b98 CFArrayRemoveValueAtIndex + 100
4   Foundation                     0x2fe58c8a NSKeyValuePopPendingNotificationPerThread + 26
5   Foundation                     0x2fe4728a NSKeyValueDidChange + 366
6   Foundation                     0x2fe338c8 -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] + 84
7   viewer                         0x002d306a 0xb8000 + 2207850
8   CFNetwork                     0x2f18c428 __55-[__NSCFURLSession delegate_task:didCompleteWithError:]_block_invoke + 48
9   Foundation                     0x2fe563c4 -[NSBlockOperation main] + 128
10 Foundation                     0x2fe465a6 -[__NSOperationInternal _start:] + 766
11 Foundation                     0x2feea768 __NSOQSchedule_f + 56
12 libdispatch.dylib             0x3a6a781c _dispatch_client_callout + 20
13 libdispatch.dylib             0x3a6ae49a _dispatch_main_queue_callback_4CF$VARIANT$mp + 274
14 CoreFoundation                 0x2f4dc89c __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 4
15 CoreFoundation                 0x2f4db170 __CFRunLoopRun + 1296
16 CoreFoundation                 0x2f445eba CFRunLoopRunSpecific + 518
17 CoreFoundation                 0x2f445c9e CFRunLoopRunInMode + 102
18 GraphicsServices               0x3437965e GSEventRunModal + 134
19 UIKit                         0x31d92148 UIApplicationMain + 1132
20 viewer                         0x000d09a6 0xb8000 + 100774

If you have an iPad of first generation, it is happening because lack of memory. Try to do PDF stacks instead of PNG/JPEG ones.

Nav to function on Android viewer V.30

We have a problem with the new Android viewer: the call to the navto function from javascript does NOT work.
As you can see in the attachment that you can download here: http://we.tl/ahfkklk8Uk (which is a stamp of the page we get), the two links function, but the 4 buttons (1 through 4) do not- these are the buttons that call the navto function in javascript code (which we need to do the “jump to” function in our products).
Why is this happening?
Thanks
TKART

You need to use window.open("navto://page2") in your code.
Neil

Android viewer issues

With the latest version of the Android viewer I've noticed two things:
1 - When I quit the app and re-open it I see the "Sign In" text in the upper left. I tap it once and there is no change, I tap it a second time and it pops up with the box for entering a username and password. With previous versions of the content viewer I don't remember having to sign-in every time I quit and restarted the app. It almost seems as if I'm already signed in after restarting, however the text says "Sign In' instead of "Sign Out".
2 - I've successfully updated a folio for the iPad and it downloaded only the changed article. However when trying to update the same article for Android I got the "can't find files/article..." message so I had to delete that article and import it fresh. I did that, entered the metadata, and dragged it to its proper place in the order of articles. I then saw the update notice on the Xoom for that folio and tapped the view button and the update progress bar was only on screen for a couple of seconds for an article that was approximately 40MB. I viewed the folio and the update hadn't been made, the article looked the same. I then deleted and re-imported all the articles for that folio and the same thing happened, an update available notice but an extremely quick update. I gave it 10-15 minutes in case the server was just slow to see the updates and it didn't make a difference. No update notice after waiting, so I deleted and imported the first article again with the same results, the article didn't actually update. I then tried downloading the whole folio fresh onto my Droid X and it was successful with the changed articles being displayed correctly.
Has anyone else noticed the strange Sign In behavior with the Android viewer? Will the client be forced to tell everyone updating this folio on an Android device to tap the Archive button and re-download before they can get the updated articles? This was what I had to do to correctly see the updated articles on our Xoom.
Andrew

Trying to get it to work on the target device (in our case the Xoom) is the best way to understand the current Android viewer limitations.
The one's I'm most aware of (the last time I checked) are:
- no inline videos, you must play videos full screen
- the in-app viewer (Open in Folio) won't play youtube videos correctly, you must use "Open in Device Browser"
- HTML articles and web views are not up to the iPad version's capabilities
- PDF formatted folios/articles don't pinch/zoom. On the iPad you can only pinch/zoom on pages without any interactivity.
Here's a list culled from the new feature release notes that tracks the limitations and how they've been improved.
http://help.adobe.com/en_US/digitalpubsuite/using/WS67cb9e293e2f1f60-6abcbe621311f4e52df-8 000.html
Release 15
Scrolling is now enabled in HTML articles for the Android viewer.
Release 14
- You can now create retail folios for Android viewers. Customers can click a Buy button in the Android viewer library to purchase a folio.
- Customers can now restore all purchases in Android viewers as they can do in iPad viewers.
Release 13
Articles set to Horizontal Swipe Only (“flattened articles”) now work in the Adobe Content Viewer for the Desktop, as well as for Android and PlayBook viewers.
Release 11
The performance of PNG and HTML articles on Android devices has improved. The Android Viewer supports in-app web view.
Release 10
Although the Android Viewer more closely matches the iPad Viewer, some features are not yet supported. Unsupported features include flattened articles, inline videos, panorama overlays, and folios exported in PDF format. HTML articles and Web View overlays may have performance issues.

Android Viewer does not retain downloaded Folios

Hi,
Android Viewers (here without subscription) for Google Play Store, do not retain the folio file when downloaded. As long as the app is active (even as background task), there is no problem. But as soon as you kill the background task and relaunch the App, the folio file is missing and the download button shows again. I tested with two different apps.
I use the the following tools:
InDesign CS5.5
Adobe Folio Builder Panel 12.2.4
Adobe Folio Producer Tools 1.11
Adobe Viewer Builder 2.1.130
The folio is v20
The App is a v21 Android Viewer for Google Play Store without subscription
My Test Tablet is an Acer IconiaTab A510 with Android 4.0.3
Developer Mode (USB Debugging, etc.) is off
Has anyone the same behaviour?
Thanks
Yves

Hi, I have the same problem: Android viewers do not retain the folio file when downloaded. While app is in background all works fine but when close and relaunch folios must be downloaded again.
I use:
InDesign CS6
DPS Desktop Tools CS6
Adobe Viewer Builder 2.1.130
Folio and App Version is 21
I tested on:
Samsung Galaxy Tab 10.1 with Android 3.2
Someone could help us please? Thanks in advance.
Edit: I rebuilt folios and custom viewer for v20 and everything works fine. What a strange...

Adobe Viewer Crashing

I have noticed that the Adobe Viewer crashes ALOT, i.e., quits to the home screen. This is not a huge problem during testing, but I am wondering about the performance of built apps and whether or not anyone has noticed the same stability issues. This becomes a concern if the app is to be used during any sort of performance venue, where quitting could cause a serious inconvenience and problem for the presenter/performer. I personally have seen this behavior in some of the folio apps I have downloaded from the App Store, but I haven't used too many to make any or of conclusion.
Specifically with the quitting to the home screen, I have observed this happening upon almost every folio update in the Viewer.
The sequence is: notice that there is a folio update, agree to update, update is downloaded, touch front page icon, Viewer quits to the home screen. This happens 99.9% of the time. I am using an iPad 3. I have tried powering the iPad off, but the same thing happens, even if nothing else is running.
I am running the latest Viewer update (v23 compatible), but experienced the same behavior in the previous iteration.
Any thoughts would be appreciated.

Neil,
Thank you for your attention.
Here's the environment:
- Adobe Content Viewer: v23 (2.8.0.0.59944)
- "Customized Viewer" (ipa): assuming the same (2.8.0.1.59944)
- Folio version: set to the same (v23).
- Testing with: all, iPad1 (32Gb WiFi/3G) + iPad2 (64Gb WiFi/3G) + iPad3 (32Gb WiFi/3G), clean iOS 5.1.1 everywhere, no jailbreaks.
- We use vector (PDF) type articles, MSO and embedded audio/video clips.
- The size: test folio is 108,639,607 bytes, 27 articles. It does not crash even on iPad1. The final test / pre-Production version is 705,428,610 bytes (161 articles). It does crash even on new iPad3.
- There are also intermediate test versions (between 50 and 90 articles, between 200 and 350 MBytes, they also cause crash at 1,2 and new 3 iPad's)
- I remember we had these intermediate versions working on iPad3 and sometimes iPad2 until new Viewer v23 was released. The full version was not ready at that time.
That's it. Any suggestios?

Android viewer on Samsung Apps

I was not able to find info about experience with submiting of Android viewer to Samsung Apps - is there such possibility?
Thanks!

DPS does not officially support the Samsung Appstore hence no documentation. However, the same android APK from app builder should work on Samsung store too. Google around on how to send it to Samsung appstore

Android Viewer crashing

Similar Messages

Maybe you are looking for