Adobe DPS, Android and HTML

I have been having problems with my multi-folio DPS app on a Galaxy Note 10" (GTn8010).
It was built for ipad and works fine on ipads 2 & 3.
On the Galaxy it is very laggy/clunky with loading wheels and all edge animations(.oam's) really struggle and some are cropped? I have to tap the screen to complete the animations in stages.
Some animations are very simple and small, yet not working at all?
Also my interactive html forms with dropdowns don't work. A simple html form with nothing fancy...
I have a contact form in Muse too, which doesn't work? The keyboard pops up, but it hides the form and doesn't input text?
Has anyone had simlar problems and is there a work around?
I have tried 1024x768 with pillarboxing and folio renditions at 1280x752 and still not working?
I hear there is an update on Jan 11th, but unsure if these issues are addressed?
Any help is much appreciated.
Thanks,
Nick.

We starting to test publish to Android. Our 1024x786 PDF iPad edition is showing OK on content viewer for android. There is black boarders, but with pich and zoom, it's perfectly viewable. HTLM and web content works fine. We simply don't have the time to recreate folios at various sizes. So our solution works for us.

Similar Messages

TransactionCannotConnectToServerError - Adobe DPS - Library and Store SDK 2.30

Hi
Adobe DPS - Library and Store SDK 2.30
What does the adobeDPS-TransactionErrorType.TransactionCannotConnectToServerError mean?
I wanted to run a login request throught the authentication service. Our entitlement server sends back the authentication token with a status code 200 but the authentication is incorrect because if this transaction error.
adobeDPS-TransactionErrorType.TransactionCannotConnectToServerError
Value: -110
Indicates the Library could not connect to the particular server needed to complete a transaction.
Thanks,
Peter

This line in Colin's video is incorrect:
"Access to Store/Library API creates new possibilities in an article"
The information in the articles is correct. Specifically, if you launch the Information Screen from within an HTML article or a Web Content overlay, you reference the Reading APIs. If you launch the Information Screen from within an entitlement banner, a custom library, or a custom slot, you reference the Library/Store APIs.

Adobe DPS Android custom viewer using Angular

Hi
I have recently developed a custom viewer app for the ipad using the excellent articles and code examples that Derek Lu provided.
This app used backbone as the MVP framework and communicated with Adobe DPS to retrieve folios and information using the provided API.
I have now been tasked with developing a similar version for the Android device and have been able to get hold of example code for the Android device from.
https://www.dpsapps.com/dpsapps/store_configurator/
However this code uses Angular as the MVP framework instead of Backbone - whilst i appreciate there are going to be device specific differences between the IPad and Android which will impact on what can / cannot be done on Android, i wondered if there was any particular reason why the code example for the Android viewer uses Angular over Backbone?
I was hoping to be able to leverage the Backbone code written for the IPad version but when i try to put this on the Android device i seem to recall it either not allowing me (when using the webbuilder) or that nothing seemed to work / appear on the device, whilst the Angular version (freshly downloaded and unchanged - but configured to bring down my folios with the relevant guid) from the dps app store configuration link (provided above) does work.
Additionally i seem to be unable to test the Android Angular version on my desktop in the same way i was the backbone version.
Has anyone else encountered similar problems?
Thanks
Dave

Having spent quite a bit of time scratching my head and googling i ended up finding the answer to this myself - so i thought i best post it to help others out.
What i could not comprehend was why a functioning backbone example on the ipad could not be directly copied across to work on the android device - what transpired was that the backbone example was using an older version of the AdobeLibraryAPI - taken from Derek Lu articles (from a few years ago) whilst the Angular version was using the most up to date version of the AdobeLibraryAPI. I found this mentioned and explained on another forum post:
https://forums.adobe.com/thread/1622729
so i went to Adobe DPS - Library and Store SDK 2.32 : Class Index : JsDoc Reference and got the latest version of the API, swopped it out and hey presto the backbone version now works on the android.

Android Adobe DPS viewer. HTML form dropdown menu closes everytime the viewer navigation pops up.

I have a web content page which contains a form dropdown menu: <select><option></option></select> ... and so on. I use this as a small filter to narrow a result.
When I tap the screen, this dropdown menu is shown and works correctly on an iPad. As a side effect the navigation from the Adobe DPS viewer is also shown although this doesn't interfere with the dropdown menu in the HTML. Both are shown.
On an Android tablet, the html dropdown menu is shown for a fraction of a second until the Adobe DPS viewer navigation pops up. The HTML dropdown menu just won't stay visible.
My question: How can I solve this? How can I make the HTML dropdown visible on an Android tablet? Or how can I prevent the DPS viewer navigation from showing?
Thanks

This phenomenon does not happen on a Samsung Galaxy Tab 2. While not showing the dropdown menu as on an iPad it shows it as a scrollable menu at the bottom.

Adobe DPS Android - Folio Size Best Practice

Hey everyone,
we designed a magazine for iPad and now want to bring it over to Android. A little bit of research and it seems, that the Samsung Galaxy Tab 7' is one of the most popular tablets. Second to that is the 10' Samsung Galaxy tab.
The problem I know have is, for which resolution I should re-do my magazine to work on most android devices.
I read about it (http://blogs.adobe.com/indesigndocs/2012/10/creating-dps-folios-for-android-devices.html), but still would be happy to hear from you guys regarding the following things:
Would it be wise do set a new folio size 1280x800 (to cover the 10')? I think it will be automatically scaled down to 7' on smaller tablets, right?
Or is it the better approach to work with an addiotional folio size 1024x600 to target the most popular tablet with 7'. As I recall correctly, the content will not be enlarged on larger tablets like 10', right?
What if I have a retina-Android-Device. Does the folio automatically scales up like on iPad?
Personally I would think that approach 1 is the one which makes most sense. content will be displayed fine on 10' and 7' with content slightly smaller on 7' (just like iPad retina and iPad mini).
What do you guys think?
Thanks a lot in advance!
florian

We starting to test publish to Android. Our 1024x786 PDF iPad edition is showing OK on content viewer for android. There is black boarders, but with pich and zoom, it's perfectly viewable. HTLM and web content works fine. We simply don't have the time to recreate folios at various sizes. So our solution works for us.

Adobe DPS prof. and free monthly magazine

Hello!
We want to produce free monthly magazine and we are ready to get adobe dps prof. edition and we are ready for annual payment.
The question is:
1. Can we make our magazine free? We need that everybody can download each new issue for free.
2. Can we make version for Iphone and Android?
Alex

1. Can we make our magazine free? We need that everybody can download each new issue for free.
Yes, you can make the Magazine free and can also enable free subscriptions as a Newstand App.
2. Can we make version for Iphone and Android?
Yes, using DPS Professional Edition you can create apps for iPad/iPhone and Android - (Google Play and Amazon)

Adobe DPS apps and cryptography/encryption

Hello,
We just used the Adobe DPS Single Edition to create an awesome animated storybook for kids (by placing m4v video overlays on every page). So, we are now ready to upload our app to the App Store.
As part of the submission process, we are being asked the following:
"Is your product designed to use cryptography or does it contain or incorporate cryptography?"
What does this mean?? Does this apply to apps created with DPS Single Edition? How would a DPS user even know the answer to this?

Select No. The custom viewer doesn't include cryptology.

Problem with Adobe Reader 9 and HTML Help, IE 7 and Firefox

Hello everyone
I have some Problems with the Adobe Reader 9.1.0 and different browsers.
If I want to open a PDF document in one of these browser the browser-window freezes for 30 seconds and the document is built-on line by line.
The Trouble is that if the document is comlete loaded an i want to scroll down, the windows freezes again and the document starts again with built-on...
I have tried to open the documents with Reader 8.1.3 and this works fine, but i need to open the documents with Reader 9.1.0 because this is a customer preference to open the document with the newer version!
Sorry for my english but i hope my problem is understandable :-)
Does anyone know how to solve this problem?
kind regards
Marcel

1. It happens with any file i want to open in browser.
2. The Problem is specific to browser. When I open a document in the Reader application everithing works fine.
kind regards
Marcel

Adobe DPS Folio and Content Viewer Query

Hello,
I am currently creating folios using the Foilo Overlays and Folio Builder and then previewing them on the Content Viewer on the iPad. My question is after the 1st May will I still have the ability to do this? I don't create app just preview them on my iPad to see how they work. If anyone can give me an answer it would be much appreciated.
Regards,
Alan

Yes, after May 1, you'll still be able to create, edit, and share folios, and you can use Adobe Content Viewer to view folios. You just won't be able to build single-folio apps using a Single Edition or Creative Cloud license.

Hi everyone !!! im a rookie in these adobe dps matters, and this is my first app launch!!!

I did a multi folio app, but apple reject it, because my multifolio app shell appears empty, without the first folio inside, i thought that apple after the app review process ,i wiil be available to upload the different folios, and at first the app it will be appear empty, but then i can upload the folios and therefore appears inside the app !!! Is this correct ? i don't understand why, when i tested the app in my ipad, appears the app the shell (the interface) perfectly but without the folios inside.... i mean like a nutshell without the folio inside...in fact the app appears empty. Can anyone help me please to understand this ??? so i can resubmit my app for review again to apple!!!! thanks a lot !!!

Hi Thanks for answer Bob you are so cool !!! but since i was read in the adobe IOS publishing companion guide pro and enterprise edition guide, and i saw, that before and after i submit the multi folio app shell to the apple for review, i can publish the folios after ...i thought that: 1. my app will appear approved by apple, appears empty 2. publishing the folio with the folio producer... but something went wrong, because at first when i tested my app in my ipad i saw that the app(shell) appears without the folio that i build !!! i said something is wrong, but i thought that i could be able to publish the folio after the app appear at the apple appstore...and in some way with the folio producer, tie up the folio to the app !!! but it didn't work !!! What i did wrong ??? Thanks a lot Bob !!! But i need your precious knowledge !!!
this is the apple message and pict from the resolution center: We were unable to locate some of the features described in your marketing materials or release notes. Specifically, the app loads to an empty storefront. Please refer to the attached screenshot.

Adobe DPS HTML/Javascript/CSS Web Console: why it is so difficult?

Why?
This is the type of question that i can not understand. Is it that difficult to make? Maybe an airpor to Google Chrome Adobe Edge Inspect? I have many files well written with CoffeeScript, that uses RequireJS, that is impossibile to forget a semicolon etc. that works like a charm on Google Chrome (desktop, AND Chrome iPad, AND Chrome Android). That works like a charm in the native iPad/iPhone web browser and in the native Android browser. But it didnt in Adobe DPS. And guess what: i cant find why it doesnt, because Adobe doesnt have a simple Web Console inside DPS / InDesign.
Is there any news on this field? Because using Adobe Edge Inspect is not a option: my code works inside EI because im browsing the page with my desktop browser. I want to know what is going on inside DPS.
And my code it is not "soooo" advanced. It is just a simple button with "on touchstart" event listener. Am i doing some stupid error? Fine! Just help me find out what it is, so i can fix it. Because in every single browser i tried, it works. But inside DPS. A sample code? Sure, here you go:
[Javascript Code]
Main.prototype.clicks = function() {
        var _this = this;
        $('#btnA').on('touchstart', function(evt) {
          evt.preventDefault();
          _this.buy('productA');
          return false;
        $('#btnB').on('touchstart', function() {
          return _this.buy('productB');
        return $('#clear_data').on('touchstart', function() {
          return _this.clearData();
[/Javascript Code]
The Javascript above is being generated by Node.JS compiling a CoffeeScript file. The buttons do work at DPS for iPad, but doesnt on Android. Maybe Android has a problem with 'touchstart'. Maybe jQuery has a problem inside Adobe DPS. But who knows? I dont have a decent web console inspector to check what is going on. Really frustrating.
Maybe Apple and Google dont give the neccessary hooks to implement the web console? But if you can do the Inspector from the desktop to the device, why not from the device to the desktop? Am i missing something on Edge Inspect? The strange part is: the above code works well on Edge Inspect but doesnt work on Android DPS.
Sorry if im a little angry or pissed. But this would be really great: a simple web inspector: HTML, Javascript, CSS. A way to inspect the <head> tag of the HTML, what was loaded, in what order. What script is missing, Javascript breakpoints, etc.
Thank you.

There is this one little widget called Safari Web Inspector, provided that you're using a Mac: https://developer.apple.com/library/safari/documentation/AppleApplications/Conceptual/Safa ri_Developer_Guide/Introduction/Introduction.html.
Besides, referring to http://helpx.adobe.com/digital-publishing-suite/kb/create-html-articles-android-viewers.ht ml, you can give window.onappear a try when you are doing JS initialization.

DPS android app for small screens, works, but poorly...

There is a way to get the DPS android app compatable with 1400 devices, including mobile phones.
In theory if you here reading this its because you have an android app made by the DPS app builder live in the play store and...
A: found out that the android app is only available on large/xlarge screens
B: are getting yelled at by your employer who bought the Adobe DPS subscription and claims this should work on his phone "because I looked at the Adobe site and it says android, my phone is an android, read their site and make it work"
C: found this because you were smart enough to read through the forums before suggesting this as a publishing solution to your employer and want to know if it really works on android phones, in whcih case, you may want to make it easy on yourself and just say "no, it does not" and then waid for Adobe to officially support small/normal screens perhaps head over to this post and bring some attention to it so we can collectivly improve this already awesome tool: http://forums.adobe.com/thread/1097433
however, before you attempt this please keep in mind the following:
1- it does not work well, if at all, on certain devices. specifically the small phone devices with the slower processors. So what typically happens is that you need to delete the data for the app and wait nearly 10 min for the "checking for updates" to process and grab new edditions. Depending on your serivce provider, this can be a nightmare. So, do NOT even attempt this if you have a cap on your data plan, think about how long it would take to download a 100mb folio file on a 3g connection, not to mention the processor which the tablets have and phones do not have.
Here is some more data:
--Android 1 from Sprint: really super slow, thats all I gotta say
--Android 2 from Verizon, again, slow, but works
--Galaxy Nexus 4.1.1, Verizon 4g connection, works great, (10% of the time) lol. about 90% of the time the Galaxy Nexus needs to be restarted after installing, and will get stuck on the "updating library" screen. the only way to fix this for any of the above phones seems to be to clear all data, uninstall, re install, do not launch, restart phone, and then launch app.
I am going to test the following soon:
     Samsung Galaxy Note II N7100 (1.6GHz Quad-core)
     (1.5GHz Quad-core)
          LG Optimus G E973
          Xiaomi MI-2
          LG Optimus 4X HD P880
          HTC One X
(the idea being that perhaps we can go through the list from google in the play store and limit the devices its on, but at least with this solutuon as described below we can get rid of the "not availabe on your device" notice.)
So before you read on, consider that for your end users. If you find a way to fix this, let me know, I have considered turning off hardware acceleration but have not tested this yet.
2- if you choose to attempt this make sure you have a good understanding of command line AND you have a new version of the app ready if you want to roll back.
consider this concept: (you should have these ready)
app a- made by Adobe DPS app builder, works on only large and x-large android screens, lets say its version 100000 and 2.5.5.000. This is already in your google.play store account as a live app,
app b- the app you are about to build in this example below, it will in theory work on small, medium, large, and x-large android screens, lets say its version is 110000 and 2.9.9.000 (it will be MADE FROM APP A, you will open it, edit it, and wrap it back up.)
app c- made by Adobe DPS app builder, works on only large and x-large android screens, lets say its version 200000 and 3.5.5.000 (which would be good to have in case your version b above does not work the way you want)
notice the VERSION codes. These are important because you can only go UP, you can not "roll back" to a previous version.
Again, I do not suggest this, but if you are daring and have some development background, feel free to give it a shot.
(I am not going to be able to support this info, but I can verify 100% that I got mine working, very poorly and slow, but it installs, pulls folios, and loads)
PC WINDOWS ONLY, I have not tried this on a MAC.
get this:
http://www.7-zip.org/
install it
get this:
http://code.google.com/p/android-apktool/
read all about it.
go here:
http://code.google.com/p/android-apktool/downloads/list
get:
          apktool1.4.3.tar.bz2
and
          apktool-install-windows-r04-brut1.tar.bz2
put them all in 1 folder, extract both items, all the way
the grab the
          android-viewer.apk
that Adobe DPS made, or whatever yours is named...
and the
          release.keystore
you made and put them in the same "stuff" folder. there should be 20 items total in here now.
get this:
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u30-download-1377139.html
          jdk-6u30-windows-x64.exe
do NOT use any other version, do NOT use version 7, use version 6.
install it all. then find it. should be here- (C://program files/Java/)
I recomend grabbing it all and putting it in your ROOT like this:
C://Java/jdk1.6.0_30/bin
then, put everything from the "stuff" folder into C://Java/jdk1.6.0_30/bin
yep, all of it.
now we are ready to get funky...
run cmd line.
open start menu, type
cmd
into the search bar, hit enter
-------- run command line, get to proper directory
cd ..
cd ..
cd Java/jdk1.6.0_30/bin
(or wherever your 'stuff' is)
--------open up
apktool d android-viewer.apk android-viewer
(this will make a folder called 'android-viewer' and you will be able to go into that folder and find the XML files in there)
--------edit XML
in file: /android-viewer/AndroidManifest.xml
open up in dreamweaver and change this stuff:
android:versionCode="_ENTER_NEW_NUMBER_" android:versionName="_ENTER_NEW_NUMBER_"
<supports-screens android:smallScreens="true" android:normalScreens="true" android:largeScreens="true" android:xlargeScreens="true" />
in file: /android-viewer/assets/META-INF/AIR/application.xml
open up in dreamweaver and change this stuff:
          <versionNumber>_MATCH_ABOVE_</versionNumber>
          <versionLabel>_MATCH_ABOVE_</versionLabel>
<supports-screens android:smallScreens='true' android:normalScreens='true' android:largeScreens='true' android:xlargeScreens='true'/>
--------package it back up
apktool b android-viewer android-viewer-new.apk
(this will repackage the folder into a new APK, note the name -new.apk added to the end)
--------Sign
jarsigner -keystore release.keystore -signedjar android-viewer-signed.apk android-viewer-new.apk YOUR_ALIAS
(now you need to sign the -new apk and recreate it as signed)
--------Verify
jarsigner -verify -verbose -certs android-viewer-signed.apk
(if the last line does not say 'successfully verified' and there is an error, make sure you are using version 6 of JDK and not 7)
--------Update APK in play store
Visit this page
http://developer.android.com/distribute/googleplay/about/distribution.html#instant
read the line that says "Instant publishing, instant updates"
while you do, understand you are being lied to, it takes anywhere from 30 min to 4 hours for your update to be "instant".
take the new "android-viewer-signed.apk"
rename it, upload it, activate it, de activate the old one.
important: beofe you click save, switch over to the "product details" tab and update your version notes.
head over to your app page in the play store.
sit there and click refresh every 10 min or take a nap and come back in a few hours.
when you finally see the version number has updated, go to the browser on your phone
find your app in the browser, refresh the page, make sure its got the new version number on it.
install it on your small screen device, cross your fingers, and hope you do not get a message that says "not signed properly"
if you do, feel free to start googling the stuff above to see where you went wrong.
If it does work, go to your boss and have him download it and run it and say "see, there ya go, its on your phone now" and when he says it does not work hand him a minni screw driver and a 1.6GHz Quad-core from the Galaxy Note II and tell him to simply upgrade the procssor in his phone because its too slow. lol.
-good luck and enjoi

Hi,
This is very interesting. I'm not an expert but i could do almost all the steps, but i can not do the sign step. i dont know where my release.keystore is. i created a .key.p12 file, is it?
I'm trying to do this for a Galaxy SIII
Thank you

Adobe DPS - using video

I am trying to set up an FAQ page with a list of questions on the left which activate videos that appear in the same frame area on the right. I’ve uploaded the video as an object state, and used the button to activate and play the relevant video/state. It works ok in the SWF preview, but crashes InDesign everytime I attempt to upload it as an article. can anyone help me?

Having spent quite a bit of time scratching my head and googling i ended up finding the answer to this myself - so i thought i best post it to help others out.
What i could not comprehend was why a functioning backbone example on the ipad could not be directly copied across to work on the android device - what transpired was that the backbone example was using an older version of the AdobeLibraryAPI - taken from Derek Lu articles (from a few years ago) whilst the Angular version was using the most up to date version of the AdobeLibraryAPI. I found this mentioned and explained on another forum post:
https://forums.adobe.com/thread/1622729
so i went to Adobe DPS - Library and Store SDK 2.32 : Class Index : JsDoc Reference and got the latest version of the API, swopped it out and hey presto the backbone version now works on the android.

Publish two publications from different customers with the same Adobe DPS ID

Hello:
I have a publication made on InDesign and I have uploaded it to the Adobe Server with my Adobe DPS account. For the first publication, I published the publication with the Folio Producer on the digitalpublishing portal, and then I created the app using the Adobe Viewer Builder. Then, I tried it locally on my iPad. It was working fine and I could see my publication.
Now, I do need to upload a new publication for a different customer with the same Adobe DPS account and I need to create a different app with the new customer look and feel but I don't want to show the first publication in this new app, only the last one.
In a nushell, I need to keep separated two publications (or more) when they are published if I'm using the same DPS Account... Is that possible?
Saludos Cordiales,

Hi Leo,
Every title should have its own publication AdobeID (a title can contain multiple editions / folios).
So you have to request for every title you want to work on a provisioned account with Adobe. Make sure that you have setup the corresponding emailaddress / emailalias. For example [email protected] and [email protected]
After the accounts have been provisioned you can:
* upload and organize multiple folios for that publication in the corresponding Folio Producer
* Create a viewer with your Viewer Builder and on the first page supply the AdobeID for the give publication
You can request new publication accounts any time and these are included with your DPS subscription.
When you first account got provisioned, you should have received an excel document to request provisioning for the various publications. In this document you can list the accounts you want to use for publications, individual users of the system and viewer builder access.
With kind regards,
Klaasjan Tukker
Adobe Systems Benelux

Adobe DPS app v31 crash

Hello,
I've built a v31 app ( iOS ) with Adobe DPS Builder and installed it on the ipad.
This first time i open the app it crashes, working fine the next time i start it.
I've tried to upload this version to itunes, but it was rejected because of this issue.
Is it a known problem? Is it something with my app version?
The last version that was ok was v29. v30 had problems with logins and v31 is crashing on first startup.
I can't build v29 apps anymore..
Thank you,
Diogo Neves

Diogo,
We became aware of a potential crash recently and are working on a fix. It may be the same crash you are experiencing. The crash isn't happening all the time, and it will only happen on first launch. Unfortunately, it's not easy to reproduce consistently, so if you uninstall and reinstall the app, then launch you might not see the problem again.
We hope to have a public fix released quickly.
I'm not aware of V30 login problems that would prevent you from using that version. What exact issue were you experiencing?
-nate

Adobe DPS, Android and HTML

Similar Messages

Maybe you are looking for