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.

Similar Messages

Android Viewer with Chinese Support

Android multi-issue app build using View Builder 1.8, failed to display chinese in Library and index list.
Please see enclosed screen capture.

There won't be any official word on this until AWS is officially rolled out. Some devices may require a firmware update as well to enable it.

Android viewer

Does anyone know when the real version for the web viewer for android is going to be available? And when the android kiosk is going to have the functions of the apple kiosk? Thank you.

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 scrollable frames

We often use scrollable frames in folios. Is there a chance the the native android viewer supports vector scrollable frames in the near future?

Yup, soon. We're trying very hard to get them done but there are some memory things on Android that get in the way of us releasing it. We're working on those issues now.
Neil

Changes of inapps prices do not appears in native Android viewer.

Hi All.
First, have created new Inapps with some price - 18 UAH . Then changed prices ( 10 - 16 UAH )
Changes do not appears in native Android viewer.
Rebuilding and reinstalling do not give any changes.
Any ideas ?

Hi Dmitry,
This is a Google Play caching issue. We ask the store for the price, and if they are still returning your previous price there is nothing we can do about it. I suggest waiting a day for Google’s system to update and then try checking the price again.
Neil

MSO problems on Android Viewer

Hi everyone,
I am currently working on a Multi-folio project for both Android and iOS tablets. I'm going to do my best to explain my system and my problem, but if you have any questions I'm free to answer them.
I've been using multi state objects for popup screen overlays (one default "off" blank state and one state "on" with the popup content).
I have two layers, one with the original page content and one for the multi state object + buttons to toggle it.
On the content layer I've placed a button to turn the MSO to the "on" state.
Nested within the Multi state object are two buttons (one to open an external URL and one to change the MSO back to it's first "off" state)
So as an example workflow:
• I have a button that says "See recipe" under a photo of cookies.
• User clicks the button to have the recipe take over the entire screen
• The user can either click "open in web" or "close" buttons now available
This is a system that has worked flawlessly on iOS devices but for some reason when I bring it over to the latest android Adobe Viewer on a Nexus 7, only certain instances of this work.
My project has about 20 pages of this and about 5 of them work. I didn't treat any of these 5 any differently from the rest so I'm curious what is at work here.
My plan is to make different renditions of my folio, but this is an obstacle I have to make it over first it seems!
Thanks in advance,
Kenny

Okay great. I am content with where this discussion went on the differences between Android and iOS on the same rendition of my folio.
As mentioned earlier, I'm pushing to make different renditions. This new rendition I'm working on is specifically for Android so I'm testing it constantly on both the desktop based viewer and the android viewer. Both always yield the same results. It seems like I get stuck at a certain step in the process:
• Testing on the desktop and android viewer, I find one Button + popup combination that works.
• Testing on the desktop and android viewer as well, I find another page with a popup that doesn't work.
• I delete the broken popup + button and replace it with a duplicate of the working popup + button.
• I test this page out on both viewers and they work flawlessly. This is great!
• I replace the content of the popup now with random rectangles and doodles for another test. This works flawlessly as well.
• I feel confident enough to replace the popup content and doodles with real content, so I paste my content in to the exact same state after deleting my old content.
• I test it out again, and find the button no longer fires. The "content" I just pasted in includes two buttons and a recipe. This means that two buttons are nested into one state, because these buttons can't show up if the recipe doesn't show up. It's as if it realizes the MSO is too complicated and simply gives up.
Unfortunately I don't the liberty of just giving up on this complicated issue like this button!
Buttons are all still linked. I'm so curious what the issue here is.
Does this help get the gears turning in any way?
Are the android and web viewers the same vs. the iOS viewer? The only reason why I figure there's an issuse with buttons / MSO is because both the web and android versions can't handle them. But if both viewers are inherently the same then that destroys the basis of my testing.

Edit the hyperlink in the alert email (Modify my alert settings, View Issue Tracking)

is it possible to add the external hyperlink in these emails instead of the internal hyperlink?
in example when I get a list tracking email there are hyperlink that get sent out with these tags Modify my alert settings | View Issue Tracking | mobile view that use the internal url //servername how can I change it to use the external
address //internetname

Hi Joe, check out the following links for solutions:
http://sharepoint.stackexchange.com/questions/13216/how-to-create-custom-email-alert-template-in-sharepoint-2010
https://social.technet.microsoft.com/forums/sharepoint/en-US/e5ebc5a7-8295-49e4-a817-c31066e1ac3d/customize-the-sharepoint-2010-email-alert
http://www.alectang.com/blog/archive/2012/05/16/how-to-customise-sharepoint-alert-email-template.aspx
cameron rautmann

Viewing issues with Adobe Acrobat Professional 8

We have Adobe Acrobat Professional 8 installed, and we are having some issues when viewing pdf documents. Once a Word document is converted to a pdf document, some of the hyperlinks are appearing thicker (almost bold) than others, and some of the text appears lighter/darker than the rest of the text. There is no pattern to this, it is all very random.
When we print the pdf document, everything looks correct, so this only happening when we view the document on the computer.
Can anyone provide a suggestion on how to fix this issue?
Thanks!

Sorry, I forgot the attachment!
Hi Bill,
I am attaching screen shots of 1) a page where the hyperlinks appear thicker and 2) the document properties pages showing the fonts.
We have tried creating it with both the Adobe PDF Maker and the MS PDF tool and it happens using both. I am thinking that this really is a viewing issue, because it prints out fine. Also, it looks the same no matter what the zoom setting is.
Please let me know if you have any other advice.
Thank you!
Cari

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 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...

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

Are inline youtube videos supposed to work in native android viewer?

Hello,
I'm testing the new native android viewer. We are currently using the legacy viewer. I am wanting to have inline video - specifically from youtube, like we are able to do in iOS. Is this possible? I am still just getting sound and no visual in all of my tests. Thanks!

After some research, we've found that this is definitely Google's bug on Android and was fixed by them in later versions.
http://stackoverflow.com/questions/14289848/embedded-youtube-player-getting-cut-off
http://stackoverflow.com/questions/10433865/problems-aligning-a-youtube-clip-centrally-in- an-android-webview
http://stackoverflow.com/questions/16273930/video-is-cut-off-on-the-right-side
http://stackoverflow.com/questions/13080578/partial-screen-webview-with-video-cut-in-half
We're discussing now whether a) we could work around this given our current architecture, and b) whether it's worth the cost for these older devices. Either way, the experience is very slow on the older API and devices that ran it when you have youtube videos embedded in web views. Those devices simply aren't powerful enough. If the publisher you're working with owns the videos, I would consider streaming them directly, outside of youtube, in a native video overlay (we support streaming video on Android). The experience and performance should be better.
Regards,
Dave

DPS native Android Viewer

I currently have an app in the iTunes store and am trying to expand into Android ( Google Play ) and am using the new web-based DPS native Android Viewer...
1. Can my AppName be the same as in the iTunes Store ?
2. Can my Bundle ID be the same as in the Apple Bundle ID ?
3. In the library pane when I choose "Configure", the only options are 768x1024 - why is this. I want a PDF based solution that will scale to the users device's ratio... ??

1. Yes.
2. Yes.
3. Ignore that section of App Builder. It's called "advanced" for a reason and you don't need to use it.
Neil

Android Viewer v18 problems

One of my clients updated their Xoom to the latest Android viewer today and now is getting a "Failed to load the folio." error message. I checked on our end and about half of the folios that were working fine yesterday in the Adobe Content Viewer are now giving this same error message, while others open as normal. Is this a server problem? I have not updated my production software yet so the files are all made with v17.
Also, the thumbnail of the iPad versions (1024x768) are displaying the veritcal thumbnail even when the device is in the landscape position and the Android thumbnail is landscape.
The iPad version of the Adobe Content Viewer app doesn't have these problems, possibly since it hasn't been updated yet.
Any idea if the first problem is temporary? The client said they were able to solve it by archiving and re-downloading, but I thought we were past that silliness a couple of versions ago. Why should the customer have to re-download entire folios every time the viewer app is updated?
Andrew

I am able to view the affected folios online with the Folio Producer and all the articles seem to be there. When trying to update an article from one of the affected folios using the Folio Builder panel in InDesign I get the message "An error has occurred while updating article layouts. The InDesign file for the layout cannot be found." I understand that previously the solution for this was to delete and reupload the articles, but I've already had to do that a couple of times because of previous tool/software updates.
Should I just plan on reuploading all articles from all folios in the future any time the viewer/tools are updated? I'm glad that relinking files is now an option, but it's one I hoped to rarely use. Being forced to use it to relink and reupload articles/folios when updates are rolled out seems like an awfully big burden to pass on to customers. I'm hoping this is just a glitch on the cloud side of things that Adobe can resolve on their end. We have 2-3 GBs worth of folios split into hundreds of articles, reuploading is more than just an annoyance...it's a profit killer.

Is there is any way to show the nomber of shares of any post in facebook page using android view not desktop view

is there is any way to show the nomber of shares of any post in facebook page using android view not desktop view

Sorry, its not related to Mozilla Profucts.

Android viewer issues

Similar Messages

Maybe you are looking for